How to Prepare for a Case Interview

A recruiter just told you there’s a case round on your calendar, and you’re not sure where to start. Case interviews reward a specific, learnable skill set: structuring an ambiguous problem out loud, doing clean math under pressure, and narrating your thinking so an interviewer can follow it. None of that is intuition. It’s a method, and you can build it in about four weeks with the right practice.

Most candidates either over-prepare on frameworks they never learn to apply, or panic-practice the week before and burn out on cases without absorbing anything. The plan below spends the first two weeks on structure and the last two on speed and communication, which mirrors how the skill actually develops.

The fastest way to prepare for a case interview is a four-week plan: weeks one and two build your structuring method and math speed through untimed practice, weeks three and four add a live partner and a strict clock. Twenty to thirty completed cases, most of them with a partner, is a realistic target before a real interview.

What actually gets tested in a case interview

Case interviews look like they’re testing whether you know the “right” business answer. They’re mostly testing four things:

1. Structure. Can you break an ambiguous problem into a logical set of drivers, live, without a script.
2. Quantitative skill. Can you do accurate mental math and sanity-check your own numbers.
3. Business judgment. Do your ideas and your final recommendation make sense given the facts you gathered.
4. Communication. Can the interviewer follow your thinking as you go, and do you engage with them like a colleague rather than presenting to a wall.

An interviewer who has run hundreds of these cares less about whether you land the exact number they have in their notes and more about whether they’d want to sit in a room with you while a client is upset.

A four-week case interview prep plan

Week 1: Learn the underlying structures, untimed

Study four or five case types until you understand the logic behind them, not just their names: profitability, market entry, market sizing, and one operations or growth case. For each, learn what drivers it typically breaks into (revenue versus cost, price versus volume, market size versus share) and practice building a tree for a made-up prompt with no clock running. Read two or three worked case examples all the way through and pause after each interviewer line to predict what you’d ask next, before reading their answer.

Week 2: Add math speed and a repeatable opening

Drill mental math daily for 15 to 20 minutes: percentages, quick multiplication, weighted averages, and back-of-envelope estimation. Slow, wrong math in the room is one of the fastest ways to lose an interviewer’s confidence, and it’s the most fixable weakness with the least glamorous practice.

Also build a repeatable opening you can use on any case: restate the problem in your own words, ask two or three clarifying questions, take thirty seconds of silence to sketch a structure, then walk the interviewer through it before you start digging into any branch.

Week 3: Start timed cases with a partner

Move to full 25 to 35 minute cases with a live partner, ideally someone who has actually interviewed candidates or been through the process recently. Time every case and debrief immediately after: what forced you to hesitate, where your structure was too generic, where the math slowed you down. Do four to six cases this week, aiming for variety across case types so you’re not just getting better at one shape of problem.

Week 4: Simulate the real interview

Do your remaining cases under conditions as close to the real thing as possible: video call, no notes prepared in advance, a stranger or near-stranger as the interviewer, and a hard stop at the time limit. Two or three cases in the final week, plus a light review of your notes from weeks one through three, is enough. More than that this close to the interview usually adds fatigue rather than skill.

Week	Focus	Format
1	Learn structures	Untimed, solo
2	Math speed, repeatable opening	Untimed, solo, daily drills
3	Timed practice	Full cases, live partner
4	Realistic simulation	Full cases, stranger interviewer, hard clock

Do I need to memorize case interview frameworks?

Learn the logic behind four or five common structures well enough to rebuild them from scratch, and stop there. Frameworks are meant to be raw material for a structure you build live, not a script you recite. An interviewer can tell within the first thirty seconds when a candidate is pattern-matching a memorized tree onto a problem it doesn’t actually fit, and it costs you more credibility than a slightly clumsier but genuinely custom structure would.

Case interview examples worth practicing

Practice a range, since firms and roles differ:

• Profitability case: “Our client’s profits have dropped 20% over two years, what’s going on.” Structure around revenue drivers (price, volume, mix) and cost drivers (fixed, variable), then narrow based on the numbers you’re given.
• Market entry case: “Should our client enter the electric bike market in this country.” Structure around market attractiveness, the client’s ability to win, and the financial case for entering.
• Market sizing case: “How many coffee cups are sold in this city each day.” Structure around a clear population breakdown and stated assumptions, and sanity-check your final number out loud against something you know.
• Growth or operations case: “A retailer wants to grow revenue 15% next year, where should they focus.” Structure around the levers available (new customers, more per customer, new channels, new products) and evaluate each against feasibility and size of impact.

If you’re aiming at consulting, strategy, or product roles specifically, also skim how those interviews layer behavioral questions on top of the case, since firms increasingly ask both in the same round. Our guide to common interview questions and how to answer them covers the behavioral side.

Mistakes that sink strong candidates

• Diving into numbers before building a structure. It feels productive and reads as scattered. Always sketch the tree first, out loud or on paper, before touching a single number.
• Silence that goes on too long. Thirty seconds to think is fine and expected. A full minute of silence with no signal to the interviewer about what you’re doing reads as stuck, even when you’re not.
• Ignoring the numbers you’re given. If the interviewer hands you a chart or a data point, use it. Cases are built around specific numbers for a reason, and skipping them to talk in generalities is a common tell of under-preparation.
• A recommendation with no “so what.” Ending with “the market looks attractive” is not a recommendation. End with a specific action, a reason, and one risk you’d flag before moving forward.
• Treating the interviewer as an audience instead of a partner. The best candidates check in (“does that structure make sense before I go further”) and adjust based on the interviewer’s reaction. Candidates who talk straight through without checking in miss cues that would have saved them a wrong turn.

The week before the interview

Stop learning new content three to four days out. Instead, review your own notes from practice cases, redo the two cases where you struggled most, and get one final live case in with a partner two days before. Sleep and a clear head the morning of do more for your performance at this stage than one more framework would.

If you want live, timed practice with someone who has actually sat on the hiring side of these interviews, interview prep coaching runs full mock cases and gives you specific, blunt feedback on exactly where your structure or your delivery breaks down. Take the two-minute quiz and get matched with a coach before your case round.