A case interview is one of the few interview formats where the test is mostly about how you think, on purpose, in real time. There is no whiteboard problem you can grind through. There is a vague business prompt, an interviewer who answers questions and shares numbers when asked, and roughly 25 minutes for you to produce something defensible.

People who didn't do consulting recruiting in business school find this terrifying. It isn't, really — the format rewards structure more than knowledge, and the structure is learnable in an afternoon. This post is the skeleton that gets you through a real case without two months of practice.

The four moves that hold a case together

A case interview is not a math test. It's a structured conversation with a number at the end. The four moves above are roughly invariant across consulting firms, corporate-strategy interviews, and product-strategy rounds at tech companies. The names of the moves change. The shape does not.

The most underrated move is the first one. Restating the prompt sounds like a stalling tactic. It isn't. About a third of candidates misunderstand the question — they hear "enter the European market" and start estimating the size of France's coffee market when the question was really about make-or-buy. Restating catches this in 30 seconds. It also buys you a moment to think.

The second move — structuring out loud — is where most candidates either freeze or over-engineer. The interviewer is not grading the elegance of your framework. They are checking that your thinking has a shape someone else can follow. A clean two-by-two beats a beautiful four-by-four that you can't navigate when the time pressure hits.

The third move is the case itself. Pick the branch that's most likely to drive the answer, dig in, do arithmetic out loud, and surface implications as you find them. Most cases are won or lost on whether you can shut up about the other branches once you've picked one.

The fourth move is the recommendation. Lead with the answer, then your reasons, then a single caveat. Then stop. Trailing off into "but it could also be X, or Y, or maybe Z" undoes a clean case in 20 seconds.

Where candidates actually lose

The quadrant is the most honest map of case performance. The plurality of rejections cluster in the bottom-left — weak structure and weak math at once — and almost all of those candidates are recoverable with two or three practice cases.

The interesting failure mode is the upper-left: strong math, weak structure. Engineers and analysts transitioning into strategy roles often hit this. They can size a market in their head but the interviewer can't tell how they got there. The fix is mechanical — write the tree down, label the branches, name the assumption before you do the arithmetic.

The opposite failure — strong structure, weak math — is more common in candidates from non-quant backgrounds. The fix is slower: do arithmetic explicitly, on paper, and check the order of magnitude before you commit. "1.2 million times $40 is roughly 50 million in annual revenue" is what the interviewer wants to hear. Numbers without the sanity check read as luck.

How long the case actually runs

Most candidates blow their first case because they don't have a time budget. A 45-minute interview is roughly 5 minutes of intro, 25 minutes of case, 10 minutes of fit, and 5 minutes for your questions. If you're 12 minutes into structuring, you're already in trouble.

A workable internal clock:

• Restate and clarify: ~1 minute
• Structure: ~2 minutes
• Dig and analyse: ~15-18 minutes
• Synthesize: ~2 minutes

The rest is fit. If you can hold this rhythm, you've already separated yourself from most candidates who run long and arrive at the recommendation breathless.

What "structured thinking" actually looks like

The phrase "structured thinking" is over-used to the point of meaninglessness. Concretely, it's three habits:

Name the bucket before you enter it. "Let's start with the cost side." Don't drift into cost analysis without flagging it. The interviewer is taking notes; they want to know where on their page to write your next observation.

Surface the implication, not just the number. "Variable costs are roughly 60% of revenue" is a number. "Variable costs are roughly 60% of revenue, which means the breakeven volume is around 250k units — about twice their current run rate" is structured thinking. The implication is the move.

Recap before you switch branches. Every 3-4 minutes, summarize what you've concluded so far and check whether the interviewer wants you to continue or jump. This is the single highest-leverage habit in case interviews and almost no one does it.

How to prep in two weeks without the case books

If you have a real case interview coming up and no time for Case in Point end-to-end, the minimum viable prep is:

1. Read two sample cases out loud. Not your eyes scanning a transcript — out loud, in the format of an interview. This rewires your sense of pacing more than 10 silent reads.
2. Do three practice cases with a friend. Even a non-consultant friend can read a prompt and ask follow-up questions. The point is to talk through structure, not to perform.
3. Memorize one default framework you trust. Profitability (Revenue - Cost), market entry (Market, Competition, Capability, Risk), or 4Cs. You will adapt it in the room — but you need a starting shape to adapt from.

The math practice is separate. Five minutes a day of mental arithmetic — percentages, ratios, market sizing — does more for case performance than another five hours of frameworks. See tell-me-about-yourself-90-seconds for the fit portion that bookends the case.

What this isn't

A few clarifications:

• It's not a knowledge test. You will not be asked the size of the European insurance market from memory. If you don't know a number, you ask for it or estimate it out loud.
• It's not a single right answer. Two candidates can recommend opposite things and both pass, if their reasoning is clean.
• It's not adversarial. The interviewer wants you to succeed — they're trying to assess thinking, not catch you out. Treat them like a collaborator.

The short version: a case interview is a structured conversation with a number at the end. Master the four moves, hold your time budget, and the case stops being mystical. Most of the candidates beating you on case day have done six practice cases. You can match them in a weekend.