Questions to Ask a COO in an Interview
These are questions to ask a COO in an interview when you are the candidate and the chief operating officer is across the table, often in a final round. The 52 questions start with openers on challenges, priorities and how success is measured, then cover how the operation runs, money and headcount, how the COO leads, the role itself, and a few for the last five minutes. Each has a note on what a full answer or a thin one tells you. If you are hiring a COO, or interviewing to become one, the guide below shows how to turn the list around.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
Openers
What are the biggest operational challenges the company is facing right now?
Why ask it
The COO is the one person in the process who cannot plausibly say there are none. Listen for whether the challenge they name is the one this role exists to help with, and if it is not, ask how the two connect.
What are the company's top priorities for the next twelve months, and where does this role fit into them?
Why ask it
Count the priorities. Three is a plan and nine is a list, and a role that maps to none of them is an easy one to cut when budgets tighten. Compare the answer with what the hiring manager told you.
What would a strong first 90 days in this role look like from where you sit?
Why ask it
You have probably put this to the hiring manager already, and that is the reason to repeat it. The COO's version is usually a result they want to see, where the manager's was a list of tasks. If the two do not match, say so and ask which one counts at your first review.
How do you measure whether operations is having a good quarter, and which number is furthest from where you want it?
Why ask it
The first half gets you the scoreboard: on-time delivery, cost per order, churn, whatever this business runs on. The second half is the useful part. The number that is off is where attention and budget will go, so ask how close this role sits to it.
Where is the company trying to be in three years, and what does operations need to be able to do by then that it cannot do today?
Why ask it
Growth targets are set in one room and delivered in another. A COO who can name the gap, whether it is capacity, systems or management depth, is describing the work of the next few years and probably part of your job. An answer that is all ambition and no gap deserves a follow-up.
Which problem has had most of your attention over the past month?
Why ask it
Where a COO's attention goes is a fair guide to what the business is really working on, whatever the strategy deck says. A month spent mostly on one customer, one site or one system shows you where the trouble is. If the answer is a string of unrelated fires, ask how long it has been that way.
Why did you join this company, and what has made you stay?
Why ask it
An easy one that still earns its place. The first half is usually a practiced story, so listen to the second: someone who can only talk about why they joined may be telling you the job has changed since.
Which competitor do you watch most closely, and what do they do better than you on the operations side?
Why ask it
Sales will tell you why the company wins. The COO is the one who knows where a rival delivers faster, answers customers sooner or runs at lower cost. A specific and slightly rueful answer is a good sign, and 'nobody really does what we do' is a claim to check for yourself before the next round.
Operations
What is the operating cadence here: which meetings, reviews and reports set the rhythm of the month?
Why ask it
Ask them to walk you through one month: the weekly review, the forecast, whatever planning cycle there is. Note which of those meetings your role would sit in or prepare numbers for. If no rhythm can be described, ask where priorities get decided instead.
How does work get prioritized when sales, product and operations all want the same resources?
Why ask it
Somebody has to referee, and it is often the person you are talking to. A good answer describes a forum and a rule, such as a weekly call where the revenue case wins unless it breaks a promise to a customer. 'We talk it through' with no example suggests the loudest executive tends to win.
If a decision forces a choice between doing it well, doing it fast and doing it cheaply, which usually loses here?
Why ask it
Most operations have a default, and people inside rarely say it out loud until asked. Ask for the last decision where it came up. If cost gave way to quality on a real order or a real launch, you know what you would be backed on when the same choice reaches you.
Which process here still runs on heroics rather than on a system?
Why ask it
Most growing companies have at least one: the month-end close that depends on a single analyst, the big customer only one person knows how to handle. A COO who names theirs straight away knows the ground floor. Then ask whether fixing it is on this year's list, and whether it would land on your desk.
Where does execution most often break down between teams, and what have you already tried to fix it?
Why ask it
Pay more attention to the second half. Two failed fixes and a shrug point to something political between two leaders, and your role may sit on that seam. One fix that half worked is an ordinary handoff problem, the kind a new person can finish.
When something goes wrong in operations here, how do you find out about it?
Why ask it
Either there is a real escalation path, such as an on-call rotation or a standing review, or bad news travels by rumor until it is too big to hide. Ask about the last incident. How it reached them is how you would be expected to raise a problem yourself.
How does what customers are saying reach you, and when did it last change how the operation runs?
Why ask it
Complaints, cancellation reasons and support tickets often stop at the team that receives them. A recent example of feedback that changed a process means the loop is closed. No example suggests operations is steered by internal numbers alone.
Which systems does the operation run on, and which one would you replace tomorrow if you could?
Why ask it
The first half tells you what tools you would be living in. The second tells you where the workarounds are, and whether a migration is likely to land in the middle of your first year.
When you roll out a change the front line did not ask for, how do you go about it?
Why ask it
A new system or rule can be sound on paper and still fail because nobody adopts it. You want to hear about pilots, training time and someone going back afterwards to check. Whatever method they describe is the one your team would be put through.
Which parts of the business are you deliberately leaving inefficient for now, and why?
Why ask it
No operation fixes everything at once, so there should be a list of things knowingly left alone. If the area you would join is on it, you have just learned not to expect budget or attention there this year. That is worth knowing before you promise anyone a turnaround.
Which operational risks keep you up at night: a single supplier, a compliance exposure, one person nobody could replace?
Why ask it
The stock version of this question gets a stock answer, which is why the examples are attached. A risk named with a plan beside it is being managed. If the one they pick sits inside the job you are interviewing for, ask what has already been tried.
What did the company get wrong in the past year, and what concretely changed as a result?
Why ask it
Naming a failure is easy, so listen for the change that followed. A story that ends without a change to a process, a team or the plan suggests the lesson did not stick.
Resources
How would you describe the company's financial position today: profitable, funded to a certain date, or somewhere in between?
Why ask it
A fair question in a final round, and the COO is one of the few interviewers who knows the answer. What they may share depends on whether the company is public or private and on its own rules, so ask what they are able to tell a candidate at this stage.
What has the company promised its board or owners for this year, and how is it tracking against that?
Why ask it
A target the operation cannot hit lands on the COO first and on everyone else soon after. How much a candidate can be told varies by company, so accept 'ahead', 'on plan' or 'behind' as a full answer. If it is behind, ask what is being done to close the gap, since that is often where a hiring freeze starts.
How are headcount and budget for this team set, and how much of the current plan is already approved?
Why ask it
The team you have been told you will build sits either in an approved budget or on a wish list, and only the first is a promise. Ask when the next budget review is and what could reopen the numbers before then. Practice differs from company to company, so get the actual dates.
When money gets tight here, what is protected and what goes first?
Why ask it
Ask about the last real instance, not the principle. Whether training, tooling, contractors or hiring went first that time is the best guide to what happens to your plans in a lean quarter.
If you were handed extra budget tomorrow, where in the operation would you spend it first?
Why ask it
The answer points at whatever is most starved today: a system held together with spreadsheets, a team one person short, a site that has run out of room. If it is the area you would join, ask why it has not been funded yet. If it is somewhere else, you know who is ahead of you in the queue.
How are you weighing automation, AI tools and outsourcing as the company grows, and what would that mean for this team?
Why ask it
You are asking what shape the operation is meant to have in two years. A COO with a plan can say which work stays in house, which goes to a vendor and which gets automated. Note where your function falls, and if it is in the second or third group, ask about timing.
Leadership
How do you and the CEO divide the work? What lands on your desk, and what goes to theirs?
Why ask it
The split is different at every company: some COOs run everything internal while the CEO faces outward, others own a handful of functions. What you need from the answer is who signs off on things in your area. If the same decision seems to belong to both of them, expect to seek approval twice.
When the leadership team disagrees, where does the argument actually happen?
Why ask it
In the meeting is healthy. In the corridor afterwards means decisions get reopened after you thought they were made, and people several levels down are left working out which executive to believe.
Tell me about a decision you reversed in the last year. What changed your mind?
Why ask it
Listen for what did the changing: new numbers, a pilot that failed, or simply whoever complained loudest. A COO who tells this story easily is more likely to let you revisit a call of your own. One who cannot think of a reversal in twelve months either gets everything right or never goes back.
How would you describe your leadership style, and would your direct reports describe it the same way?
Why ask it
The first half gets the prepared answer. The second makes them picture particular people, and what comes out is often more honest, such as being too deep in the detail or slow to give praise. A COO who has plainly never wondered is showing you how much feedback travels upward.
What do the people who do best working for you have in common?
Why ask it
You are being handed the unwritten job description. Hold the traits up against yourself honestly: if the answer is people who never need direction and you like a weekly check-in, better to know now.
Beyond hitting targets, how do you tell whether a manager here is doing well?
Why ask it
Some companies measure outcomes and some measure visibility. Listen for whether retention, quality or peer feedback come up without prompting. If you would be managing people, this is your own review described a year early.
How do you handle a manager who consistently hits their numbers but leaves damage behind them?
Why ask it
Ask what happened the last time, since every company says it would act. If the manager was moved or let go, the stated values are enforced. If the story trails off into coaching that is still going on, expect to work alongside people like that.
How would you describe the culture here, using something that happened this month as the example?
Why ask it
Asked plainly, the culture question gets adjectives. Asking for a recent example makes the COO reach for an actual event, and the one they pick, a late push to ship, a hard conversation or a celebration, is the culture as they see it.
Who has been promoted out of your organization in the past two years, and into what?
Why ask it
Development is easy to promise and simple to check. Names and destinations mean people grow here. A long pause, or a list of people who left to get the next title, shows you where the ceiling is.
When people leave your part of the company, what is the usual reason?
Why ask it
Attrition is hard to dress up when the question is asked plainly. Watch for the difference between people outgrowing roles and a pattern, such as burnout concentrated in one function.
The role
What made you want to be part of the interviews for this role?
Why ask it
At some companies the COO meets every finalist, at others only a few. If this search is one of the few, the reason matters: the role touches a problem they own, or an earlier hire went badly. Either way you learn how closely the seat will be watched.
How does the work of this role show up in what you report to the CEO?
Why ask it
You are asking them to draw a line from your daily work to something the CEO looks at. If they cannot, the role reads as overhead in their mind, which matters when budgets get cut.
What are you handling yourself today that you would hand to this person in their first month?
Why ask it
Whatever they name is your real first assignment. If it is something the hiring manager never mentioned, the two of them have not agreed on what the role is for, and that is worth raising before an offer.
A year in, what would I need to have done for you to call this a great hire?
Why ask it
Ninety days is about settling in and a year is about results. Ask them to make it measurable, then set it beside the target your future manager gave you, because you will be reviewed against one of the two.
What could I decide on my own in this role, and what would need your sign-off?
Why ask it
Decision rights are the difference between owning a function and staffing one. Ask for a concrete example, such as a hire or a vendor change, and see whether they can produce one.
What do you want to hear in an update from me, and how often?
Why ask it
Better to settle reporting expectations before you accept than to discover them in week three. A COO two levels up who wants daily detail is telling you something worth noticing now.
Who would I be working with most closely outside my own team?
Why ask it
The answer names your real stakeholders, who are often missing from the org chart you were shown. If the job depends on a team you have not met, ask to meet them.
How do you and the person I would report to work together, and what do you rely on them for?
Why ask it
When the COO is your boss's boss, this relationship decides how much backing your work gets. Warm, specific praise is a good sign. A careful or generic answer is worth remembering but not worth pressing in the room. Skip the question if you would report to the COO directly.
What did the last person in this seat find hardest about it?
Why ask it
This reads as diligence rather than doubt, provided you ask about the job and not the person. Listen for whether they know at all: a COO who cannot say what their predecessor struggled with was not close to the role. If the seat is new, ask what has been hardest about leaving it empty.
Where do you expect this team to be different a year from now?
Why ask it
You learn whether the plan is to grow the team, restructure it or automate part of it. A studiously vague answer here is common in the months before a reorganization.
Where would you want someone in this job to disagree with you?
Why ask it
Good operators want a counterweight and can say where: a forecast that is too hopeful, a deadline set without asking the team. If nothing comes to mind, ask how the last disagreement from someone at your level went.
Closing
If this hire did not work out, what do you think would be the most likely cause?
Why ask it
Save it for the end. It asks them to name the real risk in the role, whether that is scope, resourcing or a difficult stakeholder, and most operators will answer it straight. Take their answer to the hiring manager and ask how the two of you would head it off.
What would you need to be more sure of about me before making this hire?
Why ask it
Whatever the doubt is, you would sooner hear it in the room than have it settle the decision after you have left. Answer once, with a concrete example, and then let it rest. Arguing the point with the most senior person you have met tends to confirm the doubt.
Who else on the leadership team should I talk to before I decide?
Why ask it
Their choice shows who your work would depend on, and their willingness to arrange it shows how open the company is with finalists. Take them up on it: a second executive's version of the priorities is worth comparing with this one.
What have I not asked that someone joining your organization ought to know?
Why ask it
Leave room for it instead of squeezing it into the last thirty seconds. Operators often use the opening to mention a reorganization, a system change or a difficult quarter that no prepared question would have reached.
What happens next, and is this the last conversation or is there another after it?
Why ask it
A COO interview is often the final round but not always, and they usually know where the decision stands. Ask who makes the call and by when, so you know how long to wait before following up with the recruiter.
Making the COO Conversation Count
Practical guidance for the conversation itself
How to Use These Questions
Pick five, not twenty
A COO interview is usually short and much of it belongs to them, so ask at the start how long you have. Choose two openers, two about how the operation runs or how it is resourced, and one closing question, then let the follow-ups do the work. Keep a few from the role group in reserve in case the conversation runs long.
Take the groups in order of who else can answer
Questions about the role, the team and next steps can also go to the hiring manager or the recruiter. Budget, the split with the CEO, board commitments and operating risk can only really be answered by the COO, so spend this conversation there first and carry the rest to the other rounds.
Ask about mechanics, not values
COOs tend to answer process questions with detail and philosophy questions with slogans. Asking what is on the agenda of the weekly review gets you further than asking for the company's values, which is why the culture question in this list asks for something that happened this month.
Anchor each question in something you found
Mention a funding round, a new market, a product launch or a theme from employee reviews before you ask. It shows you prepared, and it makes the question specific enough that a generic answer would sound evasive.
Write down the numbers they name
Metrics, headcount figures and timelines from this conversation are the best material for your follow-up note and for checking against what the hiring manager and recruiter told you.
Reading the Answers
- Green flag: they name a specific broken process and the next step they are taking on it.
- Green flag: they can quote current numbers from memory instead of promising to send a deck.
- Green flag: the split with the CEO is described through concrete examples.
- Yellow flag: every problem is attributed to a predecessor or to a team that has since left.
- Yellow flag: headcount for your area is described as 'we will figure that out once you start'.
- Red flag: asked what happens when the company falls behind plan, they talk about who was held to account and never about replanning.
- Red flag: they cannot name anything the company got wrong in the last year.
- Red flag: the priorities they describe do not match the ones the hiring manager gave you.
If You Are the One Hiring a COO
Flip the questions into the past tense
Turn each item into evidence gathering. Instead of asking how they would set an operating cadence, ask them to walk you through the cadence they inherited at their last company and what they changed in the first two quarters.
Probe the stage they actually operated at
Running a 2,000 person organization is a different job from building the first version of one. Ask for revenue, headcount and span of control at the start and end of their last role, then ask which of those numbers they were accountable for.
Test the CEO relationship directly
Ask what they and their previous CEO disagreed about most and how it was settled. A candidate who cannot describe one disagreement that ended well has either avoided them or was not close enough to the CEO to have any.
If You Are Interviewing for the COO Job
Point the same subjects at the CEO and the board
The list still works with the seat changed. Ask the CEO which decisions they intend to keep, which functions would report to you on day one, what was promised to the board this year, and what the last operations leader found hardest. Ask a board member what they would want to see change in the first two quarters.
Find out why the seat exists now
A first COO, a replacement and a COO brought in ahead of a succession are three different jobs under one title. Ask what prompted the search and what the CEO expects to stop doing once you arrive, and compare the answers you get from each person you meet.
Meet the people around the seat
Before you accept, ask to spend time with two or three of the leaders who would report to you and, where there is one, a board member or investor. Their picture of what a COO is for may not match the CEO's, and that is easier to hear before you start than after.