Operations manager interview questions and answers (UK, 2026)
The KPI, process improvement and incident questions UK operations manager interviews really ask, with answer structures built on measured results.
What interviewers are really assessing
The interviewer, usually a site lead, head of operations or regional manager, is testing whether you run operations by numbers and systems or by firefighting and presence: both types exist, and they are hiring the first. Expect every claim to be pushed for its measurement ("productivity improved: from what to what, over when?") and at least one incident scenario, because how you behave when a supplier fails or a safety issue surfaces is the job. Many processes include a site walk-around where your observations are themselves assessed: what you notice about flow, housekeeping and safety says more than an hour of answers. Lean or CI language helps only when attached to a real result.
Operations Manager interview questions and model answers
For each question: why it is asked, and the structure of a strong answer. Adapt the worked examples to your own experience; interviewers follow up, so never borrow a story.
1. Which KPIs did you own, and what did you actually do to move them?
Why they ask it: It separates managers who owned outcomes from managers who watched dashboards someone else moved.
Name the numbers and the mechanism: for example, owning OTIF (on-time-in-full), cost per unit and labour productivity across a 60-person operation, and lifting OTIF from 91 to 96 percent by fixing the two failure sources the data showed, a pick-face replenishment gap in peak hours and a carrier cut-off missed on Fridays. The structure is metric, baseline, action, result, and interviewers discount any improvement without a named mechanism behind it.
2. Tell me about a process you improved. Walk me through it.
Why they ask it: Continuous improvement claims are universal, and this question tests whether yours have method and measurement behind them.
Use a simple improvement arc: how you identified the problem (data plus going to watch the process), root cause, the change, and the measured result with sustainment. A worked sketch: returns processing was taking eleven days; mapping the flow showed items queuing three times for one inspection, so you moved triage to goods-in and cut the cycle to four days, holding it there with a daily volume board. Mentioning what you tried that did not work first adds credibility rather than subtracting it.
3. A key supplier fails on the morning of your busiest day. What do you do?
Why they ask it: Disruption response is the core scenario of operations, and interviewers want sequence and calm, not heroics.
Sequence it: contain (size the impact in hours and orders, communicate to affected customers and your own leadership early), work the alternatives (buffer stock, an approved second supplier, re-sequencing production to push affected lines later), then recover and prevent: a supplier review, dual sourcing for critical inputs, and a trigger-based escalation added to the playbook. A real example with numbers ("we saved 80 percent of that day's orders") beats a textbook answer, so use one if you have it.
4. How do you handle a team member underperforming on shift?
Why they ask it: Operations standards die quietly when managers walk past underperformance, and panels probe for both fairness and follow-through.
Diagnose before acting: is it training, equipment, the process, or something at home, established in a private conversation rather than a public correction. Then the structure: clear expectation, support (retraining, a buddy, adjusted duties where warranted), a review date, and formal process with HR if it does not move. A worked sketch: a picker at 60 percent of rate turned out to have never been trained on the scanner shortcuts; two coaching sessions took them past standard. Panels want the fairness and the spine together.
5. Walk me through how you plan and run a peak period.
Why they ask it: Peak execution is where operations managers earn their salary, and planning depth is instantly audible.
Cover the planning arc: volume forecasting with the commercial team, labour plan (overtime, agency ratios, cross-training started weeks early so temporary staff are productive on day one), equipment and space capacity, daily rhythm during peak (start-of-shift briefs, hourly tracking against plan, an escalation trigger), and the post-peak review. A worked sketch: planning a November peak at 2.4 times normal volume, onboarding forty agency staff in two waves, and exiting peak with OTIF above 94 percent. Numbers make this answer.
6. Tell me about a safety issue you dealt with.
Why they ask it: Safety culture is tested here: interviewers listen for whether production pressure ever outranks safety in your answers.
Pick a real event and show the full arc: immediate action (stop the job, make the area safe), investigation to root cause rather than blame, the fix, and the culture layer: near-miss reporting you encouraged, and what you did when reporting rates were low, since low reporting means hiding, not safety. A worked sketch: a near-miss with a reversing FLT led you to redesign the pedestrian segregation and add a one-way system, and near-miss reports doubled once people saw action follow reports. Any hint that you would keep the line running around a hazard fails the interview.
7. You are asked to cut operating costs by ten percent without hurting service. Where do you look?
Why they ask it: Cost pressure is permanent, and the question separates managers who cut waste from managers who cut capability.
Show a hierarchy: waste first (rework, overtime driven by poor planning, agency premiums, damage and shrinkage), then alignment (matching labour rosters to the actual demand curve rather than a flat pattern, renegotiating carrier and consumable contracts), and only then structural options, with headcount as a last resort because it usually costs service. Anchor with a number: rostering to the demand curve took labour cost per unit down 8 percent without a single redundancy. Saying explicitly what you would protect (training, maintenance, safety) is part of the correct answer.
8. Why operations, and why this site or business?
Why they ask it: Operations leadership is relentless, and interviewers check your motivation survives contact with 5am starts and peak weeks.
Anchor the motivation in the real texture: the daily scoreboard, making a complex system run better than yesterday, building shift teams that take pride in the numbers. Then show site homework: their network, their growth or automation plans, the specific challenges of their sector (seasonality, cold chain, e-commerce returns), and what you would want to get hold of first. Naming something you noticed, from the advert or a site visit, lands better than general enthusiasm.
Questions to ask them
Asking nothing reads as low interest. These three work because they show you understand the role’s reality, and their answers tell you whether you want the job:
- What do the site's current KPIs look like against target, and which one keeps you up at night?
- What is the labour model here: core versus agency ratio, and how is the relationship with the agency working?
- What investment is planned for the site: automation, systems, or layout changes I would be delivering?
Practise out loud, not in your head
Reading model answers feels like preparation, but interviews are spoken: the first time you say an answer aloud should not be in the room. Rehearse each story out loud until it flows without sounding scripted. If you want a realistic run-through, Vouch’s AI coach Maya runs voice mock interviews built from a real job advert and your own CV, and gives feedback per question, which is the closest thing to the actual experience you can do from your sofa.
And since a strong interview starts with getting invited: the free cover letter generator writes a UK-format letter from your real experience, and the UK personal statement guide covers the 50-80 words at the top of your CV that decide whether it gets read.
Frequently asked questions
How should I prepare for an operations manager interview?
Prepare your numbers: the KPIs you owned with baselines and results, one process improvement with before-and-after figures, and stories for a supplier failure, a safety issue and an underperformer. Research the site and sector: volumes, peak patterns, automation level. If there is a site tour, treat it as live assessment: comment on flow, housekeeping and safety like the manager you would be.
What format do UK operations manager interviews take?
Typically a screen, then a competency interview with the site lead or head of operations, often combined with a site walk-around where your observations are assessed in context. Larger employers may add a data exercise (analysing a set of site KPIs and presenting actions) or a panel with HR and a peer manager. Expect every improvement claim to be probed for its baseline, mechanism and measurement.
How do I answer the salary question in an operations manager interview?
Anchor to scale: pay tracks the size of the operation (headcount, sites, budget), so state your current scope alongside your expectation: "I run a 60-person, two-shift operation and I am targeting the low fifties for a role of this size". Ask about the bonus structure and what it is gated on, since site KPI bonuses are common, and shift patterns and call-out expectations are part of the real package.