How to Prepare for a Case Study Interview

Case study interviews show up most often in consulting, strategy and product management hiring, and general business interviews are borrowing the format more each year. Instead of asking you to describe a past project, the interviewer hands you an unfamiliar business problem and asks you to work through it out loud, in real time. There is no script to memorise. What gets tested is how you think when you do not already know the answer.

What a Case Study Interview Actually Tests

A case study interview is not a quiz with a right answer hidden somewhere in the interviewer's notes. Most cases have several defensible recommendations, and interviewers are trained to follow whichever direction you take, adjusting the numbers and constraints as you go. What they are watching for is structure: can you break a vague, messy problem into parts that are actually useful to solve? They are also watching for comfort with ambiguity. A real case rarely gives you all the information you need up front, and how you respond when a fact is missing tells the interviewer more than any single calculation does.

This is why candidates who "know the answer" sometimes do worse than candidates who reason well out loud. The interview is measuring the process, not just the destination.

A Simple Framework for an Unfamiliar Problem

You do not need a complicated framework memorised from a case book. A simple sequence works for almost any business problem you will be handed live.

Start by clarifying the goal. Repeat the problem back in your own words and ask one or two questions that narrow it, such as what "success" means for this business or what timeframe matters. Then structure the problem into a small number of parts, three or four is usually enough, so both you and the interviewer can see the shape of your approach before you dive into any one branch. State your assumptions as you make them rather than silently baking them into your maths; if you assume the market grows at 5% a year, say so, and say why that number feels reasonable. Work through the numbers or the logic in front of the interviewer rather than retreating into your notes, narrating each step as you go. Finally, land on one specific recommendation rather than a list of options. A case interview that ends with "it depends" or three equally weighted alternatives has not actually answered the question.

How This Differs from a Technical Interview or a Take-Home

A technical interview usually has a correct answer, or at least a correct category of answer, and the interviewer is checking whether you can reach it. A case study interview is closer to the opposite: the path matters more than any single number, and two candidates can reach different recommendations and both do well, provided their reasoning holds up under questioning.

A take-home assignment gives you time. You can research the market, redraft your slides, check your arithmetic twice. A case study interview gives you none of that. The interviewer wants to see how you reason under time pressure, with an audience, without the chance to go away and think it over. That live, unscripted quality is the entire point of the format, and it is why reading case books alone rarely prepares candidates well enough on its own.

Common Mistakes

The most common mistake is jumping to a solution before the question has actually been clarified. Candidates hear "market entry" and immediately start talking about strategy, without checking what the client actually wants to know or what constraints already rule out half the obvious answers.

A close second is going silent while thinking. Interviewers cannot follow reasoning they cannot hear, and a long pause reads as being stuck even when you are not. Narrate your thinking, even the parts that feel obvious.

The third is skipping assumptions. If you use a number, whether it is a market size, a growth rate or a cost estimate, say where it came from and flag that it is an assumption rather than a fact. Interviewers push on assumptions specifically to see whether you can defend or revise them, and candidates who never stated one in the first place have nothing to defend.

How to Actually Practise

Reading case books silently teaches you the shape of common problems, but it does not build the skill the interview actually measures, which is thinking out loud in front of another person. Find a practice partner, even an informal one, and work through cases as if they were live interviews: state your assumptions, narrate your structure, and let the other person interrupt with follow-up questions the way a real interviewer would. Recording yourself and listening back also works, because it makes clear where you go quiet or start hedging.

A handful of practised cases with real feedback beats a stack of case books read alone. The goal is not to memorise more frameworks; it is to get comfortable narrating a problem you have never seen before, in the room, under time pressure.

Related guides

• How to prepare for an assessment centre
• How to prepare for a technical interview