Questions to Ask a Vice President of Operations
Questions for a panel interviewing a candidate for vice president of operations, covering the real size of what they have run, how they set cadence and metrics, where they cut cost without breaking service, and what they did during the worst week of their career.
20 questions, each with the reason to ask it · includes a conversation guide
The questions
Open any question to see why it works.
- 1
Walk me through the operation you ran: headcount, sites, budget, and what it produced.
Scope has to be established first because titles inflate freely. A VP over three plants and four hundred people and a VP over one team of twelve both carry this title, and the two jobs share almost nothing.
- 2
What did you inherit when you started, and what did it look like when you left?
Forces a before and after rather than a list of duties. Strong candidates volunteer two or three numbers without being asked. Weaker ones describe processes they maintained without saying what actually changed.
- 3
Which parts of the operation did you own outright, and which did you influence?
Operations leaders routinely absorb credit that belonged to supply chain, finance or a site manager. The distinction is not a trap: candidates who draw it themselves are usually the more credible ones in the room.
- 4
How do you decide what to measure?
Anyone can list KPIs. The useful answer explains why those and not others, and names a metric they retired because it was driving bad behavior. Removing a metric is a stronger signal than adding one.
- 5
What did your weekly operating rhythm look like?
Ask for the actual calendar: which meetings existed, who attended, and what decision each one produced. Operations runs on cadence, and a candidate who cannot describe theirs probably ran the job reactively.
- 6
Tell me about a cost reduction you made that did not hurt service.
The follow-up matters more than the story: how did they know service held? If there is no measurement in the answer, the cost most likely came out of quality and somebody else absorbed the complaints.
- 7
Where have you cut something and regretted it?
Nearly every operations leader has overcut maintenance, training or a shift of headcount at some point. Naming it and describing how they found out shows judgment rather than a rehearsed set of wins.
- 8
How do you handle a supplier or vendor that is failing you?
Listen for whether they escalate, dual-source, renegotiate or exit, and for how long they wait before doing it. A candidate who has never ended a vendor relationship has been lucky or has avoided a hard conversation.
- 9
Describe the worst operational week you have been through.
A recall, an outage, a walkout, weather, a system migration that failed. You are listening for what they did in the first six hours and who they told, because that is how they behave when there is no plan.
- 10
How do you tell the difference between a process problem and a people problem?
A common failure mode is disciplining people when the process guarantees the error. Good answers involve going to watch the work happen rather than reading a report about it.
- 11
What is your approach to safety, and what have you changed because of an incident?
Ask this wherever there is physical work. The answer should contain something specific and unflattering. Generic commitment language usually means safety has been delegated and is not being measured by them.
- 12
How do you build a bench underneath you?
A VP of operations is judged partly on whether the operation runs when they are on a plane. Ask who they promoted, where those people are now, and what they did about a strong performer who was not ready yet.
- 13
How have you handled a site or team leader who was not performing?
You want a timeline: when they knew, how long they gave it, what support came first. Moving too fast burns trust across the whole org, and waiting a year costs more than the underperformance did.
- 14
How do you work with finance?
Operations and finance is where forecast arguments happen. A good answer talks about shared assumptions and forecast accuracy. A weaker one is about defending a budget from people who do not understand the floor.
- 15
What systems or automation have you implemented, and what did they actually deliver?
Almost every candidate has an implementation story. Ask about adoption and how many people were still running workarounds a year later, because that is where implementations quietly fail.
- 16
How do you plan capacity when the demand forecast is unreliable?
This is the daily reality of the job. Look for buffers, flexible labor and a stated tolerance for carrying cost, rather than a claim that they simply made the forecast accurate.
- 17
What would your former direct reports say is frustrating about working for you?
Phrased so that deflection is awkward. Credible answers are specific and mildly costly to admit: too far into the detail, changes direction quickly, unreachable during a crisis.
- 18
In your first ninety days here, what would you look at before changing anything?
Tests whether they arrive with a template. A strong answer names what they would go and see in person and who they would talk to, and resists promising a restructure before understanding the constraints.
- 19
Based on what you know so far, where do you think our operation is weak?
Asked late, this separates candidates who researched the business from candidates who prepared answers. You are also watching how they deliver criticism to the people who own the thing being criticized.
- 20
What kind of operation do you not want to run?
A quiet question that prevents an expensive mismatch. Someone who thrives on turnaround work will be restless in a stable business, and someone who wants stability will suffer in one that is scaling fast.
Interviewing for this role
Practical guidance for the conversation itself.
Setting up the panel
Setting up the panel
- Decide in advance which of the three common versions of this job you are hiring for: scaling, turnaround, or steady-state efficiency. Candidates who are excellent at one are often mediocre at another.
- Put a site leader or plant manager on the panel. They will hear whether the candidate has actually run an operation within about ten minutes.
- Include finance. The working relationship between operations and finance is the one most likely to determine whether the hire succeeds.
- Give the candidate real numbers before the final round and ask what they would do with them. Case discussion beats behavioral questions for this role.
- Agree who asks about safety and compliance. It is the topic panels most often assume somebody else covered.
Reading the answers
Reading the answers
- Watch the pronouns. Sustained use of we with no detail about their own decisions usually means they were adjacent to the results.
- Ask for a number, then ask how it was calculated. Candidates who cannot reconstruct their own metric were reading someone else's dashboard.
- Good operators talk about constraints before they talk about goals. If every answer starts with a target and none mention a bottleneck, probe harder.
- Note whether they describe going to see the work. Operations leaders who manage entirely from reports tend to be surprised by their own operations.
- Be suspicious of a candidate with no failures. Any real operation produces them, and hiding them in an interview predicts hiding them later.
What to check afterward
What to check afterward
- Ask references for the scope numbers separately and compare them with what the candidate told you. Discrepancies here are common and telling.
- Speak to at least one former direct report, not only former managers. The report knows how decisions felt from underneath.
- Ask a reference what the candidate was like in a crisis, and then ask for the specific crisis.
- Confirm what happened to the operation after they left. A performance that decayed within months is worth understanding rather than assuming.
- Ask a reference what kind of environment they would not put this person into. It is the question that gets the most useful hesitation.