Business Management Interview Questions: 7 Full Answers

Entry level: management trainee, why business management (140 words)

Question: Why do you want a career in business management?

Answer: Because the part of every job I have had that I liked most was making the work run better for the people doing it. In my last year of college I was shift lead at a campus coffee shop with nine student staff. Schedules were posted on a Thursday for the next Monday, and people swapped shifts by text, so we were short at least twice a week.

I moved the schedule to a shared app, posted it two weeks ahead and set one rule for swaps. Short shifts went from twice a week to about twice a month. That is a small operation, but it is the job in miniature: a process, people and a number. Your trainee program would give me that at a much larger scale.

Mid level: business manager, setting goals and measuring them (140 words)

Question: How do you set goals for your team and measure them?

Answer: I start with the two or three numbers the business is judged on and work back to what my team controls. When I took over a regional service branch, the company measured revenue and customer retention. My team could not move revenue directly, but they controlled first visit fix rate and response time, which drive retention.

We set a target for first visit fix rate, reviewed it every Monday by technician, and I paired the two lowest scorers with the two highest for a month. Over two quarters first visit fix went from 71 to 82 percent, and the branch's renewal rate rose with it.

I also keep goals few. A team with eleven KPIs has none, because nobody can tell you which one matters this week.

Mid level: business manager, managing a budget under pressure (141 words)

Question: Tell me about a time you had to cut costs without hurting results.

Answer: Last year our office services unit was asked to cut its operating budget by eight percent mid year, on a budget of a little under $2 million. The easy option was a hiring freeze, which would have overloaded a team already at capacity.

I went through every contract first. We had three print and mail vendors doing overlapping work, two software tools doing the same job, and an overtime pattern caused by a weekly report that landed on Friday afternoons. I consolidated the vendors after a short bid, cancelled the duplicate tool and moved the report to Thursday. We hit the eight percent with no job losses and overtime fell by about a third.

What I learned is to look at contracts and calendars before people.

Mid level: business manager, handling an underperforming employee (153 words)

Question: How do you handle an employee who is not performing?

Answer: First I check it is a performance problem and not a clarity problem. In my last role a senior coordinator was missing deadlines on supplier orders. In our first conversation it turned out she had inherited a second region's suppliers without anyone telling her the priorities.

We agreed on a written list of which orders came first and a fifteen minute check in each week for a month. Her deadlines recovered within three weeks. If they had not, the next step would have been a formal plan with HR, with clear targets and dates.

With a different person on the same team, the conversation was about attitude, not workload, and it ended with a formal plan and, two months later, a fair exit. Both outcomes are part of the job; the mistake is waiting six months to have the first conversation.

Senior: general manager, a decision with incomplete information (152 words)

Question: Tell me about a major decision you made without all the information you wanted.

Answer: As general manager of a distribution business with around 140 staff, I had to decide whether to renew the lease on our second warehouse, a five year commitment, three months before our largest customer would confirm their volumes for the next year.

I modelled three cases: the customer stays, cuts by half, or leaves. I asked the landlord for a two year renewal with an option to extend, at a slightly higher rate. That cost more per square foot but limited our exposure in the worst case.

The customer cut volumes by about a third. With the shorter lease we consolidated into one site at renewal instead of carrying an empty building. I now model the bad case first on any long commitment, because it is the one that decides whether you can survive being wrong.

Senior: operations director, leading change people resisted (151 words)

Question: Describe a change you led that people resisted.

Answer: We replaced paper job sheets with a mobile app for sixty field technicians. The first rollout, before I joined, had failed because the app arrived by email with a training video.

I asked the three most skeptical technicians to test the app for a month and tell me what was wrong with it. They found four problems that would have killed it, including that it needed a signal to save a job, which half our sites do not have. The vendor fixed offline saving before launch. Those three technicians then trained their own crews.

Adoption reached all sixty technicians within ten weeks, and invoicing time after a job fell from about nine days to two, because sheets no longer sat in vans. The lesson for me was that the loudest critics are the best testers you will ever get for free.

Mid level: business manager, conflict between two departments (151 words)

Question: Tell me about a time two departments in your area were in conflict.

Answer: Sales and operations at my last company argued every week about delivery dates. Sales promised customers next week, operations said three weeks, and customers heard both. Each team thought the other one was the problem.

I put the two team leads in a room with the last sixty orders and asked one question: where did each order wait? It turned out most of the delay came from orders entered with missing specifications, which operations then sent back. Nobody was lying; they were looking at different halves of the same order.

We added three required fields to the order form and a daily ten minute call between the two leads. Within a quarter, orders sent back for missing information fell by more than half, and the weekly argument stopped because both teams were reading the same report.