Published 8 min read
Clarifying Questions in Case Interviews: What to Ask First
Good clarifying questions in a case interview do three things. They confirm you understood the prompt correctly, they fill in a gap the interviewer left on purpose, and they narrow the scope enough that you can build a real structure instead of guessing. Ask two or three, tied directly to the objective, right after you restate the prompt. Skip anything the prompt already answered, skip anything with no bearing on the objective, and stop before you drift into stalling.
I conducted well over a hundred McKinsey interviews, and clarifying questions were one of the first places a candidate revealed how they think. Not because the questions themselves were brilliant. Because most candidates either skipped this step entirely and charged into a structure built on a wrong assumption, or asked so many disconnected questions that it looked like they were buying time. Both read badly. Here is how to do the version that reads like a consultant.
Why this step exists at all
The case prompt you're handed is deliberately incomplete. Interviewers leave holes in it on purpose, partly to see if you notice, and partly because real client problems arrive incomplete too. Nobody hands a McKinsey team a fully scoped brief on day one. Someone on the team has to ask the questions that turn a vague situation into a workable problem.
So this step is not a formality before the "real" case starts. It is part of the case. The interviewer is scoring how you handle ambiguity from the very first exchange, before you've drawn a single branch of your structure.
The three types of question worth asking
Almost every good clarifying question falls into one of three buckets.
The first is a scope question. What exactly is in bounds here. If the prompt says "our client's profits are falling," does that mean the whole company or one division? Is a specific geography or product line off limits? Getting this wrong means you build a structure for a different problem than the one being asked.
The second is a definition question. Case prompts often use a word that has more than one reasonable meaning. If the case is about "market share," ask whether that means share of revenue or share of units, because the two can move in opposite directions and you do not want to discover that thirty minutes in.
The third is a constraint question. Is there a deadline, a budget ceiling, or a stakeholder who has already ruled something out. A client that has explicitly said "we will not lay anyone off" changes which branches of your tree are worth pursuing. You want to know that before you spend five minutes down a dead branch.
What not to ask
The fastest way to look unprepared is asking a question the prompt already answered. If the interviewer told you revenue is 400 million and margins have compressed from 22 percent to 14 percent over two years, do not ask "so is this a profitability case." You already have the numbers. Restate them back, do not ask about them again.
Also skip questions with no connection to the objective. Asking about the client's headquarters location or how many employees work in a department that has nothing to do with the problem tells the interviewer you're filling time, not thinking. Every question should trace back to something you'll actually use in your structure or your math later.
And skip questions that ask the interviewer to solve the case for you. "What do you think is driving the decline" is not a clarifying question, it's an attempt to get the answer handed to you. Interviewers notice this instantly, and it costs you more than it saves.
How many, and when
Two to three questions is the right range for almost every case. One is usually too few, because it suggests you either understood everything immediately, which is rare, or didn't look hard enough for gaps. Five or more starts to feel like a stall, and by question four the interviewer is often just waiting for you to get to the point.
Ask them right after your opening restatement, before you take your structuring pause. The sequence that reads well is: restate the facts, confirm the objective, ask your two or three questions, then say you'd like a moment to structure your approach. Doing it in that order shows a clean, deliberate process rather than a scattered one.
A worked example
Say the prompt is that a regional grocery chain's profits have fallen despite steady revenue. A candidate who skips clarifying questions might jump straight to a cost-side profitability tree. A candidate who asks well might say something like this instead.
First, is the profit decline happening across all stores or concentrated in specific locations. Second, when the prompt says costs, does that include one-time items like a recent acquisition, or only ongoing operating costs. Third, is there a target profit level the client has in mind, or are we simply diagnosing the cause.
Each of those questions changes what the candidate builds next. If the decline is concentrated in a handful of stores, the tree looks completely different than if it's uniform across the chain. That's the entire point. A clarifying question that doesn't change your next move wasn't worth asking.
Good versus weak clarifying questions
| Weak question | Better version | Why it's better |
|---|---|---|
| What is this case about | Is the profit decline concentrated in specific stores or spread across the chain | Ties directly to how the structure will branch |
| How big is the company | Does "market share" here mean share of revenue or share of units | Resolves an ambiguity that changes the analysis |
| What do you think caused this | Has the client already ruled out any options, like layoffs or price increases | Surfaces a real constraint instead of asking for the answer |
| Can you repeat the numbers | Let me confirm: revenue is flat at 400 million, and margin fell from 22 percent to 14 percent over two years | Shows synthesis, not just repetition |
Common mistakes I saw as an interviewer
The single most common mistake was asking a question purely to fill silence. Candidates sometimes feel like they need to say something clever before they think, so they reach for a question that sounds sophisticated but doesn't connect to anything. I could tell within a sentence when a question was generated on the spot to look thorough rather than because the candidate actually needed the information.
The second mistake was treating clarifying questions as a checklist to complete rather than a tool to use. Some candidates had clearly memorized "always ask about the timeline, the competition, and the goal" and asked all three regardless of whether the case needed it. A market sizing case rarely needs a timeline question. Asking it anyway signals memorization over thinking, which is exactly what case interview frameworks done badly look like.
The third was silence. Some strong analytical candidates skipped this step entirely because they were eager to show off their structure. They'd build an impressive tree on a wrong assumption, and the whole case would drift for ten minutes before anyone noticed. If you want to see how this step fits into the broader case flow, how to structure a case interview walks through what comes immediately after.
Interviewer-led versus candidate-led cases
The number and type of clarifying questions shifts slightly depending on the case format. In an interviewer-led case, common at firms like McKinsey, the interviewer is steering more actively, so your questions can be tighter and fewer, because you'll get more guidance as the case unfolds. In a candidate-led case, common at BCG and Bain, you're driving more of the analysis yourself, so getting the scope right at the start matters even more, since you won't have as many checkpoints to course-correct. If you're not sure which format you're walking into, interviewer-led versus candidate-led cases breaks down the difference in more detail.
If you've never sat through a full case before, it helps to see the whole arc first. What is a case interview covers the format end to end, including where this step sits relative to the math and the recommendation.
The bottom line
Clarifying questions are not a warm-up exercise before the real case begins. They are the first piece of evidence an interviewer has about how you think under ambiguity. Ask two or three, make each one earn its place by connecting to your objective, and skip anything the prompt already told you. Get this part right and your structure starts on solid ground instead of a guess. For a longer look at the mistakes that follow when this step goes wrong, see the most common case interview mistakes.
Go deeper
This is one small piece of the Interview Dance, the sequence I teach for running a full case cleanly from the first sentence to the recommendation.
Get the complete Cut to the Case course →
One payment, lifetime access, 30-day guarantee.
Frequently Asked Questions
How many clarifying questions should I ask in a case interview?
Two to three is the right range for almost every case. Fewer suggests you didn't look for gaps in the prompt, and more starts to feel like you're stalling before you actually engage with the problem.
When should I ask clarifying questions during a case?
Right after you restate the facts and confirm the objective, and before you take your pause to build a structure. Asking them in that order shows a clean process rather than scattered thinking.
What is a good clarifying question in a case interview?
One that changes what you'll do next. Good questions resolve scope, such as which part of the business is in play, resolve a definition, such as what a term like market share means here, or surface a constraint the client has already set, such as a ruled-out option.
Should I ask what caused the problem as a clarifying question?
No. Asking the interviewer to diagnose the case for you reads as an attempt to skip the actual work, and interviewers notice it immediately. Your questions should gather information you'll use, not request the answer.
Is it bad to ask no clarifying questions at all?
Usually, yes. Case prompts are built with intentional gaps, and skipping this step often means you build a structure on an assumption you never confirmed. Even a strong analytical candidate loses points if the whole case drifts because of one wrong assumption made at the start.
Do clarifying questions differ between interviewer-led and candidate-led cases?
Slightly. Interviewer-led cases give you more guidance as the case unfolds, so tight, minimal questions work well. Candidate-led cases put more of the driving on you, so getting the scope right at the very start matters more since you have fewer checkpoints to correct course later.