Clarifying Questions to Ask in a Case Interview
Good questions to ask in a case interview do one of two jobs: they pin down what the client wants before you draw a structure, or they get you the right number once the analysis is under way. The 52 questions here run in the order a case does: the objective, the client, the problem, the ground rules before you structure, the data and math in the middle, and wrapping up. Treat the clarifying questions in the first three groups as a menu and pick the two to four that would change your structure.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
Objective
Before I start, can I check the objective? The client wants to decide whether to enter this market, is that right?
Why ask it
Restating the prompt in your own words is the one clarifying question worth asking in every case. It catches the misread that would otherwise cost you the whole interview, and it gives the interviewer an easy moment to correct you before anything is built on it.
Is the goal profit specifically, or revenue, or something else?
Why ask it
Growth, share and profit lead to different structures, and a prompt about improving performance rarely says which. If the interviewer says profit, you have effectively been handed the top of your tree.
Is there a specific number the client is trying to hit?
Why ask it
A stated target turns the case quantitative and tells you what your recommendation has to clear. When there is no target, say you will treat it as directional rather than inventing a threshold later and getting attached to it.
What is prompting this now?
Why ask it
The trigger reveals what the client actually wants, which may differ from the stated question: a board demand, a new competitor, an expiring contract. It often comes with a date, which is the nearest thing to a deadline the case will give you.
Is the client deciding whether to do this at all, or how best to do it?
Why ask it
A go or no-go decision ends in a yes or a no with conditions, and a how question ends in a plan. Prompts about launches and acquisitions blur the two, and a should-we structure for a client that has already decided wastes your first ten minutes.
Is the client thinking about the next twelve months or a longer horizon?
Why ask it
A fix that has to pay back within a year rules out most new products and new plants, while a five-year view lets them in. The horizon also sets the period for any payback or break-even sum later, so write it next to the objective.
Does the client have any goals beyond the main one that I should keep in mind?
Why ask it
Secondary goals, such as keeping the workforce, protecting a brand or holding share, often decide between two options that look equal on profit. If the reply is no, take it and move on.
Who is making this decision, and what do they care about most?
Why ask it
Most useful in organizational and change cases. A founder, a newly arrived chief executive and a divisional head weight cash, growth and risk differently, and the recommendation should be addressed to whoever is deciding.
The client
Could you tell me a little about what the client does and how it makes money?
Why ask it
Ask this when the industry is unfamiliar, and ask it plainly rather than bluffing. Interviewers expect it for niche businesses, and a wrong assumption about the revenue model will misdirect every branch of your analysis.
Which products or business lines are in scope?
Why ask it
Multi-line businesses often have the problem sitting in one line. If the answer narrows it, you have avoided a market-wide analysis of something the client does not care about.
Which geographies are we looking at?
Why ask it
Assuming one country when the client is regional, or the reverse, changes market sizing and competitive dynamics entirely. It is a one-word answer, which makes it cheap to ask and expensive to skip.
Are we looking at the whole market or a particular segment?
Why ask it
This decides whether segmentation belongs in your framework or has already been done for you. An answer of the whole market is a hint that segmenting will be where the insight comes from.
Who are the client's customers: consumers, other businesses, or both?
Why ask it
Selling to a handful of large accounts and selling to millions of shoppers are different problems. One is about contracts and concentration, the other about price, channel and brand, and the reply tells you how to segment later without guessing.
How does the product reach the customer: direct, through distributors, or online?
Why ask it
Channel is where margin often goes missing, and the prompt rarely mentions it. If a retailer or distributor sits in the middle, there is now a party whose incentives belong somewhere in your structure.
Roughly where does the client sit in its market: the leader, one of several, or a small player?
Why ask it
A leader defending share and a challenger trying to take it get different advice from the same numbers. You do not need an exact share yet. A rough position is enough to decide whether competitor response deserves its own branch.
Does the client have particular strengths, such as a brand, a patent or a distribution network, that I should factor in?
Why ask it
In market entry and growth cases the answer is usually the reason the client can win at all, and it belongs in your recommendation by name. If there is nothing distinctive, state that as a risk instead of leaving it out.
Is the client a standalone company, or is it part of a larger group or owned by an investor?
Why ask it
A parent company or a private equity owner changes what counts as success: savings shared with sister businesses, or a sale a few years out. It can also explain a constraint that would otherwise look odd, such as a cap on investment.
The problem
When did this start, and how has it moved since?
Why ask it
A sudden change points at one event: a competitor entering, a contract lost, an input price. A slow drift points at structural causes. Getting this early stops you building a framework for the wrong shape of problem.
How big is the change we are talking about, and from what starting point?
Why ask it
Prompts tend to say only that profit is 'down'. Whether that means two points of margin or half the profit tells you to look for several small leaks or one large cause, and it gives you a figure your analysis has to add up to at the end.
Is this affecting the whole business, or is it concentrated in one part?
Why ask it
If one region, product or customer group carries the whole problem, you know where to look before you have spent any structure on it. The interviewer will often have that split ready, which is why it is worth asking this early.
Is this happening to competitors as well?
Why ask it
An industry-wide decline and a client-specific decline call for completely different recommendations. Skip it and you can spend twenty minutes on the client's internal costs when the answer was a shift in the market.
Has anything changed recently, inside the company or in its market, such as a new entrant, a new rule or a different supplier?
Why ask it
Keeping it this broad lets the interviewer hand you the event the case is built around. Hearing that nothing has changed is useful too: you are then looking for a slow structural cause and not a shock.
Does the client have its own view on what is causing this?
Why ask it
Management's theory is a free hypothesis. Test it first, then either confirm it quickly or explain why the evidence points elsewhere. Both make a stronger story than ignoring what the client believes.
Has the client already tried anything?
Why ask it
What has been tried and failed is a fact interviewers tend to hold back until someone asks. Knowing it keeps you from recommending something the client abandoned last year, and the reason it failed is often a clue to the real cause.
Are there constraints I should know about, such as capacity, capital or regulation?
Why ask it
Constraints eliminate branches of your tree before you waste time in them. Ask once, broadly, rather than checking each one individually as you go.
Is anything off the table, for example an acquisition or a price increase?
Why ask it
Cases are often written with one path fenced off. Finding it out early is far better than presenting a recommendation and being told the client would never do that, which leaves you rebuilding under time pressure.
Ground rules
Can I check one term? When you say attachment rate, do you mean the share of customers buying the add-on?
Why ask it
Always ask rather than guess. Confirming a definition takes five seconds and reads as precision, while a misunderstood metric produces a confident answer to the wrong question and is usually caught in the math.
Would you like me to lead the case, or will you take me through specific questions?
Why ask it
Formats differ between firms and sometimes between interviewers at the same firm, so ask if the prompt has not made it obvious. If you are leading, you pick the first branch and say why. If you are being guided, answer the question asked and resist drifting back to your own tree.
Should I ask you for data as I go, or work from estimates?
Why ask it
Some interviewers hold a folder of exhibits and release each one when you ask for the right thing. Others want every number built from assumptions. Knowing which saves you from requesting figures that do not exist, or estimating ones that were sitting on the desk.
Roughly how long do we have for the case, so I can pace myself?
Why ask it
If the recruiter already told you, skip it. When the slot is unclear, knowing whether you have twenty minutes or forty decides how deep to go on the first branch and when to start steering toward a recommendation.
Before I move on: we know the market is growing, margins are down and the client has not changed price. Have I missed anything important?
Why ask it
A short recap at the end of scoping catches the fact you noted wrongly and invites the interviewer to hand you anything they were waiting to give. Keep it to three facts, as here, so it sounds like a summary and not your notes read back.
Could I take a minute to think this through and come back with a structure?
Why ask it
Interviewers expect the request and it is rarely refused. Write the objective at the top of the page first, then the structure under it. Thinking aloud at this point is what produces a meandering framework.
Would it help if I turned my page toward you, or shall I talk you through the structure as I draw it?
Why ask it
Across a table the interviewer is reading your page upside down, and on a video call they cannot see it at all. Asking how they want to follow along is a small courtesy that also makes you number your branches and say them in order.
That is how I would approach it. Is there an area you would like me to start with?
Why ask it
Ask it after you have presented the structure, never in place of presenting one. In a guided case the interviewer will pick the branch. In a candidate-led one you may hear that it is your call, so have your first branch and the reason for it ready.
Data and math
Do we have revenue split by product, by region or by customer type?
Why ask it
A request for a specific cut gets you further than asking whether there is any data on revenue. Offer the cut you think matters most and say why. If that breakdown does not exist, the interviewer will often give you the one that does.
How do the client's costs divide between fixed and variable?
Why ask it
You need this for any break-even, capacity or volume question, and it changes the advice. A business with mostly fixed costs gains a lot from extra volume, and one with mostly variable costs gains little. If no split is offered, propose one and check it.
Is that figure annual, and is it for the client or for the whole market?
Why ask it
Numbers read aloud lose their labels. Mixing a monthly figure with an annual one, or a market total with the client's own slice, is how a correct method ends in a wrong answer. Write the unit and the period beside every number as it is given.
Would you like me to estimate that, or do you have a number I should use?
Why ask it
It shows you are willing to size the thing yourself while giving the interviewer the chance to save you the time. If the reply is to estimate, state your assumptions one at a time so each can be corrected before you multiply.
Is it all right if I round these numbers to keep the arithmetic clean?
Why ask it
Ask before you round, not after. Then say what you rounded and in which direction, so that at the end you can tell the interviewer whether your answer runs slightly high or slightly low.
Could I take a moment to read this exhibit before I comment on it?
Why ask it
Thirty quiet seconds on the title, the axes, the units and any footnote beats a fast first remark that misreads the chart. When you do speak, start with what the exhibit says overall and then the one thing that stands out.
Does this table show all of the client's products, or only a selection?
Why ask it
Exhibits are sometimes partial on purpose, with a row marked 'other' or a year left out. Knowing what was omitted stops you drawing a conclusion about the whole business from four lines of it.
Do we know how the client compares with its competitors on this measure?
Why ask it
A margin or a cost per unit means little with nothing beside it. A benchmark shows whether the gap is the client's own doing or the industry's. If none is available, say what you would want to check with the real client.
Could you repeat that last number? I want to be sure I wrote it down correctly.
Why ask it
Hearing it again costs a few seconds and nobody minds. A misheard figure carried through three steps of arithmetic costs minutes, and it is much harder to recover from with someone watching.
My answer comes out at roughly 12 percent. Does that sound plausible for this industry?
Why ask it
Sense-check it yourself first, against the size of the market or the client's current margin, and say that check aloud. Then the question invites a correction instead of handing the judgement to the interviewer.
I am not seeing a clear driver in what we have so far. Is there information on customers or competitors I could look at?
Why ask it
When a branch runs dry, say so and name what you would look at next. It is a far better use of a stuck moment than silence, and it shows you can tell having no answer apart from having no data.
Based on this, I would look at pricing next. Is that where you would like me to go, or should I stay with costs?
Why ask it
Saying where you want to go, and why, keeps you leading the case while leaving room for a redirect. Being redirected is not a mark against you. It usually means the interesting part of the case is elsewhere and the clock is running.
Wrapping up
Is there anything we have not covered that you would want me to consider before I conclude?
Why ask it
Ask it only if there is time, and before the recommendation, not after. Now and then it surfaces a piece the interviewer meant to hand over, and you can fold that into your risks or next steps.
We are close to time. Would you like a recommendation based on what we have so far?
Why ask it
An interviewer can only score a recommendation they have heard, so when a branch is still open and the clock is nearly out, offer to conclude instead of racing the arithmetic. Name the branch you did not reach as your first next step.
Could I take thirty seconds to pull my recommendation together?
Why ask it
Use the pause to write three lines: the answer, the two or three reasons with their numbers, and the risks or next steps. If you are told the chief executive has just walked in and wants it now, skip the pause and lead with the answer.
Now that we are finished, was there a point in the case where you would have gone a different way?
Why ask it
Some interviewers give feedback on the spot and some are not allowed to, so ask lightly and do not press. Whatever you hear is the most specific coaching you will get before the next round.
Was this based on a real engagement, and can you say what the client ended up doing?
Why ask it
Many cases are drawn from the interviewer's own projects, and people tend to enjoy being asked. It turns the last minutes from a test into a conversation, and the reply often shows which part of the problem mattered most in practice.
What made this problem hard for the team that worked on it?
Why ask it
A natural follow-up when the case was a real project and a general answer is allowed. It tells you something about the firm's work that a brochure cannot, and it leads into your own questions about the job.
How to ask questions in a case without stalling
Practical guidance for the conversation itself
How many to ask, and when
Two to four questions, then stop
Clarifying is scoping, not discovery. Confirm the objective, then ask the two or three questions that would change your structure. A candidate working through ten questions before proposing anything reads as someone stalling rather than someone thorough.
Do not ask what the prompt already told you
It is an unforced error, and it signals that you were not listening. Write the prompt down as it is read, and only ask about what is genuinely absent from your notes.
Ask, then say what you will do with the answer
'I would like to know whether competitors are also declining, because if they are I would focus on the market rather than the client's costs.' The second half of that sentence is what gets credit. The reply on its own is only information.
Separate scoping from testing a hypothesis
Clarifying questions come before your structure and are about what the problem is. Questions that test an idea come after, and asking them too early looks like guessing at the answer before you have framed it.
What to clarify by case type
- Profitability: whether the decline is in revenue or cost, over what period, and whether it is industry-wide.
- Market entry: the definition of the market, the geography, and what the client already owns that is relevant.
- Pricing: what is being priced, against what alternative, and whether the client has pricing power or is a follower.
- Growth: whether growth means revenue, volume or share, and whether it must come from existing customers.
- Operations: which step of the process is the constraint, and what the current performance actually is.
- Mergers and acquisitions: what the client is trying to gain, and whether the decision is whether to buy or how much to pay.
After the opening: questions in the middle and at the end
Ask for a cut, not for data
Once your structure is on the page, every question should come out of a branch of it. 'Do we know how volume moved in each region?' tells the interviewer which exhibit to hand over. 'Is there any more information?' tells them nothing, and it sounds as if you have lost the thread.
Label every number when it lands
Write the unit, the period and whose number it is beside each figure: client or market, per month or per year, thousands or millions. Most of the questions under Data and math exist to fill in one of those three labels before the arithmetic starts.
Close each branch aloud before opening the next
Say what the branch showed, what it means for the objective, and where you want to go next. That one sentence does the work of a question: the interviewer can agree, redirect you or hand over the next exhibit, and you never have to ask what to do now.
Keep the last questions about the case
The first three questions under Wrapping up get you to the recommendation. The last three are for the minute after it, while the case is still on the table. Questions about staffing, travel and promotion belong to the separate slot at the end of the interview, and they need their own preparation.
What loses marks
- Asking for numbers you are expected to estimate. Population, market size and average price are usually yours to build, not to request.
- A stream of yes or no questions with no reasoning attached to any of them.
- Not writing down the objective, then drifting away from it twenty minutes later.
- Asking about industry background at length when the interviewer clearly wants you to structure the problem.
- Accepting a vague objective. Improve performance is not something you can solve or measure against.
- Restating the prompt word for word rather than in your own words. It shows recall, not comprehension.
If the interviewer turns a question back on you
Being asked what do you think, or told to make an assumption, is normal and is usually a test rather than an obstruction. Give a specific assumption, say why it is reasonable, and flag that you will revisit it if the data disagree. If a question you consider central is refused outright, treat that as information: the case is probably meant to run without it, and continuing to push for it costs you time you will want later for the numbers.