Interview guide for operations roles: a full loop with a floor walk and a KPI case

Operations managers are hired to keep output, cost, quality and safety on target while demand moves around them. The interview loop has to show how a candidate reads a running operation, finds the cause behind a bad number, plans people against volume, and leads the supervisors who do the daily work. This guide gives hiring managers a complete loop for an operations manager at a distribution or fulfillment site: five stages, who owns which competency, core questions with what to listen for, a floor walk and a KPI case, the scorecard weights, and the debrief decision rule. An office-based version is at the end.

The recruiter's first call is in operations manager screening questions. This page is everything from there to the hiring decision.

The loop at a glance

Stages 3 to 5 fit into one site visit of about three hours. Schedule it during a working shift so the floor walk sees real activity.

Stage 1: the screen (30 minutes)

• "Describe the operation you run now: volume, headcount, shifts, and the three numbers you report every week." Listen for: numbers given without hesitation and metrics that cover output, cost, quality and safety, not only one.
• "How many supervisors or leads report to you, and how did you get them?" Listen for: hiring and developing leads, not only inheriting them.

Stage 2: hiring manager interview (45 minutes)

1. "Tell me about your last peak season or volume spike. How did you plan labor and space for it?" Listen for: a forecast they used and questioned, a staffing plan with temporary labor or overtime trade-offs, and what they would change after seeing the actual volume.
2. "Tell me about a time output and safety pulled in different directions." Listen for: stopping or slowing work when needed, explaining the decision upward, and fixing the condition rather than only reminding people to be careful.
3. "Which of your metrics was hardest to move, and what finally moved it?" Listen for: a root cause they found, a specific change, and a result sustained over months rather than one good week.

Stage 3: the floor walk (45 minutes)

The site manager walks the candidate through receiving, storage, picking, packing and shipping on a fixed route for 30 minutes. The guide explains what each area does and answers questions, but does not point out problems. Afterward, 15 minutes seated:

• "What three things did you notice?"
• "Which one would you look into first, and how would you check whether it is a real problem?"
• "What would you not change in your first month, and why?"

Listen for: observations about flow (where work waits, where people walk or search, where items are touched twice), safety conditions, and visual management; a plan to check with data or by asking the people doing the work before changing anything; and restraint about changing things they do not yet understand. Score observation and reasoning, not whether they found the problems you already know about.

Stage 4: the KPI case (45 minutes)

Give the candidate a one-page invented weekly report for the last eight weeks: units shipped, on-time shipment rate, overtime hours, pick error rate, headcount including temporary staff, and two lines of notes (a new carrier started in week four; a warehouse system update in week six). On-time shipments have fallen and overtime has risen.

• 10 minutes alone with the sheet.
• 20 minutes discussing: "What do you think is going on? What would you check first? What would you do this week, and what next month?"
• The pushback at minute 30: the finance partner says, "We cannot add headcount. What else?"
• 5 minutes out of role: "What information is missing that you would want?"

Listen for: separating symptoms from causes, connecting the timing to the notes (carrier change, system update, rise in temporary staff) as hypotheses to test rather than conclusions, a short-term action and a longer fix, and options other than headcount under the constraint. More on structuring this kind of stage is in how to interview for problem solving.

Stage 5: supervisor conversation (30 minutes)

• "Tell us about a supervisor of yours who was struggling. What did you do?" Listen for: time on the floor with them, specific feedback, and a clear outcome either way.
• "How do you find out what is really happening on a shift you are not on?" Listen for: shift handovers, walking the floor at different times, asking frontline staff directly, and checking data rather than relying on one source.
• "Tell us about a time another department's decision caused problems for your team." Listen for: raising it with facts, finding a fix with the other team, and protecting their own team without blaming.

Briefing the interviewers

Operations interviewers are often pulled off the floor to interview, so give each a one-page brief the day before: the competencies they own, their questions with probes, the scorecard, and what not to ask. The site manager running the floor walk gets the fixed route and an instruction not to point out known problems. The supervisors get a reminder that questions about family, childcare or health are off limits, even when asked in a friendly way about shift patterns; the recruiter has already confirmed the candidate can work the schedule. Everyone writes evidence in the candidate's words and submits before talking to the others.

Scorecard competencies and weights

Example weights for a site operations manager. Set yours at intake.

Print the sheet for the panel from the scorecard builder; it confirms the weights add up to 100.

The debrief decision rule

1. Scorecards with evidence are submitted before the debrief, which happens within two working days of the site visit.
2. Gate: operational problem solving at 3 or above.
3. Floor: no 1 on safety mindset. Weak safety judgment is not offset by productivity strengths.
4. Weighted total: in this example, 2.8 or higher on the 1–4 scale moves to references.
5. The supervisors' view on people leadership carries weight: if they score it 2 and the director scores it 3, read their evidence first; they are the ones who would report to this person.

Adjusting the loop

Common mistakes in operations loops

• Hiring on industry jargon. Knowing the terms is not the same as finding causes. The KPI case separates the two.
• No frontline input. The supervisors know within minutes whether someone could lead on the floor.
• A site visit on a quiet day. An empty floor tests nothing. Schedule during a shift.
• Rewarding the candidate who would change everything. Big first-week plans for a site they have seen for 30 minutes are a risk, not a strength.