A case interview is a simulation of a client engagement, compressed to 30–40 minutes. The interviewer plays a client, or your engagement manager, with a business problem: profits are falling, should we enter India, is this acquisition worth the price, how should we price the new product. Then they hand it to you with far too little information, on purpose. You are not being tested on whether you already know the answer. You are being tested on how you get to one: whether you impose structure on chaos, whether you can do arithmetic under mild social pressure, whether your business instincts are sound, and whether you communicate like someone a client would pay to be in the room.
Concretely, five things are scored, and every strong candidate is deliberately good at all five:
- Structure. Do you break the problem into a logical, gap-free tree before diving in, or do you free-associate? This is the single most heavily weighted dimension, because it is the one that transfers to real work.
- Quantitative fluency. Can you set up and execute case math cleanly, and sanity-check the result? Freezing on a number, or accepting an absurd one, both fail here.
- Business judgment. Do your hypotheses and recommendations make commercial sense? Do you know that airlines have high fixed costs and that software has near-zero marginal cost?
- Communication. Do you think out loud clearly, signpost where you are ("I'll look at three things; first…"), and lead with the answer when it's time to conclude?
- Poise and coachability. Are you calm when the interviewer pushes back, and do you use new data rather than cling to your first idea?
Advertisement
What is the six-beat arc of a case interview?
The six-beat arc. Every case, in every firm, follows the same underlying rhythm. Learn it as a reflex:
- Clarify (30–60 seconds). Play back the prompt in one sentence, confirm the objective and its metric (are we maximizing profit? market share? a 3-year return?), and pin the scope (which geography, which segment, what time horizon). One or two sharp clarifying questions; never a fishing expedition.
- Structure (2–3 minutes). Ask for a moment, then build a MECE tree tailored to this problem (see MECE and the issue tree and the profit tree). Present it top-down: "I'd like to look at three areas — A, B, C. Under A…". This is where you win or lose the case.
- Hypothesize (woven in). State where you suspect the answer lies and which branch you'd test first, and why (see hypothesis-driven structuring). This turns a framework into a plan.
- Analyze (the bulk). Walk the tree, request data, read exhibits, do the math (see case math under pressure), and update as facts arrive. Signpost constantly.
- Synthesize. Pull the threads into an insight: the "so what," not a recap of "what."
- Recommend (60 seconds). Answer first, two or three reasons tied to your analysis, then risks and the next step (see the 60-second recommendation).
Interviewer-led vs candidate-led case interviews
Two delivery formats. Interviewer-led (the classic McKinsey style) means the interviewer steers: they ask you a specific question, you answer, they hand you the next question and exhibit. Your structure still matters, but the interviewer controls the path. Candidate-led (the classic Bain/BCG style) means you drive: after structuring, you choose which branch to pursue, you ask for the data you want, and you decide when you have enough to conclude. Candidate-led is harder, because it also tests prioritization, but the underlying arc is identical. The two full cases on the module page are interviewer-led; the app's deeper track drills both. Before either room, most firms screen applicants with an online test: McKinsey's Solve, a game-based problem-solving assessment, and at other firms an online case or aptitude test whose form varies by office and year (as of October 2026, check on each firm's careers page).