Operations Manager interview kit: questions and rubric

How to use this kit

1. Agree the competencies with the hiring manager before the job is posted.
2. Give each interviewer one or two competencies, so nothing is asked twice.
3. Ask every candidate the same core questions; follow up freely.
4. Rate each competency against the anchors straight after the interview, alone.
5. Debrief on quotes, not adjectives, then decide with the rule at the end.

First-round screen

Fifteen to twenty minutes, by phone, video or a disclosed AI screen. The aim is to confirm the basics before the panel spends its time.

1. What draws you to this role, and what kind of operation do you want to run next?
2. Tell me about the operation you run today: what it delivers, how big the team is, and which numbers you are measured on.
3. This role covers the sites, shift pattern and travel set out in the job description. Do those work for you?
4. What is your notice period, and what compensation range are you expecting?

1. Tell me about a process you improved. What was wrong, how did you find out, and what changed?

   Follow up with

   • How did you measure before and after?
   • How did you make the change stick?
   • Who resisted, and why?
   Strong answer

   Names the process and a measured problem (cycle time, errors, cost), found the root cause by watching the work and reading the data, made the change with the people who do the work, and gives before-and-after numbers and how the gain was sustained.

   Weak answer

   Describes a new tool or a reorganization with no measured problem or result, or an improvement that faded once they moved on.

2. Work sample: here is a simple process map and a week of volume and error data from an order-processing team. Where would you look first, and what would you do in the next two weeks?

   Follow up with

   • What would you want to see on the floor before deciding?
   • What quick change would you try, and how would you know it worked?
   Strong answer

   Spots the bottleneck or the source of errors in the data, asks to watch the work, proposes a small, testable change with a measure, and plans to involve the team.

   Weak answer

   Proposes a big restructure or new software at once, or reads the data without wanting to see the work.

1. Tell me about a supervisor or team lead you developed. What did you do?

   Follow up with

   • What did they struggle with at first?
   • How did you know they were ready for more?
   Strong answer

   Names the person's starting point, the specific coaching and stretch responsibilities they gave, and observable growth such as running a shift alone or leading an improvement.

   Weak answer

   Talks about development in general terms, or the person grew with no clear part played by the manager.

2. Tell me about a time you had to deal with repeated lateness or absence in your team.

   Follow up with

   • How did you find out the cause without prying?
   • How did you keep it consistent with how you treat everyone else?
   Strong answer

   Spoke privately and early, set clear expectations in line with policy, offered reasonable support, documented the conversations, and applied the same standard to everyone.

   Weak answer

   Let it run until it became a crisis, handled it publicly, or treated favorites differently.

3. What would you do if a well-liked, high-performing team lead was found bending a safety or quality rule to hit targets?

   Follow up with

   • What would you say to the rest of the team?
   Strong answer

   Stops the practice at once, addresses it with the lead directly and in line with policy regardless of their results, and checks whether the targets created the pressure, then fixes that too.

   Weak answer

   Lets it go because of the results, or punishes the individual without examining the target that drove the behavior.

1. Which three numbers did you look at every day in your last role, and why those?

   Follow up with

   • Tell me about a time one of them moved and you acted.
   • Which of them could be gamed, and how did you guard against that?
   Strong answer

   Names specific measures tied to the operation's goals, explains why each matters, describes a change that triggered action, and knows how each measure could mislead.

   Weak answer

   Names generic measures with no link to decisions, or describes acting on numbers they did not understand.

2. Your service level fell below target last week with no change in volume. What do you investigate?

   Follow up with

   • What would you tell your stakeholders while you investigate?
   Strong answer

   Checks staffing and schedule adherence, handling time, system problems, new joiners and any change in how the number is calculated, then acts on the cause.

   Weak answer

   Tells the team to work faster, or adds overtime without diagnosing anything.

1. Work sample: next month's volume is forecast 25% above this month, with no extra hiring budget. Here is the current staffing and shift plan. How would you plan for it?

   Follow up with

   • What would you tell your stakeholders, and when?
   • What would you stop doing?
   Strong answer

   Quantifies the gap, combines options (shift changes, cross-training, deferring lower-priority work, overtime within limits, a budget request backed by numbers), names the risks, and tells stakeholders early what service to expect.

   Weak answer

   Relies on overtime alone, or promises the same service level with no plan for the gap.

2. Tell me about a time you had to choose between two urgent priorities with the same people. How did you decide?

   Follow up with

   • Who did you consult?
   • How did you tell the side that lost out?
   Strong answer

   Weighed the impact on customers, cost and risk, consulted the right people, made the call, and told everyone affected clearly and early.

   Weak answer

   Tried to do both and did neither well, or let whoever shouted loudest decide.

1. Tell me about a serious operational failure you handled, such as a missed shipment, a system outage or a supplier failure.

   Follow up with

   • What did you do in the first hour?
   • Who did you tell, and how?
   • What changed afterwards so it would not happen again?
   Strong answer

   Contained the impact first, brought in the people needed, communicated early and factually to affected customers and leadership, then ran a root-cause review and changed the process.

   Weak answer

   Describes personal heroics with no communication, blames another team, or stops at the fix without preventing a repeat.

2. What would you do if sales promised a key customer a delivery date your operation cannot meet?

   Follow up with

   • What would you say to the sales lead?
   • What would you change afterwards?
   Strong answer

   Confirms the facts, talks to the sales lead quickly, works out what is possible, agrees with sales how to tell the customer early with an alternative, then fixes the hand-off so promises are checked.

   Weak answer

   Lets the date fail and blames sales afterwards, or breaks safety or quality rules to meet it.

Never ask

• Don't ask a candidate's age, or whether they are comfortable managing people older than them. Why: age says nothing about operational skill, and age-based decisions are unlawful in many places.
• Don't ask about marital status, children, pregnancy or family responsibilities to judge whether they can handle long hours or travel. Why: none of it is job-related. Describe the hours and travel and ask every candidate whether they can meet them.
• Don't ask about religion, caste, community or the origin of a surname, directly or by proxy ('What does your father do?'). Why: in India these questions signal caste and religion, which have no bearing on the job.
• Don't ask 'Where are you from originally?' or 'What is your native place?'. Why: it invites judgments about region and community. If location matters, ask whether the candidate can work from the sites in the job description.
• Don't ask about health conditions, disabilities or past medical leave. Why: the only relevant question is whether the candidate can perform the essential functions of the job, such as being on the floor for a full shift, with or without reasonable accommodation.
• Don't ask for salary history where the law restricts it, as many US states and cities do. Why: it carries past pay gaps into the new offer. Ask for the expected compensation range instead.
• Don't screen on an MBA, a college tier or a particular company name as a proxy for operational skill. Why: many strong operations managers rose from the floor. The case exercises show the skill directly.

Questions people ask

Should operations manager interviews include a case exercise?

Yes, a short one built from your real operation: a process map, a week of data, a staffing plan. It shows how the candidate diagnoses before acting. Keep it to 30 to 45 minutes inside the interview rather than a take-home.

Should we walk the floor with the candidate?

Where you can. A short walk through the operation, followed by 'What did you notice?', shows how the candidate observes work. Rate it against the process-improvement anchors, not on rapport.

How do we compare candidates from different industries?

Focus on the transferable evidence: improving a process with measured results, leading front-line teams, planning capacity and handling failures. Industry knowledge can be learned. Require it only if the job truly needs it from day one, and say so in the job description.

Who should interview an operations manager?

The hiring manager, a peer from a function the role works with daily (sales, finance or supply chain), and, where possible, a supervisor who would report to them. Give each a distinct competency and the same written anchors.