What are the three types of executive interview questions?

Judgment, scope, and fit — and interviewers rarely separate them. Judgment holds up well live, since you can watch someone reason and push back in real time. Scope falls apart live, because the candidate is the only witness to their own history and has every reason to describe it generously. Fit is useful color for the hiring decision, but it isn't something an interview can score as fact.

Why doesn't a polished answer in an executive interview tell you much?

A polished answer is a narrative the candidate has already tested on other interviewers and kept the parts that worked, not evidence. A good answer to 'tell me about a time you led change' tells you the candidate is good at answering that question — it does not tell you whether they can lead change in this role.

How do you ask an executive scope question that is hard to fake?

Ask for the org chart two layers down the quarter before they left, what decisions in their scope needed someone else's sign-off, and the specific number that changed while they were there — headcount, budget, or market count. Each produces something a reference call can independently confirm, which 'tell me about your scope' never does.

What is the 'third follow-up' technique for interviewing senior executive candidates?

Practiced candidates are fluent in the first answer and much less fluent by the third follow-up, because it usually was not part of the prepared story. Plan the third follow-up before the interview starts — deciding it in the room, after a smooth first answer, is when interviewers talk themselves out of asking it.

Executive Interview Questions That Work

Q: Is there research evidence that structured interviews actually predict performance better?

Yes. Schmidt and Hunter's 1998 meta-analysis of selection methods, published in Psychological Bulletin, found that structured, standardized interviews predict job performance meaningfully better than unstructured, free-form ones — the same logic that favors a question producing a checkable answer over one producing a good story.

Q: What can't an executive interview confirm on its own?

It cannot independently verify a scope claim, only make an inflated one harder to sustain. It cannot show how someone actually behaved under pressure two jobs ago, only how they describe it now. That is why research and reference checks exist as separate steps rather than folded into a longer interview.

Search “executive interview questions” and every result is a list. Twenty prompts, thirty prompts, grouped by competency, ready to read off a page. The problem is not that the questions are bad — most of them are fine, as questions go. The problem is that they are the questions everyone has, which means the person across the table has answered most of them before and has a polished answer ready before you finish asking.

A polished answer is not evidence. It is a narrative the candidate has already tested on other interviewers and kept the parts that worked. Getting a good answer to “tell me about a time you led change” tells you the candidate is good at answering that question. It does not tell you whether they can lead change here.

What a question is actually testing for

Before asking anything, it helps to be explicit about what category of information the question is even capable of producing. Interview questions at executive level tend to fall into three buckets, and most interviewers do not distinguish between them:

Judgment questions. How does this person reason through a real trade-off? These work well live — you can watch the reasoning happen and push back on it.
Scope questions. What did this person actually own, and how big was it? These work poorly live, because the candidate is the only source in the room and has every incentive to describe scope generously. A CV already asserts scope; asking the same question again in a different tone does not add evidence, it adds a second assertion from the same person.
Fit questions. How does this person operate day to day — communication style, what they need from a boss, how they handle disagreement? These work live but are read, not scored — inputs to judgment, not confirmable facts.

The failure mode is treating all three the same way: asking a scope question and accepting a fluent answer as if it were a judgment question with a reasoning path to evaluate. It has neither. It has a claim, delivered well.

Why the standard bank produces narrative, not evidence

“Tell me about a time you led a major change initiative” is a scope-and-narrative question wearing a judgment question’s phrasing. The candidate picks the anecdote, controls the framing, and decides which details to include. Nothing in the format forces the story to reconcile with anything outside the room.

That is fine for a first-round screen, where the goal is simply to see if someone can construct a coherent account of their own work. It is not fine for the round meant to separate finalists, because by then every candidate has told a version of this story enough times that fluency has stopped correlating with the thing you actually want to know.

This is not just a hunch about interview mechanics. Structured, evidence-anchored interviewing has one of the more robust track records in personnel psychology — Schmidt and Hunter’s 1998 meta-analysis of selection methods, published in Psychological Bulletin, found that structured, standardized interviews predict job performance meaningfully better than unstructured, free-form ones. The same logic extends one level down: a question that produces a checkable answer is a step further toward structure than a question that produces a good story, even inside an interview that is nominally “structured” on paper.

Probing scope claims the CV asserts but cannot prove

Reconstructing scope from evidence rather than reading it off a title is the research-desk version of this problem. The interview-room version is asking questions that make an inflated scope claim hard to sustain rather than easy to restate.

A few patterns that do this:

Ask for the org chart, not the headline. “Walk me through who reported to whom, two layers down, the quarter before you left.” A real operator answers this specifically. Someone describing scope they did not actually carry slows down, generalizes, or reaches for the title again.
Ask what they did not control. “What decisions in that scope needed sign-off from someone else?” Real ownership comes with real boundaries the person can name unprompted. A generously described role tends to have suspiciously few.
Ask for the number that changed while they were there. Headcount, plant count, budget, market count — whatever the scope metric is for the role. “What was it when you started, what was it when you left?” That produces something a reference call can independently confirm, which “tell me about your scope” never does.
Ask about the failure inside the success story. Someone who can describe a specific decision that did not work was actually making decisions. Someone who reframes the question into another win was probably closer to the edge of the scope than the résumé suggests.

None of these are cleverer than the standard bank. They are aimed at producing something checkable instead of something well told.

When the candidate is better at interviewing than you are

At senior levels this happens more than most interviewers admit. Someone who has been through a dozen executive processes has effectively trained on the format — they know which questions are coming and how to redirect a conversation back toward a story they are comfortable telling.

The interviewer’s leverage here is not asking harder questions. It is refusing to move on. A practiced candidate is fluent in the first answer and much less fluent in the third follow-up, because the third follow-up usually was not part of the prepared story. “What did the team think of that decision at the time?” “Who disagreed with you, and were they right?” “What would you do differently with six more months?” — not trick questions, just past the point where a rehearsed answer holds up. If every answer stays equally smooth three questions deep, that is itself a data point, not a reassurance.

Plan the third follow-up before the interview starts. Deciding it in the room, after a smooth first answer, is when interviewers talk themselves out of asking it.

Where the interview stops

Even a well-run interview cannot do everything. It cannot independently confirm a scope claim — only make an inflated one harder to sustain. It cannot tell you how someone actually behaved under pressure two jobs ago, only how they describe it now. And it cannot substitute for what a reference who worked alongside the person can add: whether the story holds up when someone else tells it.

That is not a flaw in the interview — it is why the research and reference stages exist as separate steps rather than folded into a longer interview. The interview is good at judgment in real time and at pressure-testing a narrative. It is structurally weak at anything that depends on the candidate being the only source in the room. Sending scope questions to research and reference, instead of asking the interview to do both jobs, is what keeps a final-round assessment from resting on how well someone tells their own story.

What “confirmed” actually means once a claim leaves the interview room and needs an outside source is the next layer of this same discipline — and getting the brief specific enough that the interview knows what it is checking for is the layer before it. The interview, the research, and the reference calls are three different instruments; the mistake is expecting any one of them to do the other two’s job.