Operations Manager Interview Questions, and How to Answer Them

Operations manager interviews cover much the same ground wherever you apply: how you've improved processes, which metrics you owned, how you manage people, budgets and costs, supplier and supply problems, and how you prioritize when several things go wrong at once. Many add a case exercise. Nearly every question asks you to prove a result, so the best preparation is knowing your own numbers.

Below are the questions that come up in each area, what each one probes, and an outline of a strong answer. The outlines are not scripts: the details have to be yours.

What the interviewers want to find out

Three things, asked in different ways: whether you have improved something measurable and kept it improved, whether people work well for you, and whether your judgment holds up when the plan falls apart.

Expect two kinds of question. "Tell me about a time…" asks for evidence from your past; the STAR method is the clearest way to structure those answers. "What would you do if…" tests how you think through a situation you may not have met yet.

Process improvement

1. "Tell me about a process you improved. How did you know it worked?" Probes: your method, and whether the result lasted. Strong answer: the baseline; what you found when you looked (the root cause, not the symptom); the change; the result over a stated period; and what you did to make it stick, such as standard work or training.
2. "How do you find the bottleneck in a process?" Probes: whether you go and look. Strong answer: walk the process, see where work queues up, check the data, and talk to the people doing it. Then fix the constraint, because speeding up any other step doesn't increase output.
3. "Tell me about an improvement that didn't work." Probes: honesty and learning. Strong answer: a real failure, why it failed (often because the people doing the work weren't involved), and what you do differently now.

Metrics, KPIs and systems

4. "Which KPIs did you own, and what were they when you started and when you left?" Probes: whether you know your numbers. Strong answer: three or four metrics, each with a baseline, a result and a timeframe, such as on-time delivery, cost per unit, error rate or productivity.
5. "What would you look at first in your first week here?" Probes: whether you think from the customer back. Strong answer: it depends on the operation, and you say how: service levels and backlog in a service team; on-time in full and order accuracy in a warehouse; safety, output and quality on a production line. Then where the numbers come from, and whether people trust them.
6. "A KPI is green, but customers are complaining. What do you do?" Probes: whether you know what metrics hide. Strong answer: check how the metric is defined and measured; look past the average for the orders or customers that fail; talk to the people complaining; add a measure closer to what customers experience.
7. "Which systems did you use to run the operation, and which report did you check every week?" Probes: hands-on use, not a list of software names. Strong answer: the systems (an ERP, a warehouse or scheduling system, spreadsheets) and what you used each one for; a report that changed a decision; and what you did when its data turned out to be wrong.

People management

8. "Tell me about a time you managed someone who was underperforming." Probes: fairness and follow-through. Strong answer: what you checked first (were expectations clear, and did they have the tools and training?), the conversation, the agreed plan, how you followed up, and the outcome, including if they left.
9. "Your team resists a change you're introducing. What do you do?" Probes: whether you can bring people with you. Strong answer: explain why the change is needed, involve the people who do the work in designing it, pilot it, and listen to objections, because some of them will be right.
10. "How do you keep the operation running through absence and turnover?" Probes: planning. Strong answer: cross-training, a schedule with cover built in, written procedures, and looking at why people leave, not only at how to replace them.

Budgets and costs

11. "What budget have you managed, and how did you track it?" Probes: financial discipline. Strong answer: the size and the main cost lines (labor, overtime, materials, freight), a regular review of actual spending against budget, and one variance you spotted, explained and fixed.
12. "Tell me about a cost you reduced. What did you protect?" Probes: whether the savings were real and lasting. Strong answer: the cost and its cause, the change, how you confirmed the saving afterwards, and what you made sure didn't suffer: service, quality, safety or the team.
13. "You're asked to cut your budget by 10%. How do you approach it?" Probes: analysis before action. Strong answer: break the costs down; separate fixed from variable; look for waste first, such as rework, overtime and expediting; present options with their effect on service; and agree the trade-offs with your manager rather than cutting evenly across the board.

Suppliers and supply problems

14. "A key supplier tells you a delivery will be two weeks late. What do you do?" Probes: containment first, then the cause. Strong answer: check stock and what's at risk; look for alternatives, such as another supplier, a substitute or a partial delivery; decide which customers or lines to protect; tell sales and customers early. Afterwards, review the supplier, and whether you need a second source or more safety stock.
15. "How do you manage supplier performance?" Probes: structure. Strong answer: agreed measures (on-time delivery, quality, cost, responsiveness), regular reviews, a clear escalation route, and a willingness to work through problems with a supplier before switching.
16. "Tell me about a time you changed suppliers or renegotiated a contract." Probes: commercial judgment. Strong answer: why, how you compared total cost rather than unit price, the risks you managed during the switch, and the result.

Prioritization

17. "A safety issue, a big customer's late order and a system outage all land at once. What order, and why?" Probes: judgment under pressure. Strong answer: safety first, always: make the area safe. Then weigh the customer against the outage by impact, hand one of them to someone capable, and tell the people affected what's happening.
18. "How do you decide what your team works on when everything is urgent?" Probes: whether you have criteria. Strong answer: safety and compliance first, then customer commitments, then the cost of delay; make the trade-off visible to the people asking; and say "no" or "not yet" out loud.

The case exercise

Many operations interviews include a practical exercise: an in-tray of competing problems, a data set or dashboard to interpret, or a short presentation such as a 90-day plan. Here is an invented example of the data kind:

"On-time delivery at a distribution center has fallen from 97% to 89% over six weeks, while volume is flat. What do you investigate first, and what would you do in your first week?"

A strong response:

• Checks the measure. How is "on time" defined, and has the definition or the data feed changed?
• Breaks the misses down by shift, carrier, customer and product, to find where most of them happen.
• Asks what changed six weeks ago: new staff, a system update, a new carrier, a new layout.
• Contains, then fixes: a quick action to protect customers this week, and a fix for the root cause, with a measure that will show whether it worked.
• States its assumptions and ends with a recommendation, not just a list of things to look at.

For a 90-day plan, show that you'd listen and learn before changing much: the people, the process and the numbers first, a few quick wins, then a plan agreed with your manager.

How to prepare with your own numbers

Most of these questions can only be answered well with figures, so put yours on one page before the interview:

• Your scope: team size, shifts, sites, volume per day or week, and budget.
• Three or four metrics you owned: where each started, where it finished, and over what period.
• Two cost savings: what they were, how you confirmed them, and what you protected.
• One failure: what happened, and what you changed afterwards.

Know the denominator. "We cut errors by 40%" invites "From what to what, and over how long?" Be clear about what you drove and what improved around you, because interviewers ask. If figures are confidential, use percentages or ranges.

Then match each requirement in the job description to one of your stories. For the hiring stages and a week-by-week plan, see our guide to preparing for an operations manager interview; for the exercise formats employers set and how they're marked, see operations manager practice assessments.

For director or head of operations roles, expect the same areas at a larger scale: a P&L rather than a budget, several sites, and how you develop the managers who report to you. Our operations manager career guide sets out how the role changes at each level.

Cohesyve, which publishes this guide, runs practice job simulations for your role, with written and spoken questions and data to interpret, and a scored report on where you lost marks.

If you're the interviewer

The same areas work from the other side of the table. Ask for numbers, then ask what the candidate personally did. Test the claims with a short case, and score every candidate against the same criteria. Our page of operations manager interview questions is written for interviewers, with what to look for in each answer.