Questions to Ask a COO at the End of an Interview
For candidates who get the last ten minutes of a COO interview to ask their own questions. These cover what the first quarter should produce, decision rights, operating cadence, and how to close the conversation well.
The questions
Open any question for the note
What would you want the person in this role to have accomplished by the end of their first quarter?
Why ask it
The first quarter answer is the one you can hold them to later. If it comes back as getting to know the team and learning the systems, the role has not been scoped and you will be inventing it in month two.
Which part of the operation are you personally most focused on right now?
Why ask it
A COO's own focus is where budget and attention go. If their answer sits far from the function you would join, expect to argue for resources rather than ride a priority.
How does the work of this role show up in what you report to the CEO?
Why ask it
Forces a line between your daily work and something the CEO looks at. If they cannot draw it, the role reads as overhead in their mind, which matters when budgets get cut.
Who would I be working with most closely outside my own team?
Why ask it
Names your real stakeholders, who are often missing from the org chart you were shown. It also flags whether the job depends on a team you have not met and should ask to meet.
What did the last person in this seat find hardest about it?
Why ask it
Asked at the end, this reads as diligence rather than doubt. Listen for whether they know at all: a COO who cannot say what their predecessor struggled with was not close to the role.
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 reorganisation.
Which decisions would be mine to make, and which would come to you?
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 weekly or monthly rhythm would I be plugging into?
Why ask it
Tells you how much of your calendar is already committed and where you would be expected to present. A company with no described cadence sets direction ad hoc, which is tiring from below.
When something goes wrong in operations here, how do you find out about it?
Why ask it
Reveals whether real escalation exists, such as an on call rotation or a Monday review, or whether bad news travels by rumour until it is too big to hide.
What is the company deliberately not fixing this year?
Why ask it
A COO who can name a conscious tradeoff is sequencing priorities. One who says everything is a priority is describing a place where projects start and quietly stall.
How much of what this team does is still manual, and is that changing?
Why ask it
Manual work is where new hires lose their first six months. The follow up worth asking is whether tooling budget exists this year or only appears on a roadmap.
What do you want to hear in an update from me, and how often?
Why ask it
Sets reporting expectations before you accept instead of discovering them in week three. A COO two levels up who wants daily detail is telling you something worth noticing now.
Which internal team is hardest to get things done with, and why?
Why ask it
You are asking about friction, and most operators answer honestly because they live with it. If they claim no team is difficult, they are managing the interview rather than answering it.
What has changed in the operation since the last funding round or reorganisation?
Why ask it
Anchors your question in something you researched and gets you the recent history that shapes the job. A recent restructure often explains why the role is open at all.
Beyond hitting targets, how do you tell whether a manager here is doing well?
Why ask it
Separates companies that measure outcomes from companies that measure visibility. Listen for whether retention, quality or peer feedback come up without prompting.
What is the most common reason people leave this organisation?
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.
Is there anything in my background that gives you pause?
Why ask it
Lets you answer an objection while you are still in the room. It often surfaces a concern that would otherwise never be raised with you until after the decision was made.
What would make you say, a year from now, that this hire was the right one?
Why ask it
Their answer is your first performance review, delivered in advance. If it differs from what the hiring manager told you, resolve the gap before you accept an offer.
What are the next steps, and who else would I meet?
Why ask it
Practical and expected at the close. It also shows how far along the process really is, since a COO who does not know the remaining steps may not be the decision maker.
Is there anything you would want me to think about before we speak again?
Why ask it
A low pressure invitation that often produces the most useful minute of the conversation: a topic they want covered next time, a lingering concern, or homework worth doing.
Using the Last Ten Minutes Well
Practical guidance for the conversation itself
The end of the interview is not a formality
Most COO interviews leave five to ten minutes for your questions, and it is the only stretch of the hour you control. Choose three before you walk in: one about what the first quarter should produce, one about how the operation actually runs, and one closing question. Rushing through eight questions leaves a worse impression than asking two and following up properly on the answers.
Pick questions a COO can answer
- Ask about mechanics: cadence, decision rights, escalation, headcount. Operators answer these in detail because they live in them.
- Skip anything the recruiter already covered, such as benefits or start dates. It signals you did not track your own process.
- Skip broad questions about culture and values. They produce slogans, and the COO has answered them dozens of times this year.
- If the COO would not be your manager, ask about the operation and the company rather than about your day to day tasks.
Two questions worth saving for last
- "Is there anything in my background that gives you pause?" It lets you answer an objection in the room instead of losing on it silently a week later.
- "What would make you say in a year that this hire was right?" It hands you the performance criteria before you negotiate the offer.
Reading what you get back
- Numbers offered without prompting, such as cycle times or headcount, suggest a leader who is close to the operation.
- A first quarter described entirely as onboarding usually means the role has not been defined yet.
- If their account of priorities does not match the hiring manager's, raise it before accepting rather than after.
- If every problem is attributed to a team that has since left, expect the same explanation about you one day.
After the conversation
- 1Write down the numbers and names they mentioned while you still remember them accurately.
- 2Send a short note that references one specific thing they said rather than a generic thank you.
- 3If they named a concern about your background, address it in that note with evidence rather than reassurance.
- 4Compare their version of the role against the job description and the recruiter's version, and take any gap into the offer conversation.