- 20 questions
- Scoring rubric 1–5
Operations Manager Interview Questions
An operations manager is hired to make things run predictably and cheaper without breaking them. Interview for that with questions about a process they fixed and the before-and-after numbers, a cost they cut and what it broke, an incident and the first hour, and how they got other teams to change. Every strong answer in this role has a number in it.
Chosen by over 1,000 companies to document their interviews
Operations candidates talk fluently about efficiency, KPIs and continuous improvement. The interview has to get underneath the vocabulary to the actual work: which process, what number, what went wrong when they changed it, who resisted.
The 20 questions below are built for that, grouped by what an operations manager actually does, and each one says what a strong answer contains and what should worry you.
01
Before you ask: what this operations role actually owns
Operations in a warehouse, a SaaS company, a clinic and a restaurant group are different jobs with the same core: process, metrics, cost, people, and things going wrong. Decide which two areas matter most here and pick your follow-ups from those rows. Ask for numbers on every question.
Process and improvement
Metrics and reporting
Cost and vendors
People and cross-team
Incidents
02
Process and improvement
01Tell me about a process you fixed. What was the number before, what was it after, and how did you measure it?
- What a strong answer shows
- A specific process, a baseline they measured themselves, the change, and a result with a number and a timeframe.
- Red flag
- «We improved efficiency» with no baseline and no figure.
02Describe an improvement you made that broke something else. What did you miss?
- What a strong answer shows
- A real second-order effect, how they found out, and a change to how they now test changes.
- Red flag
- Nothing they changed has ever caused a problem downstream.
03How do you decide which process to fix first when everything is inefficient?
- What a strong answer shows
- A criterion (cost, customer impact, effort) applied to a real backlog, and something they deliberately left alone.
- Red flag
- They fix whatever is most annoying to them.
04Tell me about a process you documented. Did anyone use the documentation?
- What a strong answer shows
- Honesty about adoption and what they did to make it stick (training, checklists, embedding it in the tool).
- Red flag
- They wrote a manual and consider the job done.
05Give me an example of a manual task you automated or removed. What did it cost, and what did you do with the time saved?
- What a strong answer shows
- A real task, the cost of the fix, and a concrete use of the freed capacity.
- Red flag
- Automation as a goal in itself, with no accounting of what it saved.
03
Metrics and cost
06Which metrics did you own, and which one changed a decision? Tell me about that decision.
- What a strong answer shows
- Two or three metrics and one specific decision that a number drove — a hire, a vendor change, a stopped project.
- Red flag
- A dashboard nobody acted on.
07Tell me about a cost you cut. How much, what did it affect, and how did you know it did not hurt service?
- What a strong answer shows
- A number, the trade-off they watched, and the service metric they checked afterwards.
- Red flag
- A cut with no idea what it affected, or one that quietly degraded service.
08Describe a time your numbers looked good and the reality was not. How did you find out?
- What a strong answer shows
- Awareness that metrics can mislead, a specific case, and a change to what they measure.
- Red flag
- The numbers are always right.
09How did you handle a vendor or supplier who was underperforming?
- What a strong answer shows
- Data on the failures, a direct conversation, an SLA or a replacement, and the outcome.
- Red flag
- They complained about the vendor for a year.
10Walk me through a budget you managed. Where did you overspend, and what did you do?
- What a strong answer shows
- A real budget, an honest overspend with a cause, and how they corrected or re-forecast.
- Red flag
- Always under budget, or no budget responsibility described as if it were.
04
People and cross-team work
11Tell me about getting another team to change how they worked when you had no authority over them.
- What a strong answer shows
- They understood the other team’s constraint, showed the cost with data, found a trade, and can say what changed.
- Red flag
- «I escalated» as the whole story.
12Describe a change your own team resisted. What was their objection, and were they right?
- What a strong answer shows
- They can state the objection fairly, adjusted the plan where the team was right, and pushed through where they were not.
- Red flag
- Resistance is always the team’s problem.
13How do you know what is happening on the floor or in the queue without being there all the time?
- What a strong answer shows
- A cadence (daily numbers, a short stand-up, a weekly walk) and an example of catching a problem early.
- Red flag
- They find out when something breaks.
14Tell me about a performance problem on your team. How long did it take you to act?
- What a strong answer shows
- Early action, clear expectations, a fair process, and an outcome.
- Red flag
- Months of tolerance.
15Give me an example of a hire you made for your operation. What did you look for, and how did it go?
- What a strong answer shows
- Specific signals they interviewed for, and an honest outcome — including a hire that did not work.
- Red flag
- Every hire has worked out.
05
Incidents and pressure
16Tell me about the worst operational incident you have handled. What did you do in the first hour?
- What a strong answer shows
- Specific first moves (contain, communicate, assign), who they told and when, and the fix afterwards.
- Red flag
- Vague heroics, or the incident was somebody else’s.
17Describe a time demand spiked beyond capacity. How did you decide what to protect?
- What a strong answer shows
- A priority order they can defend, communication to customers or stakeholders, and what they let slip on purpose.
- Red flag
- «We all worked through the night» as the plan.
18How do you run a post-incident review? Give me an example of a change that came from one.
- What a strong answer shows
- A blameless review, a root cause beyond «human error», and a concrete change that stuck.
- Red flag
- The review found who was at fault.
19Tell me about a time you had to tell leadership that a target would be missed. When, and how?
- What a strong answer shows
- Early, with a cause and a revised forecast, and a plan.
- Red flag
- Leadership found out at the end of the period.
20What would your team say is the thing you push hardest on? And what do you let slide?
- What a strong answer shows
- A credible answer on both halves, with self-awareness about the cost of what they let slide.
- Red flag
- They push on everything, or the answer no team member would give.
06
How to score the answers
Score the numbers and the failures. An operations candidate with no baselines, no incidents and no changes that broke anything has either done very little or is not telling you about it. Use the same scale for every candidate and write the figures next to the score.
- 1No evidence
Vocabulary — lean, KPIs, efficiency — with no process named
- 2Thin evidence
A process named, but no baseline, no number, no second-order effect
- 3Solid evidence
A real process, before-and-after numbers, a decision driven by a metric
- 4Strong evidence
Above, plus an improvement that broke something, an incident owned, a team moved without authority
- 5Exceptional
Above, plus a change that stuck after they left
FAQ
Frequently asked questions
What are the best interview questions for an operations manager?
Questions that require a number and a failure: a process they fixed with before-and-after figures, an improvement that broke something else, a cost they cut and how they knew service did not suffer, a metric that changed a decision, the first hour of their worst incident. Vocabulary about efficiency without a named process is not evidence.
How do you assess an operations manager’s analytical skills?
Ask which metrics they owned and for one decision a number drove, then ask about a time the numbers looked good and reality did not. Strong candidates know their metrics can mislead and have changed what they measure because of it. Pair it with a short exercise: give them a real dataset or report and ask what they would do first.
What are red flags when interviewing operations managers?
No baselines or numbers; nothing they changed ever caused a downstream problem; a dashboard nobody acted on; resistance always described as the team’s problem; incidents handled with heroics rather than a method; and leadership learning about misses at the end of the period.
Should the operations manager interview include a case study?
Yes, a short one: a realistic bottleneck from your own operation, described in a paragraph, and thirty minutes to talk through how they would diagnose it. Score the questions they ask and what they would measure first, not whether they reach your preferred answer.
How many questions should an operations manager interview include?
Eight to ten across process, metrics and cost, people, and incidents, with follow-ups, in about an hour. The numbers and the failures usually come out on the second follow-up, so fewer questions asked properly beat a long list.
Stop writing up interviews by hand.
Voicit records the interview, transcribes it and fills your scorecard against the competencies you defined, so you can listen instead of typing.
4.8 out of 5 350+ reviews