Questions to Ask a Director of Operations
Questions for interviewing a director of operations, covering what they have actually owned, how they diagnose a broken process, headcount and cost decisions, vendor failures, the metrics they trust, and how they behave in a bad week.
20 questions, each with the reason to ask it · includes a conversation guide
The questions
Open any question to see why it works.
- 1
What does operations own where you are now, and what sits outside it?
The title covers wildly different jobs, from running a warehouse to owning every internal process in a company. The boundary they draw tells you which one they have done, and whether it matches the scope you are hiring for.
- 2
What do you look at every Monday morning?
Ask for the actual screen or spreadsheet. Someone who runs an operation can list four or five numbers without pausing, and the ones they name first are the ones they manage by rather than report on.
- 3
Tell me about a process you inherited that was broken. What did you find, and what did you change first?
The sequencing is the test. Strong operators start by watching the work and talking to the people doing it, while weaker candidates start by rewriting the documentation or buying a tool.
- 4
How do you decide whether to fix a process or replace it?
Both answers can be right, so listen for the criteria: volume, error rate, how much the current system is load-bearing, and what the team can absorb. A candidate who always replaces is expensive and a candidate who never does is why you are hiring.
- 5
How many people have reported to you, directly and through managers?
Managing managers is a different job from managing individual contributors, and the step is where operations leaders most often stall. If they have only run a flat team, ask how they would handle a layer they cannot observe directly.
- 6
Tell me about a time you took cost out without reducing output.
Expect a specific number and a specific mechanism, such as renegotiating a contract, changing a shift pattern, or removing a step. Answers that reduce cost purely by cutting headcount are a different skill and should prompt a follow-up about what happened to quality afterwards.
- 7
How do you set staffing for a team whose volume swings?
This separates people who plan from people who react. Good answers involve forecasting, cross-training, a flexible layer of temporary or part-time capacity, and an explicit decision about how much overtime is acceptable.
- 8
How do you choose vendors, and how do you manage them once they are in?
Selection is the easy half and everyone has a story about it. Push on the management half: scorecards, review cadence, and what leverage they keep, since a vendor with no consequences will drift.
- 9
Tell me about a supplier or vendor that failed you. What did you do in the first forty-eight hours?
You are testing triage under time pressure. Look for a sequence that includes containing the customer impact, finding an alternative source, and telling people internally early rather than hoping it resolves quietly.
- 10
What have you automated, and where did automation not pay off?
The second half is the one that matters, because everyone can list a success. Candidates who can describe a tool that cost more to maintain than the manual process have learned something most operators only learn once.
- 11
How do you handle a manager who is well liked but running a poor operation?
This is the most common hard problem in the role and the answer is rarely rehearsed. Watch for whether they distinguish between a capability problem and a standards problem, and whether they have actually done it or are describing what they would do.
- 12
What is your working relationship with finance, and have you ever been wrong about a number in front of them?
Operations leaders who own a budget have been wrong at least once, and admitting it is a good sign. Follow up on what they changed in how they produce numbers afterwards, which is where the real answer is.
- 13
Where does operations rub against sales in your company, and give me a recent example?
Every business has this friction, usually around promises made on delivery dates or custom work. A candidate who says there is no tension either has no visibility or is avoiding the question, and both are worth probing.
- 14
What safety, quality, or compliance responsibility have you personally carried?
Ask what they were accountable for by name, not what existed at the company. In regulated or physical operations this is the part of the job that produces the worst outcomes when someone treats it as paperwork.
- 15
Tell me about a time you were the person saying no.
Operations is often the function that has to refuse a deadline or a shortcut. Look for whether they said no with an alternative attached, and how the relationship survived it, since the second part predicts how they will work with your other leaders.
- 16
What would your first ninety days here look like?
A credible plan front-loads listening and small visible fixes and leaves the big restructure until later. Be cautious about anyone who arrives with a full reorganization designed before they have seen the operation run.
- 17
What would people who reported to you say frustrated them about you?
The phrasing makes it harder to give a disguised strength. Useful answers are specific and slightly costly to admit, such as moving too fast, over-measuring, or getting into detail that belonged to someone else.
- 18
What is a metric you used to trust and stopped trusting?
This is the clearest signal of an operator who thinks rather than inherits. Expect something like utilization, average handle time, or on-time delivery measured in a way that could be gamed, plus what they replaced it with.
- 19
What part of this work do you not want to do anymore?
Everyone at this level is running from something, and knowing what it is tells you whether your role contains a lot of it. An honest answer here is also a fair predictor of how long they will stay.
- 20
What would have to be true for you to still be here in three years?
It asks for their conditions rather than their intentions, which is a much more useful thing to hear before an offer. If nothing they name exists at your company, you have learned that now instead of at their exit interview.
Interviewing for the operations chair
Practical guidance for the conversation itself.
What the role actually is
What the role actually is
The title hides three different jobs
Director of operations can mean running physical operations such as a plant, warehouse, or field team, running business operations such as process, systems, and reporting, or being the general manager for everything the founders stopped doing. Decide which one you are hiring before you write the questions, because the strongest candidate for one is often a poor fit for another.
Scope is more informative than title history
Ask about budget owned, headcount managed, and what decisions they could make without approval. A director at a small company often has broader scope than a director inside a large one, and the resume will not show it.
The job is mostly judgment under incomplete information
Very little of the work is running a known process correctly. Most of it is deciding what to fix first, what to tolerate, and when to escalate, so weight the situational questions above the resume walk.
Follow-ups that separate operators from observers
Follow-ups that separate operators from observers
- Ask for the number. Anyone who has run an operation remembers the error rate, the cycle time, or the cost per unit, at least approximately.
- Ask what they did in the first week of a problem, not what the eventual solution was. The eventual solution is usually a team's work; the first week is theirs.
- Ask who disagreed with them and what happened. Change without resistance usually means the change was small.
- Ask what broke afterwards. Every real fix creates a new constraint somewhere else, and candidates who can name it were paying attention.
- Give them a real problem from your own operation and watch what they ask before proposing anything. The questions are the interview.
If you are the one being interviewed
If you are the one being interviewed
- Ask what is broken enough that they decided to hire for this role now. The answer is your actual job description.
- Ask who owned operations before you and where that person is now.
- Ask what you would be able to decide alone, what needs the chief executive, and what needs the board.
- Ask how the company measures whether operations is doing well, and whether anyone outside the function agrees with those measures.
- Ask what happened the last time someone in leadership pushed back on a deadline or a cost. It tells you whether no is a usable word here.
