What a COO Actually Wants From You
A COO interview is rarely about culture fit or passion statements. They are evaluating whether you can translate strategy into operational reality without making their day significantly worse. I have sat on both sides of that table, and the dynamics shift depending on whether the role is more execution-focused or transformation-focused. The approach changes accordingly. The core skill they are testing is your ability to think in systems. When a COO asks a question, they are usually listening for whether you understand second-order consequences. Say you propose a new workflow. The immediate follow-up I always listen for is whether you mention how that workflow interacts with finance, compliance, and customer support. If you don't, I assume you haven't thought it through yet. Here is the practical part. Prepare three specific operational war stories where something broke and you fixed it. Not high-level descriptions. Real details. The time you had to reconcile a sales promise with a shipping constraint in forty-eight hours. The process you redesigned that cut lead time from eleven days to four. Quantify everything because COOs think in numbers, not narratives. Vague claims like "I improved efficiency" mean nothing to someone who has seen a hundred of them. Saying "I reduced checkout abandonment by 18 percent by removing a mandatory fields step" is the kind of thing that lands.
I ran into a candidate once who was brilliant on paper and had impressive metrics from their last role. During the interview, they described scaling a fulfillment operation but kept framing it as a people problem. They talked about hiring and training. What they completely missed was that the real bottleneck was their WMS integration with the carrier API, which caused a 30 percent manual intervention rate. That system issue was costing them roughly $240,000 annually in extra labor. When I pointed it out, they went quiet and admitted they never audited the tech stack. They were too close to the ground to see the real lever. Don't be that person. Show you understand the infrastructure, not just the headcount. Another counter-intuitive thing: sometimes the best answer to a COO's question is a well-reasoned "I don't know, but here is how I would find out." They hear plenty of confident bullshit from people who talk big and deliver little. Operational leaders respect intellectual honesty because it is rare. It also saves everyone time when you flag a knowledge gap instead of fumbling through a half-built answer.
The Questions They Will Throw At You
Expect scenario-based questions about resource allocation under constraints. They might ask how you would handle a situation where revenue targets demand a delivery speed the current ops team cannot support. The answer is not a single solution. It is a framework: assess the gap, identify the constraint, evaluate trade-offs, and communicate the decision with rationale. Walk them through that logic. Show the thinking, not just the conclusion. You will also get questions about cross-functional friction. COOs sit at the intersection of every department and they deal with conflict constantly. When they ask about working with difficult stakeholders, they want to know whether you escalate unnecessarily, avoid hard conversations, or actually resolve the root cause. Describe a specific disagreement, what you did to understand their position, and how you aligned on a path forward. Concrete examples beat generic platitudes every time. One more thing most candidates get wrong. They come in rehearsed, as if performing a monologue. COOs read through that in about three minutes. They can tell when someone is reciting prepared answers versus actually engaging with the question. Let the conversation breathe. Listen more than you speak. Ask clarifying questions before launching into your response. This signals that you operate collaboratively, which is exactly what the role demands.
Get the Full Details
What Not To Do
Do not oversell. Do not claim you single-handedly rescued a company. Operational work is almost never a solo hero story. Acknowledge the team, the constraints, and the trade-offs you made. Credibility matters more than impressiveness here. Do not ignore the financial implications of your answers. Every operational decision has a cost side. If you propose a solution, understand the capex, opex, and timing involved. I once dismissed a candidate who suggested a full platform migration without being able to estimate the downtime risk or the migration cost. They had no idea. That alone revealed they lacked the operational depth for the role. Also, do not treat the interview as a one-way interrogation. A good COO interview has a conversational rhythm. Offer brief, relevant follow-ups that show you understand their world. Ask about the current operational priorities they are most worried about. It demonstrates genuine interest and gives you material to tie your experience back to their actual problems.
When This Approach Falls Short
Not every COO values the same things. Some are deeply hands-on technical operators who want granular detail. Others are more strategic and care about vision and execution alignment. If the role is early-stage and the COO is still building the function from scratch, they may prioritize builders over optimizers. A candidate who only talks about refining existing processes might sound irrelevant to someone who needs to create processes from nothing. Adjust your framing based on the company stage and the COO's known background. Check their LinkedIn, previous companies, and any public interviews they have done. It takes five minutes and prevents a major mismatch. There is also a limit to preparation. If you are interviewing at a company where you genuinely lack domain knowledge, no amount of framing will compensate. In that case, lean hard on transferable operational principles and be transparent about the learning curve. Overconfidence in unfamiliar territory is the fastest way to lose credibility.
