Questions to Ask a COO in an Interview
Questions for the hiring side of a chief operating officer interview, whether you are the chief executive, a board member, or a peer on the panel. They ask for evidence rather than philosophy: numbers the candidate owned, a process they rebuilt, cuts they made, and how they worked with the chief executive above them.
The questions
Open any question for the note
Walk me through the operation you inherited in your last role: what was broken, and what did the numbers look like when you left?
Why ask it
You are listening for before-and-after figures and for the mechanism between them. Candidates who describe initiatives without outcomes were running programs; candidates who name a metric, a baseline, and what they changed were running an operation.
Which measure did you personally own, and where did it start and end?
Why ask it
Strong operators have one or two numbers they lived in: on-time delivery, cost per unit, cycle time, churn, gross margin. If the answer is a portfolio of everything, probe further, since chief operating officers who cannot name their own metric usually inherited someone else's dashboard.
Tell me about a process you rebuilt. Who resisted, and what did you do about it?
Why ask it
Every real change has an opponent. A candidate who names the person or the function, and describes what they did next, has actually led change. Answers where everyone quickly saw the benefit describe a proposal rather than an implementation.
Describe a time you took cost out. What did you cut, and what broke afterward?
Why ask it
The second half is the question. Serious operators know what degraded, whether service times, quality, or morale, and can say how they detected and handled it. Anyone who reports pure savings with no consequence has not looked closely or is not telling you.
What did you decide not to fix, and why?
Why ask it
Judgment in operations is mostly triage. A clear example of a known problem left alone, with the reasoning and the risk accepted, is a good sign. Candidates who imply they addressed everything are describing an operation smaller than the one you are hiring for.
How did you and your chief executive divide decisions, and where did you disagree?
Why ask it
This relationship is the most common reason these appointments fail. Look for an explicit division of authority rather than a description of good chemistry, and for a disagreement they can describe without disparaging the other person.
Tell me about a senior leader you had to replace.
Why ask it
At this level, most improvement runs through the team, and someone who has never made a change at leadership level either inherited a strong bench or avoided the decision. Listen for how long they waited, what they tried first, and how the exit was handled.
How did you run your weekly operating review: what was on the agenda, and who was in the room?
Why ask it
The operating cadence is the most transferable thing a chief operating officer brings. A candidate who can describe the agenda, the metrics reviewed, and how commitments were tracked is describing a system. Vagueness here usually means they inherited someone else's rhythm.
Describe the last time a major operational commitment was missed. What did you do in the first two days?
Why ask it
You are testing behavior under pressure and whether they escalate honestly. Good answers include telling the customer or the board early. Answers focused on finding who was at fault tell you how bad news will travel once they are here.
What systems did you implement, and how did that go against the original timeline and budget?
Why ask it
Nearly every implementation runs late, so the credible answer includes the overrun and what caused it. Candidates who report clean deliveries on complex systems either had exceptional circumstances or were not close enough to the work to know.
How did you set headcount, and tell me about a time you refused a hire your own team wanted.
Why ask it
Headcount discipline is where a chief operating officer either protects the company's economics or becomes an advocate for their own organization. The refusal example matters more than the planning method, and it shows how they handle pressure from below.
Has there been a safety, quality, or compliance failure on your watch, and what happened?
Why ask it
In most operating environments something has gone wrong. What you want is a candidate who reports it plainly, describes the investigation, and names the control that was added. Deflection here should weigh heavily, given what the role is responsible for.
How did you find out what was actually happening on the floor, in the queue, or in the field?
Why ask it
Look for a specific habit: walking the operation, listening to support calls, reading tickets, a standing session with front-line supervisors. Chief operating officers who rely only on their reports' summaries are the ones surprised by problems everyone else already knew about.
What would your direct reports say is the most difficult thing about working for you?
Why ask it
The useful answers are specific and mildly unflattering: impatience with unprepared meetings, too much detail, moving people around. A polished non-answer at this level suggests either little feedback received or little appetite for it.
Tell me about a decision you reversed.
Why ask it
Reversals are cheap early and expensive late, so listen for how quickly they noticed and what evidence changed their mind. Candidates who cannot recall reversing anything are describing either a short tenure or a habit of defending decisions past their usefulness.
How many people have you managed at peak, and how many did you hire yourself?
Why ask it
Scale of team is not the same as scale of budget, and both differ from having built the team versus inheriting it. This is a factual question, easy to verify in references, and it distinguishes candidates whose experience is a fit from those a level away.
What would your first sixty days here look like, and what would you need from us?
Why ask it
The plan matters less than what they ask for: access, data, authority over specific functions, agreement on which problem comes first. Candidates who present a full plan without asking what shape the operation is in are selling rather than diagnosing.
From the outside, what looks wrong in our business?
Why ask it
This tests preparation and courage together. A candidate willing to name something uncomfortable, hedged appropriately because they lack inside information, is showing you how they will behave in your leadership meetings. Flattery is the answer to be worried about.
Which of our numbers would you want to see first?
Why ask it
The request itself reveals their operating model: unit economics, retention, cycle time, utilization, working capital. It also shows whether they have understood what type of business this is, which matters if they are crossing industries.
What kind of chief executive do you work badly with?
Why ask it
Asking for the negative gets a franker answer than asking about ideal partnerships. If their description matches your chief executive, you have found the problem before the hire, which is much cheaper than finding it eighteen months in.
Who should we speak to about your work, including someone who left your team?
Why ask it
Anyone senior has a curated reference list. Asking for a departure, or for a peer rather than a former manager, tests both their confidence and their relationships. Take the reluctance seriously, but ask again in the final stage.
What are your compensation expectations, and how do you think about cash against equity?
Why ask it
Raise this before the final round. How a candidate reasons about the split tells you whether they are betting on the company or protecting against it, and it prevents a process that ends with an offer nobody can accept.
Hiring a chief operating officer
Practical guidance for the conversation itself
Settle the role before the first conversation
Write down which functions report to this person
Chief operating officer means something different in every company: sometimes everything except product and engineering, sometimes only delivery and support. Put the list on paper, get the current leadership team to agree to it, and share it with candidates. Most failed appointments trace back to this list never having existed.
Name the problem you are hiring against
Scaling a working operation, fixing a broken one, and professionalizing a founder-run company need different people. Say which one it is, because a candidate who is excellent at one of them is frequently mediocre at another.
Be honest about the chief executive relationship
If the chief executive intends to keep making operating decisions, say so. Candidates can work with that, but not with discovering it later. Ask your chief executive in advance which decisions they will genuinely hand over, and treat a vague answer as a reason to pause the search.
Use a work sample rather than more conversation
Ask finalists to review an anonymized operating pack and present what they would change, or to run a mock operating review with two of your leaders. An hour of this reveals more than three interviews, and it also shows the internal team what they would be getting.
What to listen for
- Numbers with baselines and dates attached, not initiatives with adjectives.
- The word I used for decisions and we used for results, rather than the reverse.
- Specific opponents in change stories: a named function, a union, a large customer, a colleague.
- Willingness to say what broke, what they got wrong, and what they left unfixed.
- An operating cadence they can describe in detail, including how commitments were tracked between meetings.
- Questions of their own about your data, your decision rights, and your leadership team.
- Comfort with being told no during the interview, since that is a large part of the job.
What goes wrong
Hiring a chief operating officer to solve a chief executive problem
When a board wants someone to compensate for a founder's weaknesses without changing the founder's authority, the new appointment absorbs the blame and leaves within two years. Fix the mandate first, or accept that the hire is a temporary arrangement.
Interviewing for philosophy instead of evidence
Questions about approaches to operational excellence get fluent, unfalsifiable answers, because every experienced candidate has that speech ready. Ask what happened, when, to which number, and who objected.
Assuming industry experience transfers, or that it does not
Some operating skill is general, such as cadence, metrics, and running a leadership team. Some is not, such as regulated environments, physical supply chains, and union relationships. Decide in advance which parts of your operation are unforgiving of a learning curve.
Skipping back-channel references
For a role this senior, the candidate's own list is the least useful evidence you will gather. Ask for a former peer and a former subordinate, then find one more person independently, and ask each of them what the candidate is like when things go badly.
Leaving the first ninety days undefined
Without an agreed list of what this person owns from day one, existing leaders keep the decisions and the new appointment spends a quarter negotiating for authority. Write the list, and tell the leadership team before the start date rather than after.