An operations manager interview tests three things: can you read a process and find the constraint, can you run a P&L and the metrics under it, and can you lead a team through change without breaking service. Expect a mix of process and metrics cases ('walk me through how you'd cut cycle time on this line'), people-management scenarios (underperformance, turnover, a shift you inherited), and behavioral questions answered with real numbers. The strongest candidates do not recite definitions of Lean — they tell tight, quantified stories about systems they fixed. Below are the questions that come up most, what each is really probing, and how to answer without rambling.
What the interview is really measuring
Strip away the specific questions and an operations interview is checking three things. Can you look at a flow and find where it is actually constrained, rather than optimizing the part that feels busiest? Can you run to numbers — own a budget, defend a cost per unit, trade off service against cost deliberately? And can you move a team and a process through change at the same time without breaking the thing you are responsible for? Every question below maps back to one of those.
The questions that come up most
| Question | What it’s really probing | How to answer well |
|---|---|---|
| Walk me through how you would cut cycle time on a line running over takt. | Can you reason from data to a measured result, or do you guess? | Baseline the metric, find the constraint with data, name the method, quantify the gain, and say how you sustain it with standardized work. |
| Tell me about a time you missed a key metric. What happened? | Ownership and recovery — do you hide misses or fix them? | Name the miss and its size honestly, the root cause you found, the corrective action, and the number after. Show the system change, not just an apology. |
| How do you handle an underperformer on your shift? | Do you diagnose before judging, and do you hold a standard? | Distinguish a training, process, or fit problem; describe the conversation and plan; give the outcome for both the person and the operation. |
| You inherit a team with high turnover. First 90 days? | Can you stabilize people and process at once under pressure? | Stabilize service first, then diagnose causes (scheduling, pay, leadership, workload), fix the highest-leverage one, and name the metric you would watch. |
| How do you trade off cost against service level? | Do you treat operations as a system with deliberate tradeoffs? | Show you quantify both sides — cost per unit vs. OTIF or fill rate — and decide against a business target, not by reflex. |
| Describe a process you improved using Lean or Six Sigma. | Real application vs. buzzword familiarity. | Tell one tight, quantified story: the tool (DMAIC, value-stream map, 5S), the before/after numbers, and the dollars or service it returned. |
How to structure a case answer
Process and metrics cases are where strong operators separate from the pack, and the separation is structure. When asked to improve a line, a DC, or a service flow, walk the same path every time:
- Define the metric and baseline. "First I want the current cycle time and where it sits against takt." You cannot improve what you have not measured.
- Find the constraint with data. Name how you would locate the bottleneck — time studies, a value-stream map, defect Pareto — rather than naming the fix you already assumed.
- Apply a method, sized to the problem. Quick win versus a full DMAIC. Interviewers like candidates who right-size the rigor.
- Quantify the expected gain and the guardrail. "I'd target a 20% cut while holding the defect rate flat." The guardrail shows you do not chase one number into a new problem.
- Sustain it. Standardized work, a control chart, a daily metric review. Improvements that are not held do not count.
People-management scenarios
Roughly half of an operations manager interview is leadership, because the job is getting results through a team that often did not pick you. When you get a scenario — an underperformer, a high-turnover shift, two leads in conflict, a safety pushback — resolve it the way you would on the floor: name the issue, cite the data or observation that surfaced it, describe the conversation or change you made, and give the outcome for both the person and the operation. The trap is answering as a personality ("I'm firm but fair") instead of a process. Diagnose before you judge — an "underperformer" is often a training or staffing problem wearing a performance costume — and show you hold a clear standard once the cause is understood.
Questions to ask them
The interview runs both ways, and an operator’s questions signal how you think. Ask what the team’s current pain metric is and where it sits against target. Ask what broke the last time they scaled, and what the first 90 days would actually own. These show you walk into an operation looking for the constraint — which is the job.
The honest summary
Operations interviews reward operators who reason from data to a measured result, know their numbers cold, and lead change by diagnosing cause before judging. Structure your case answers, bring three quantified stories, and be credible about the systems and metrics you ran. For pay and demand context to ground your level and your questions, the BLS Occupational Outlook for general and operations managers is a useful baseline. Prepare the three stories well and most of the interview is just you choosing which one fits the question.
Common questions
- How do I answer a process-improvement case question?
- Structure beats cleverness. Define the metric and current baseline, find the constraint with data (not a guess), name the method you would apply (value-stream mapping, root-cause, a controlled change), quantify the expected gain, and say how you would sustain it with standardized work. Interviewers are watching whether you reason from data to a measured result, not whether you know the textbook term.
- What metrics should I be ready to discuss?
- The ones you have actually owned: cycle time, throughput, OTIF, fill rate, cost per unit, scrap or defect rate, inventory turns, labor as a percent of revenue, and safety incident rate. Know your numbers cold — the baseline, what you moved it to, and exactly how. "We improved efficiency" gets followed up; "we cut cycle time from 36 to 22 hours by rebalancing the line" closes the loop.
- How do I handle people-management scenario questions?
- Use a real situation and resolve it like an operator: name the issue, the data or observation that surfaced it, the conversation or change you made, and the outcome for both the person and the operation. For underperformance, show you diagnosed cause (training, process, fit) before judging. Interviewers want evidence you hold a standard and develop people, not that you are nice or harsh.
- How technical do I need to be on tools like SAP or ERP?
- Enough to be credible about what you ran in them and what you pulled out: the reports you steered by, the inventory or production data you trusted, the integrations that broke and how you handled it. You will not be quizzed on configuration unless the role is systems-heavy, but vague answers about "the ERP" signal you watched dashboards rather than operated.
Sources
Keep reading
How to answer "tell me about yourself"
Answer "tell me about yourself" with a 60-90 second present-past-future pitch tailored to the role. The structure, a before/after example, and what not to do.
What questions should I ask the interviewer?
The best questions to ask an interviewer, organized by who you are talking to. Questions that signal seriousness, surface red flags, and the ones to avoid.
How do I prepare for a behavioral interview?
Prepare for a behavioral interview with the STAR method, a bank of 6-8 stories mapped to common competencies, and practicing out loud. Examples included.
Software engineer interview questions
The real software engineer interview loop — phone screen, coding, system design, behavioral — with representative questions per stage and how to prep.