What makes COO interview questions different from generic executive interview questions?

A 'VP Operations' or 'COO' title hides how much someone actually owned — a single-site plant, a multi-site network, or scope adjacent to real ownership. Generic leadership questions produce the same fluent answer from all three. The questions that discriminate ask for mechanics only the person who actually ran the operation can produce: how the P&L rolled up, the actual sign-off threshold, and whether the network grew organically or through acquisition.

How do you test whether a COO candidate really owned the P&L, not just described it?

Ask two things: how the number actually rolled up (site-by-site or consolidated by them), and what dollar figure required their sign-off before it escalated further up. Someone who genuinely held the authority answers both with a specific mechanism and a specific number, on the spot. A fluent 'I had full ownership' that never produces a threshold usually means the job was bigger in the retelling than it was in practice.

How do you tell if a candidate's regulated-industry experience is real, not just a sector label?

Ask for one specific audit they personally owned the response for, not a description of the compliance system generally. A candidate who has actually done this names the regulator, the finding, and the corrective action plan. Someone who only worked inside a system someone else built tends to speak in generalities and struggles to land on one instance.

Why ask about union experience directly instead of assuming it from the industry?

Labor relations is a discrete, learned skill, not a byproduct of general operational strength — a strong non-union operator has, by definition, never exercised it. Asking for a specific contract negotiation cycle or grievance handled directly produces a real answer naming the issue, the position taken, and the outcome, rather than general comfort working alongside a unionized workforce.

Can interview questions alone confirm a COO candidate's claimed scope?

No. Even a candidate who answers every mechanics-level question specifically has only demonstrated they can describe their own record convincingly under pressure — still one person's account. Confirming that account against an outside source, such as a filing, a plant announcement, or a reference who watched the work happen, is a separate step the interview cannot do on its own.

COO and VP Operations Interview Questions That Actually Discriminate

Search “coo interview questions” and the results are lists — twenty prompts about leadership style and cross-functional collaboration, interchangeable with a list for any other C-suite seat. That is the wrong shape for this particular role. Operations titles travel worse than almost any function’s, because the org chart follows the plant network rather than a repeatable template — which means the resume-level facts a generic interview list tests for are exactly the facts a COO or VP Operations candidate can describe fluently without having actually owned them. The questions worth asking are not more probing versions of “tell me about your operational experience.” They ask for the specific mechanics that only show up if the person actually ran the thing.

Why the standard list misses this role specifically

Most executive interview questions fail the same way regardless of function: they invite a rehearsed story instead of a checkable answer. Operations has an additional problem on top of that. A “VP Operations” or “COO” title tells you almost nothing about what the person actually owned. The scope hides behind the same words whether the candidate ran a single-site plant or a multi-site network, whether they held consolidated P&L authority or coordinated above site-level owners who each held their own number. A generic leadership question cannot surface that difference, because both candidates answer it the same way: in the language of the org, not the language of what they specifically controlled.

The interview questions that work for this role are the ones that ask for detail a person could only produce from inside the seat — the reconstruction work a research desk does from filings and trade press, compressed into questions a candidate has to answer live.

Questions that test P&L structure, not P&L language

Almost every operations candidate will say some version of “I owned the P&L.” That sentence is true of a site GM, a regional coordinator above several site GMs, and a network-wide COO, and it sounds identical coming from all three.

“Walk me through how the number rolled up — did each site own its own P&L, or did you consolidate across the network?” A candidate who actually did this can describe the mechanics: which line items sat where, how site-level numbers fed into a consolidated view, where the friction was in getting sites to report consistently. A candidate who was adjacent to this, reporting into someone who did it, tends to describe the org chart correctly but cannot describe the reporting mechanics, because they never had to reconcile them.
“What was your actual sign-off threshold — for capex, for headcount, for working capital?” A specific number. Someone who held real authority can usually produce one without pausing, and can say whose sign-off it escalated to above that threshold. “I had full ownership” with no number attached is the tell that the authority was described more generously than it was held.
“Was the network you ran built organically, or through acquisition?” These are different jobs wearing the same résumé line. Growing a network from scratch and integrating an acquired plant onto a shared operating system and reporting structure are distinct skills, and a candidate who only did one of them should be able to say so plainly rather than describing both as “growing the operation.”

None of these questions are adversarial. They just ask for the layer of detail that sits below the title — and a candidate who held the scope they claim can usually go there without effort.

The constraint set, asked as history rather than as a label

Regulated, unionized, and capital-intensive experience are not interchangeable, and a candidate’s resume rarely says clearly which of the three they actually carry. Asking about the sector name gets you the label. Asking for a specific instance gets you the history.

On regulated experience: “Describe an audit you personally owned the response for — not the system generally, one specific audit.” A candidate who has done this names the regulator, the finding, and what the corrective action plan actually involved. A candidate who has only operated inside a compliance system someone else built tends to describe the system in general terms and struggles to land on one specific engagement.
On union experience: “Walk me through a specific contract negotiation cycle or grievance you handled directly.” Labor relations is a discrete, learned skill, not a byproduct of general operational strength. A strong non-union operator has, by definition, never exercised it, and a real answer here names the issue, the position taken, and the outcome rather than a general comfort with “working alongside a unionized workforce.”
On capital intensity: “What was your capex planning horizon, and how did utilization or maintenance cycles inform it?” Asset-heavy operations run on planning cycles that behave nothing like an asset-light one’s — someone who has actually planned a multi-year capex cycle for owned capacity can describe the horizon and the trade-offs; someone whose experience is optimizing leased space usually cannot.

What a rehearsed answer sounds like next to a real one

The tell is rarely a wrong answer — it is a fluent one that never gets more specific no matter how the question is asked. A rehearsed answer stays in the register of the title: “we ran a large, complex, multi-site operation,” “I had full P&L ownership,” “I’m very comfortable in regulated environments.” A real answer moves down a level on the first or second follow-up, into a number, a name, or a specific event that a reference could independently confirm.

This is the same distinction a research desk makes when a title alone cannot tell you what someone actually ran: site count, consolidation structure, capex authority, organic growth versus acquisition integration. The interview cannot pull investor materials or trade-press coverage the way a research pass can, but it can ask for the same layer of specificity live, and a candidate’s ability, or inability, to produce it on the spot is itself useful signal.

Where this still needs the next step

Even a candidate who answers every one of these questions specifically has only demonstrated that they can describe their own record convincingly under pressure — which is closer to the truth than a rehearsed answer, but still one person’s account of their own scope. Confirming that account against an outside source — a filing, a plant announcement, a reference who watched the work happen — is a separate step, and the interview was never going to be able to do it alone. What the questions above are for is narrower and still useful: making it harder for a candidate who was adjacent to an operation to sound the same in the room as the person who ran it.