Operations manager screening questions: scope, KPIs, people, safety and improvement
On this page
An operations manager screening call should pin down what the candidate ran: how many people, how many shifts, what budget, and which numbers they were measured on. Then ask for one result with a starting point, an ending point and what they changed to get there, plus the worst operational day they handled. Real operators talk in units per hour, on-time percentages, overtime hours and names of shift roles. Inflated resumes say "drove operational excellence" and "improved efficiency by 30 percent" and cannot say 30 percent of what.
"Operations manager" covers plants, distribution centers, service back offices and multi-site field teams, so the first questions place the candidate. This is not the project manager screen, which tests projects with an end date, and for hourly warehouse and production roles use light industrial screening questions.
Place the role: plant, distribution, service or multi-site
| Setting | What the job usually is | Facts to ask for | Common overstatement |
|---|---|---|---|
| Manufacturing plant | Production schedule, labor, quality, maintenance coordination, safety | Lines or cells, shifts, headcount, union or not, output measure, OEE or yield | "Ran the plant" as one of three area managers |
| Distribution or fulfillment center | Inbound, storage, picking, outbound, carriers, peak staffing | Square footage, orders or units per day, WMS, temp labor share, peak volume | Peak-season headcount quoted as permanent team size |
| Service or back-office operations | Claims, orders, customer service processes, SLAs, workforce planning | Transactions per day, SLA targets, team leads, systems | "Operations" meaning they managed a queue report |
| Multi-site or field operations | Several locations through site managers; standard work, audits, budgets | Site count, direct reports, travel, how they measured sites | Regional scope claimed for a project that visited several sites |
| Startup operations | Whatever needs building: vendors, processes, logistics, support | Company stage, what existed before, what they built | Every function claimed, none owned for long |
Scope: people, shifts and budget
Get the numbers early and write them down exactly. They are what the client will compare, and they frame every later answer.
| Question | What a strong answer sounds like | Red flags |
|---|---|---|
| How many people reported to you, directly and through supervisors? | "Four supervisors, one per shift and a maintenance lead; about 120 hourly, plus up to 60 temps in Q4." | A single large number with no structure. |
| Which budget did you own, and what was in it? | A figure and the lines: labor, overtime, temp labor, supplies, maintenance. Who approved capital spending above what limit. | "I managed a 40 million dollar operation," which is the site's revenue, not their budget. |
| Who did you report to, and who were your peers? | A clear picture: GM, with peers in quality, maintenance and HR. | Unclear reporting line. |
| What decisions could you make without approval? | Overtime, schedule changes, hiring within budget, discipline up to a level. | No decision rights at all, for a role that needs them. |
KPIs: the baseline test
Ask: "What three numbers were you measured on? For each one, where was it when you started, where was it when you left, and what did you change?" This one question separates operators from observers faster than anything else on the call.
| Setting | Typical measures | What a strong answer includes | Red flag |
|---|---|---|---|
| Plant | OEE, yield or scrap, schedule attainment, cost per unit, overtime | "OEE went from about 58 to 67 percent on line 2. Most of it was changeover time; we cut it from 90 to 40 minutes." | A percent improvement with no baseline or line. |
| Distribution | Units per hour, order accuracy, on-time ship, dock-to-stock time, cost per order | "Pick rate from 110 to 140 units an hour after re-slotting the fast movers closer to pack." | Credits a new WMS for everything, with no own change. |
| Service operations | SLA attainment, backlog, handle time, first-pass accuracy, cost per transaction | "Backlog from 9 days to 2 by splitting simple claims into a separate queue." | Only activity measures, like calls taken. |
| Any | Turnover, absenteeism, safety rate | A starting rate, an ending rate and the program behind the change. | "Morale improved." |
Follow up on any big number with: "What else changed at the same time?" Volume drops, new equipment and price changes all move metrics. A strong candidate separates their effect from the rest without being asked twice.
People: supervisors, shifts and turnover
| Question | What a strong answer sounds like | Red flags |
|---|---|---|
| How did you run shift handovers? | A fixed format: safety issues, what is behind, equipment status, staffing gaps; written or on a board. | Relied on supervisors to talk to each other. |
| Tell me about a supervisor who was struggling. What did you do? | Specific gaps, coaching, clear expectations, a timeline and an outcome either way. | Removed them with no support, or kept them for years with no change. |
| What was hourly turnover, and what did you do about it? | A number, a cause they found (first-week attrition, a bad shift pattern) and what changed. | "It's just the industry." |
| Did you work with a union? What was your part in grievances or bargaining? | Describes grievance steps they handled and the relationship with stewards. | "Union experience" meaning the site had a contract they never read. |
| How did you staff for peak? | Forecast from volume, temp agency lead times, cross-training, overtime limits, and what they learned from a bad peak. | Hired late every year. |
Continuous improvement claims
Lean and Six Sigma appear on most operations resumes. Ask for one project and walk it end to end: "What was the problem in numbers, what did you measure, what did you change, what was the result, and did it last six months later?"
- Strong: a defined problem ("scrap on the bottling line was 4.2 percent"), data collected, a root cause, a change, a control to sustain it, and a verified result.
- Weak but honest: "I led 5S in the warehouse. It looked better; I didn't measure much." Useful, and honest about its limits.
- Red flag: savings figures with no method: "saved 2 million" with no idea whether finance validated it.
Belts vary. There is no single issuing body, so a Green Belt can mean a weekend course or a company program with projects. ASQ's Certified Six Sigma Black Belt, for example, requires completed projects with signed affidavits and a proctored exam (as of September 2026). Ask who issued the belt and what project it required.
Safety: rates and programs
Ask about the site's safety performance and what the candidate changed. The total recordable incident rate is recordable cases times 200,000, divided by hours worked; the 200,000 represents 100 full-time employees for a year, as the Bureau of Labor Statistics explains in how to compute your firm's incidence rate.
Worked example (invented numbers)
A candidate says the site "had 6 recordables last year with about 150 people."
- Hours worked: roughly 150 × 2,000 = 300,000.
- Rate: 6 × 200,000 ÷ 300,000 = 4.0.
- Now ask: "What was it the year before, and what did you change?"
You are not grading the number against an industry. You are checking that the candidate knows their own site's rate and has a story behind its movement.
- "What was the most serious incident on your watch, and what changed afterwards?" Strong: investigation, root cause, a physical or procedural fix. Red flag: blamed the employee and moved on.
- "How did you handle a supervisor who pushed output over safety?" Strong: a direct conversation and consequences. Red flag: "Numbers come first on a busy day."
- "Do you have OSHA 30?" It is a useful signal, but OSHA states that its 10- and 30-hour cards are completion cards from a voluntary program, not certifications, per the Outreach Training Program page.
Ask about site safety results, not the candidate's own injuries, medical history or workers' compensation claims. Physical requirements for site walking or lifting should be asked the same way of everyone and tied to the job. This is not legal advice; confirm with the client's HR or counsel.
The bad day question
Ask: "Tell me about the worst operational day you managed: a line down, a system outage, a no-show shift, a weather closure." Listen for the order of decisions.
| What to listen for | Strong | Red flag |
|---|---|---|
| First moves | People safe, customers told early, priorities set | Jumped into fixing the machine personally while nobody ran the floor |
| Communication | Who was told, when, and with what estimate | Leadership found out from a customer |
| Trade-offs | Which orders were protected and why | "We got everything out," with no cost mentioned |
| Afterwards | A review and a change that reduced the chance of a repeat | Nothing changed |
Systems, knockouts and scorecard
Ask what systems they used and at what depth: ERP (SAP, Oracle, Dynamics, NetSuite), WMS (Manhattan, Blue Yonder, SAP EWM, or smaller systems), MES or maintenance systems, labor management and scheduling tools, and Excel or BI for daily reporting. "Built the daily production report" tells you more than a list of system names. Then cover shift expectations, on-call, travel between sites, salary and bonus expectations, relocation, notice period and other processes.
Must-ask on every operations manager screen
- Setting, site size, headcount structure, shifts and union status.
- Budget owned and decision rights.
- Three KPIs with baselines, results and the change behind each.
- One improvement project walked end to end.
- Site safety rate and one change they made.
- The worst day and the order of decisions.
- Schedule, on-call, travel, relocation and pay expectations.
Knock out, or flag before submitting, if the candidate cannot give a single baseline for their own results; if their largest team is a fraction of the client's with no supervisor layer; if shift, on-call or relocation requirements are a clear no; or if they describe putting output ahead of safety as normal.
| Area | 1 | 2 | 3 | 4 |
|---|---|---|---|---|
| Scope match | Much smaller, no supervisors | Smaller, some supervision | Comparable | Comparable with multi-shift or multi-site depth |
| Results | No baselines | Results without clear own contribution | Baselines, results and changes | Sustained results, separated from other factors |
| People leadership | Individual contributor | Supervised hourly staff | Led supervisors, handled turnover | Built a supervisor bench and handover system |
| Safety | Unaware of rate | Knows rate, no program | Knows rate and one change | Measurable improvement with lasting controls |
| Logistics fit | Deal-breaker | Two open questions | One open question | All aligned |
Next to each score, write the evidence as said: "Pick rate 110 to 140 UPH after re-slotting; 4 supervisors, about 120 hourly." Interview Signal builds the scorecard with quotes like that from the call. For planning and inventory roles that feed operations, see supply chain analyst screening questions.
Questions people ask
What should an operations manager be able to tell you on a first call?
Their headcount, the budget they controlled, the three numbers they were measured on, where those numbers started and ended, and one bad day they handled. A candidate who cannot give baselines for their own results usually did not own them.
Is a Six Sigma belt a reliable signal?
It depends on who issued it. There is no single governing body, so belts range from short online courses to ASQ's Black Belt, which requires completed projects with signed affidavits and a proctored exam. Ask about the project, its baseline and its result, and who signed off.
Can I ask about a candidate's safety record?
Ask about the site's safety performance and what the candidate changed, not about their personal injuries or workers' compensation claims. Site recordable rates and the programs they ran are fair and job related.
How is an operations manager screen different from a project manager screen?
A project manager delivers something with a start and an end. An operations manager runs something that repeats every shift. So the operations screen focuses on recurring metrics, staffing, shift handovers and continuous improvement rather than scope, milestones and change requests.