Questions to Ask a COO Candidate in an Interview
55 questions to ask a COO candidate in an interview, written for the hiring side of the table: the chief executive, a board member, or a peer on the panel. They are grouped by what you are testing, from track record and how the candidate runs an operation, through people, the chief executive and the board, and judgment, to fit with this role. Most ask for evidence over philosophy, such as a number the candidate owned, a process they rebuilt, or a cut they made and what it broke. Each has a note on what a strong or a weak answer sounds like and what to ask next. Nobody gets through the whole list in one meeting, so pick six to eight per round and give the chief executive questions to whoever will work with this person every day.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
Track record
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. A string of initiatives with no outcomes attached means they ran programs. A metric, its baseline and the thing they changed means they ran the operation.
Which number did you personally own, and where did it start and finish?
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, ask which one they would have lost the job over. Someone who cannot choose was probably reading a dashboard another person built.
Tell me about a process you rebuilt. Who resisted, and what did you do about it?
Why ask it
Real change nearly always has an opponent. Naming the person or the function, and what they did about the objection, is the mark of someone who led the change through. When everyone quickly saw the benefit, you are hearing about a proposal and not 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 is the fastest growth you have run an operation through, and which part gave way first?
Why ask it
Fast growth breaks something first, often onboarding, fulfillment or the support queue, and a person who was in the seat remembers which. Ask for volumes at the start and at the end, then ask what they would have built six months sooner. If your own company is flat or shrinking, weigh this answer less and the cost question more.
How many people have you managed at peak, and how many did you hire yourself?
Why ask it
Running a large team someone else assembled is a different job from building a small one from nothing, so get both numbers, plus how many layers sat between them and the front line. Set the answer beside your own organization chart: it shows whether this job would be a step up, a step sideways or a step down for them.
What budget or profit and loss were you accountable for, and how much could you approve without asking anyone?
Why ask it
Accountable and consulted are different things, and the approval limit is the quickest way to tell them apart. Someone who looked after a large budget but needed sign-off on every contract was administering another person's plan. Get the figure, then check it with a reference.
What did you build that still runs the way you left it, and how do you know?
Why ask it
Results that vanished when the person left were being held up by effort. A review cadence, a planning process or a team that outlasted them is the stronger evidence, and 'how do you know' checks whether they are guessing. Staying in touch with former colleagues is a decent sign on its own.
Why did you leave each of your last two roles, and what would the chief executive there say was the reason?
Why ask it
Senior departures often come with an agreed story, so the chief executive's version is where the detail is. You are not looking for a spotless record: a sale, a new chief executive or a role that shrank are ordinary reasons. What matters is that the two versions would roughly match, and references will tell you whether they do.
Have you taken a company through an acquisition, a fundraise or a sale, and what exactly was your part?
Why ask it
Go deep on this only if one of the three is on your horizon. Working in the data room, running an integration and sitting through one as a spectator are different levels of experience, and the word 'exactly' is there to find out which. Deal terms may be confidential, but their own part in it should not be.
Operations
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 one of the few things a chief operating officer can carry from one company to the next. An agenda, the metrics reviewed and the way commitments were tracked between meetings add up to a system. Vagueness here suggests the rhythm was set by someone else and they attended it.
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.
How do you turn an annual plan into what a team is working on this week?
Why ask it
This is the job in one sentence, so a thin answer is costly. A complete one has layers: yearly goals, quarterly priorities with owners, and a regular check that the week's work still lines up with both. Ask to hear about the document they used and who was allowed to change it mid-quarter.
How did you build your forecast, and how wrong was it the last time it missed?
Why ask it
Operators who forecast for real remember their misses closely and can say whether demand, capacity or timing threw the number off. Whether the forecast was theirs or finance's matters as well. If you already have a strong finance chief, a candidate who wants to own it outright is a conflict to settle before the offer.
What systems did you implement, and how did that go against the original timeline and budget?
Why ask it
Big system projects run late so often that the credible answer includes the overrun and what caused it. A clean delivery on something complex does happen, so ask what made it possible. If they cannot say, they were probably not close to the work.
What work have you automated, and what did you do with the hours it freed up?
Why ask it
Plenty of candidates can list tools, including the newer AI ones. Fewer can say where the saved time went: into more volume, fewer people, or nowhere measurable. Ask what the error rate did after the change, because automating a messy process mostly produces mess faster.
How did you set headcount, and when did you last refuse a hire your own team wanted?
Why ask it
Headcount is where a chief operating officer either protects the company's economics or becomes a lobbyist for their own organization. The refusal tells you more than the planning method does. Ask who made the request, what the team did without the person, and whether the manager who was turned down is still there.
Tell me about a supplier or partner you replaced. What did the switch cost that the business case left out?
Why ask it
Cheaper on paper is the easy half of a sourcing decision. The hidden half is the transition: dual running, retraining, late deliveries during the changeover, a relationship that had been absorbing small favors for years. People who have done this can price those from memory, and many will volunteer the one switch they regret.
Sales has promised a customer a date that operations cannot hit. What do you do that afternoon?
Why ask it
It is a hypothetical, but one every operating chief has lived, so push for the real instance. The weak versions are a quiet scramble that burns out the team or a public fight with the head of sales. Better answers deal with the customer first and then change how dates get quoted.
Tell me about a customer you lost, or nearly lost, because of something operations did. What changed afterward?
Why ask it
Sales tends to own the win and operations the loss, so someone who ran delivery should have an account in mind. Listen for whether they spoke to the customer themselves, and whether the fix went into the process or stopped at an apology. If the story is mostly about an unreasonable customer, ask what the account manager would say.
How do you decide what gets measured, and which metric have you stopped reporting?
Why ask it
Adding measures is easy and nobody objects. Retiring one means telling whoever built it that it was not driving decisions, which takes a view about what the operation is for. If nothing has ever come off their dashboard, expect yours to grow.
People
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.
Who is the best leader you ever hired, and how did you find them?
Why ask it
The cheerful partner to the replacement question. Notice whether the person came through their own network, a search firm or a promotion from inside, since that is how they will fill your open roles too. A candidate whose former reports would follow them is bringing you a bench, though ask whether any agreement with a past employer limits who they can recruit, because that varies by contract and by country.
Who has gone on from your team to run something bigger, and what did you do that helped?
Why ask it
Names and current titles, please, since both can be looked up. A long list says they develop people and let them go. An empty one after many years says talent either stalled under them or left quietly, and it hints that you would be getting one indispensable person and no future leaders behind them.
How would you describe your management style, and which team did it not work on?
Why ask it
The first half gets the prepared speech, which is fine, since you need to hear it once. The team it failed on is what you are really asking about. Someone who has only ever managed operators may never have had to adapt to engineers, clinicians or a sales floor, and your mix of teams could be the first test.
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 feedback you gave a senior person who did not want to hear it.
Why ask it
Listen for the actual words, because people who have these conversations can quote themselves. Timing counts too: the same week, or saved up for a review months later. If every example ends with the other person thanking them, ask for the one that went badly.
Describe a culture you changed. What did people do differently afterward that a visitor would have noticed?
Why ask it
Culture answers drift toward values posters unless you pin them to behavior. Meetings that began on time, defects reported by the person who made them, managers on the floor at shift change: those can be observed. When the candidate cannot name one, the change was probably a communications campaign.
Have you led a layoff or closed a site? Walk me through how the people affected found out.
Why ask it
Skip this if cuts are not a realistic prospect for you. If they are, the sequence of that day tells you a great deal: who spoke, how much notice there was, what the people staying were told. Rules on notice and consultation differ by country and state, so a careful candidate will mention having checked them with counsel.
CEO and board
How did you and your chief executive divide decisions, and where did you disagree?
Why ask it
Much of whether this appointment works will come down to this one relationship. Look for an explicit division of authority and not only a description of good chemistry, and for a disagreement they can describe without running the other person down.
Tell me about a time your chief executive overruled you. What did you do in the weeks after?
Why ask it
Being overruled is routine for a number two, so the test is the aftermath. Carrying out the decision properly and reporting back on how it went is the job, while slow-walking it, or telling the team it was not their call, is how a leadership team splits in two. Ask who turned out to be right.
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.
What do you need a chief executive to stop doing so that you can do this job?
Why ask it
Put this to finalists with your chief executive in the room if you can. Common answers are approving every hire, taking escalations straight from the team, and reopening decisions that were settled. Whatever they name is a term they are asking for, and it is better negotiated now than in the third month.
What have you presented to a board, and what was the hardest question a director put to you?
Why ask it
Some operating chiefs present every quarter and some have never been in the room, and both kinds can be good at the job. You need to know which you are getting if your directors expect direct access. Recalling a hard question in detail suggests the board held them accountable in their own right.
Which peer on the leadership team did you clash with most, and where does that stand now?
Why ask it
Finance and sales are common answers, since their targets pull against the operation's. A clash is not a mark against anyone. You are weighing whether it ended in a working arrangement or in one of them leaving, and whether the candidate can describe the other person's position fairly.
Have you ever been pressed to report a number you did not believe, to a board, a lender or a customer? What did you do?
Why ask it
The operating chief often knows the shipped units, the backlog or the incident count before anyone else, which makes them the one leaned on when the figure is inconvenient. A credible answer describes the pressure and what they put in writing, without needing to name who applied it. If it has honestly never come up, ask what they would do if the request came from your chief executive.
Where do you want to be in five years, and does that include the chief executive's chair?
Why ask it
Ask it plainly, because either answer is fine and a dodged one is not. A candidate who wants the top job needs to hear whether that path exists here. One with no interest in it may be the better partner for a founder who plans to stay, so match the answer to your own succession thinking before you judge it.
Judgment
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. Anyone who implies they fixed everything is describing an operation smaller than the one you are hiring for.
When did you last change course on something you had already announced, and what made you do it?
Why ask it
Backing out is cheap in the first month and expensive in the tenth, so ask how long it took them to notice and what evidence did it. 'Already announced' is the point, because changing your mind in private costs nothing. No example at all suggests a short tenure or a habit of defending decisions past their usefulness.
What is the biggest call you made without the data you wanted, and why could it not wait?
Why ask it
An operation seldom hands over the full picture before the deadline, so what matters is how they decided they had enough. Good answers separate what was known from what was guessed, and name the early sign that would have told them the guess was wrong. Follow with what the missing data showed when it finally arrived.
Tell me about a time this quarter's number and a longer-term investment pulled against each other. Which did you protect?
Why ask it
Neither choice is wrong on its face: a company short of cash protects the quarter, and one with room protects the training budget or the new line. You want the reasoning and who they had to persuade. Set it against your own position, because a candidate formed in a well-funded business may never have had to choose.
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.
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.
What is the most expensive mistake you have made as an operator, and what did it cost?
Why ask it
Insist on the price, in money, customers or months. People who own their record can give it, and the figure shows the size of decision they were trusted with. A mistake that turns out to be a strength in disguise, such as caring too much or moving too fast, is a non-answer and worth a second attempt.
Where does your own time go in a normal week, and what did you most recently hand off?
Why ask it
An operating chief's calendar fills with other people's emergencies unless they defend it. The handoff matters because people promoted out of a function tend to keep doing the part they were best at. If nothing has been delegated lately, your current department heads should expect close company.
Tell me about a crisis that started outside the company, such as a supplier failing, an outage, or a sudden change in the rules.
Why ask it
Nobody chooses the cause of these, so what you learn is how much slack and how many alternatives they had built beforehand. Find out who made the calls in the first hours and whether a plan existed on paper. Then ask what they changed once it was over.
This role
Why this role, and why now? What would it take for you to stay where you are?
Why ask it
Many candidates at this level are employed and were not looking, so the reason they are in the room is real information: a stalled path, a new owner, a chief executive they no longer rate. Whatever would keep them is also what a counter-offer would have to contain. If all you hear is praise for your company, you have not reached the reason yet.
From what you have heard so far, how would you describe this job, and which functions would you expect to report to you?
Why ask it
The title covers anything from running delivery to running everything the chief executive would prefer not to, so their description shows which version they think they are being hired into. If it differs from yours, the interview is a better place to find out than the offer letter. Being asked for the reporting lines on paper is a good sign, and a prompt to write them down if you have not.
What would your first 90 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. A full plan delivered without a single question about the state of the operation is a pitch, not a diagnosis.
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.
Which part of this job have you never done, and how would you cover the gap?
Why ask it
No candidate matches the whole brief, and the good ones know their gap before you find it. A plan built on a named hire, a specific advisor or a few weeks working alongside the front line is credible. Claiming there is no gap, for a role that spans several functions, should send you back through their work history.
What have we not told you that you would need to know before saying yes?
Why ask it
Leave this until late, once they have met most of the team. The requests tend to be for the financials, the ownership picture, the reason the last person left, or a private conversation with a director. Each is reasonable at this level, and how you respond is part of what they are assessing in you.
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 someone who left, or for a peer instead of a former manager, tests their confidence and their relationships. Hesitation early on is reasonable while their employer does not know they are looking, so ask again at the final stage and agree who you may call.
What are your compensation expectations, and how do you think about cash against equity?
Why ask it
Raise this before the final round, so the process does not end with an offer nobody can accept. How they weigh salary against equity shows whether they are betting on the company or insuring against it. Ask about expectations and leave past pay out of it: some places restrict questions about salary history, so check the rules where you hire.
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. An argument over who owns what is far cheaper to have over a draft list than after the start date.
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 can be ordinary 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. It shows how they read numbers and handle a room in a way that another round of conversation does not, and it lets the internal team see what they would be getting. Keep it to an hour or two of their time, and do not use it to collect free advice on a live problem.
Divide the questions across rounds and interviewers
A list this long is a menu for a whole process. Give the track record questions to the first round, operations and people to the panel members who run those functions, and keep the chief executive and board questions for the person who will share the job. Agree beforehand who asks what, so three interviewers do not each spend twenty minutes on the same cost-cutting story.
Put the same core questions to every finalist
Comparison only works if the finalists faced the same questions. Choose five or six that every candidate gets, word for word, and write the answers down the same day. Everything else can vary with the person and with what their history throws up.
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.
- The same event told the same way when two interviewers ask about it in different rounds.
- Answers that hold back names or deal terms for confidentiality reasons but still give you the shape of what happened and their own part in it.
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 tends to absorb the blame and seldom has the standing to fix anything. Settle 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
The candidate's own list is chosen to flatter, so ask for a former peer and a former direct report as well as former managers, and ask each what the candidate is like when things go badly. If you want to speak to someone who is not on the list, tell the candidate first and stay away from a current employer who does not know they are looking. What you may ask a referee, and what consent you need, varies by country, so check with whoever handles hiring law for you.
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.