Questions to Ask a COO in an Interview
For candidates who have a COO interview on the calendar, usually in a final round. These 20 questions dig into operating cadence, real metrics, resourcing and decision rights, so you learn how the company actually runs.
The questions
Open any question for the note
How do you spend most of your week right now, and what does that tell me about the company's priorities?
Why ask it
A COO's calendar is the most honest statement of what the business is actually working on. If the answer is all firefighting, expect a reactive operation rather than a planned one.
What is the operating cadence here: which meetings, reviews and reports set the rhythm of the month?
Why ask it
Well run operations have a visible drumbeat, such as a weekly business review, a monthly forecast and a quarterly planning cycle. A vague answer usually means priorities get set in hallway conversations.
Which two or three numbers do you look at first on a Monday morning?
Why ask it
This gets you the real scoreboard instead of the dashboard on the careers page, and it tells you which metrics your own work will eventually be judged against.
How does work get prioritized when sales, product and operations all want the same resources?
Why ask it
Resource conflict is the daily reality of the COO seat, so the answer shows whether there is a real arbitration process or whether the loudest executive tends to win.
What would a strong first 90 days in this role look like from where you sit?
Why ask it
It surfaces the specific outcomes you will be measured on early, and any gap between this answer and the job description is worth resolving before you accept.
Which process here still runs on heroics rather than on a system?
Why ask it
Every scaling company has one, and a COO who can name it immediately is honest and self aware. A COO who says nothing comes to mind either does not know the ground floor or will not admit it.
Where does execution most often break down between teams, and what have you already tried to fix it?
Why ask it
The list of failed attempts tells you far more than the diagnosis, because it reveals whether this is a solvable handoff problem or an entrenched political one you would inherit.
How do you decide when to redesign a process versus add headcount to absorb the load?
Why ask it
This separates operators who build leverage from ones who scale cost linearly with volume, and it hints at how much room you will have to fix things properly.
How is headcount planned here, and how much of the current plan is actually funded?
Why ask it
It tests whether the team you are told you will build exists in an approved budget or only in a hiring wish list, which is the difference between a promise and a plan.
What has the company committed to the board this year, and what happens internally if a quarter comes in short?
Why ask it
The reaction to a miss defines the culture under pressure, and it tells you whether shortfalls trigger a replan, a hiring freeze, or a hunt for someone to blame.
Which parts of the business are you deliberately leaving inefficient for now, and why?
Why ask it
A deliberate answer signals a leader who sequences priorities instead of chasing every fire, and it shows you where mess is tolerated on purpose versus by neglect.
How do you and the CEO split decision rights? What lands on your desk and what goes to theirs?
Why ask it
Unclear boundaries at the top create rework and quiet vetoes further down. This also tells you who you actually need to convince to get anything approved.
Tell me about a decision you reversed in the last year. What changed your mind?
Why ask it
Reversals are where you learn whether someone updates on evidence or on pressure from whoever complained loudest, and whether they will support you when your own call needs revisiting.
How do you handle a manager who consistently hits their numbers but leaves damage behind them?
Why ask it
This is the clearest test of whether stated values survive contact with revenue, and the answer predicts what behavior gets rewarded on the teams around you.
When quality, speed and cost collide on the same decision, which one gives first here?
Why ask it
Every operation has a default tiebreaker, and knowing it in advance tells you which tradeoffs you will be defending for the next few years.
For the next stage of scale, how are you weighing automation and tooling against outsourcing or offshoring?
Why ask it
The answer shows the intended shape of the operation two years out, including whether your function is likely to grow, be automated, or be handed to a vendor.
Which operational risks keep you up at night: a single vendor, a compliance exposure, a key person dependency?
Why ask it
A COO who has mapped concentration risk will name specifics with mitigations attached, while a generic answer suggests risk work has not moved past the spreadsheet stage.
How would your direct reports describe what it is like to be managed by you?
Why ask it
It invites a candid self assessment rather than a rehearsed leadership philosophy, and the specificity of the answer tells you whether they have actually asked.
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 with no resulting process, staffing or roadmap change means the lesson did not stick.
If I take this job and it does not work out, what do you think the most likely reason will be?
Why ask it
This is the highest signal closing question you can ask an operator, because it forces them to name the real risk in the role, whether it is scope, resourcing, or a difficult stakeholder.
Making the COO Conversation Count
Practical guidance for the conversation itself
How to Use These Questions
Pick four, not twenty
A COO interview is usually 30 to 45 minutes and much of it belongs to them. Choose one opener, two about how the operation runs, and one closing question, then let the follow ups do the work.
Ask about mechanics, not values
COOs answer process questions with detail and philosophy questions with slogans. 'What is the weekly business review agenda' gets you further than 'how would you describe your culture'.
Anchor each question in something you found
Reference a funding round, a new market, a product launch or a Glassdoor theme before you ask. It shows preparation and it makes the question specific enough that a generic answer would look 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 cross checking against what the hiring manager and recruiter told you.
Reading the Answers
- Green flag: they name a specific broken process and the exact next step they are taking on it.
- Green flag: they can quote current numbers from memory rather than promising to send a deck.
- Green flag: the split of decision rights with the CEO is described in 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: the answer to a missed quarter is about accountability with no mention of replanning.
- Red flag: they cannot name anything the company got wrong in the last year.
- Red flag: their described priorities do not match the priorities 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 'how do you set operating cadence', ask 'walk me through the operating cadence you inherited at your last company and what you changed in the first two quarters'.
Probe the stage they actually operated at
Running a 2,000 person org 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 resolved. A COO who cannot describe productive disagreement rarely survives the second year.