What Operations Manager Interviews Actually Test

Who actually sits across the table

For an operations manager role, the panel is rarely just HR. Expect the hiring manager (a site director, operations director, or COO depending on seniority), often a peer operations manager from another site or shift, and sometimes a finance business partner if the role carries budget or P&L ownership. In manufacturing, warehousing, and logistics, it's common for a shift or production supervisor to sit in on part of the process, and for the interview to include a walk of the floor rather than staying in a meeting room the whole time.

The process is usually staged: a screening call, a panel interview, and then either a case study or a site visit, sometimes as a separate round. If the advert mentions a specific site, expect to be walked through it.

The exercise you actually get given

It's rarely a generic "tell me how you'd solve this" case study. The common formats are more concrete:

• A KPI dashboard extract — OTIF, first-pass yield, absence rate, cost per unit — with one metric moving the wrong way, and you're asked to talk through root-cause diagnosis live, sometimes on a whiteboard.
• A scheduling or capacity problem: given shift patterns, current headcount, and a demand spike, you allocate resource and justify the trade-offs out loud.
• A written case sent 24–48 hours in advance covering something like a supplier failure, an SLA breach, or a health and safety incident, with a short plan or slide to present back.
• A site walk, where you're taken round the floor or warehouse and asked what you notice — a blocked fire exit, a work-in-progress pile-up at one station, a missing piece of PPE, a bottleneck that's obvious once you're standing in front of it. This tests observation and immediate prioritisation, not memorised theory.

If you're told there's a "practical element" and given no further detail, it's worth asking directly whether it's a desk exercise or a floor walk — the preparation is different.

The questions that are actually testing something

A few questions come up in almost every operations manager interview, and each one is doing more work than it looks like:

• "Walk me through a KPI you owned that went the wrong way, and what you did in the first 48 hours." This separates people who can run a structured root-cause process — five whys, a fishbone diagram, pulling the right data first — from people who jump straight to a solution without diagnosing anything.
• "Tell me about a time a deadline and a safety or compliance issue collided." This is checking whether you'll actually stop a line or process when you need to, and whether you know the reporting obligations that apply — RIDDOR, COSHH, whatever's relevant to the site — rather than just saying safety comes first.
• "How do you run a shift handover or daily stand-up?" This is looking for a real cadence — tiered meetings, gemba walks, a specific handover sheet — not "I communicate well with my team."
• "Describe a time you managed a budget variance." This tests whether you actually know the cost levers — labour versus overtime, cost per unit, which line items you control versus which are fixed — or whether you've only ever watched a dashboard someone else built.
• "Tell me about a supplier or vendor that let you down." This is about SLA enforcement and escalation — do you have a mechanism for holding a vendor to account, or do you just absorb the disruption and move on.
• A live scenario along the lines of: "Volume has just gone up sharply and two people are off sick — what do you do in the next hour?" This tests prioritisation under a real constraint, not the theory of prioritisation.
• "What ERP or WMS have you used — SAP, Oracle, NetSuite, Manhattan?" followed by "how did you use it to build the shift schedule" or "how did you use it to track shrinkage." This tests hands-on fluency, not whether you recognise a product name.
• Questions about direct reports — managing out an underperformer, handling someone who won't follow a new process — testing real people management rather than a conflict-avoidance answer.

What a shallow answer sounds like

To someone who does this job, a few patterns give away a rehearsed or thin answer immediately:

• Naming a framework — Lean, Six Sigma, Kaizen — without describing one specific process you changed and what actually happened to the numbers afterwards.
• Describing "leading a team of X people" with no detail on shift patterns, absence handling, or how communication actually runs day to day.
• On the KPI question, going straight to "I'd talk to the team" without saying what data you'd pull first or what the metric is actually measuring.
• On the safety question, saying "safety is always my priority" with no description of an actual procedure — who gets notified, what the paperwork is, what happens to the process while it's under investigation.
• Claiming P&L ownership but being unable to say what the cost per unit or labour percentage actually was, or which costs you controlled versus which were fixed above you.
• Answering the systems question with a tool name and nothing else — "yes, I've used SAP" — rather than which module, and what you did in it beyond logging in.

Most experienced interviewers only follow up once. If the follow-up produces a name, a number, or a specific decision, the original answer was real. If it produces another abstraction, it wasn't — and that's usually the moment the interview effectively ends, even if it continues for another twenty minutes.

What to do before you go in

Have three or four incidents ready, each with a number attached: a KPI you moved, a cost you cut, a headcount problem you solved, a compliance issue you handled and how. Know the exact systems you've used and one thing you did in each beyond logging in. If the advert names a specific tool, a certification such as CPIM or a Six Sigma belt, or a regulation, expect a direct question on it — don't claim more familiarity than you have, because the follow-up question will find the gap. If there's a site visit, look for what an operations manager would look for anywhere: bottlenecks, safety, and whether the shift handover looks organised or chaotic — and be ready to say what you'd check first.

If the harder problem right now is not the interview but getting to one at all — sending applications into adverts and hearing nothing back — that's a different problem with a different mechanism. jobmarket.pro is an agent that reads each advert in full, explains where a candidate's actual experience fits and where it doesn't, and prepares the application from one profile it cannot invent experience into.