Case Interview

An interview format where candidates work through a business problem in real time — the dominant hiring method in management consulting.

A case interview is a live problem-solving exercise where the interviewer presents a business scenario — 'how would you evaluate whether our client should enter the Chinese market?' or 'our client's profits have declined 20% over three years — how would you diagnose that?' — and the candidate works through a structured analysis out loud. Case interviews are the dominant hiring method in management consulting (McKinsey, BCG, Bain, Deloitte, and their peers) and are widely used in strategy, operations, and business development roles at large companies.

Case interviews are not about knowing the answer. There rarely is one correct answer, and experienced interviewers are explicitly not looking for candidates who arrive at a specific conclusion. They're evaluating how you think: whether you structure ambiguous problems logically, whether you ask the right clarifying questions before diving in, whether you can perform quick mental estimates, and whether you communicate insights clearly under pressure. A candidate who reaches a mediocre conclusion through excellent structured reasoning typically scores higher than one who lands on a correct answer through a disorganized process.

Preparation for case interviews requires more dedicated practice than any other interview format. Most successful candidates spend 30–100 hours on deliberate preparation: learning 2–3 core analytical frameworks (profitability trees, market entry frameworks, growth strategy), mastering mental math, and doing repeated practice cases — ideally with a partner who can give real-time feedback. Case performance is a learnable skill, not a measure of raw intelligence, and candidates who don't prepare for the format specifically almost always underperform relative to their actual analytical ability.

Case interviews come in two structural types: interviewer-led and candidate-led. In interviewer-led cases (common at McKinsey), the interviewer guides the direction, asking questions sequentially and steering the analysis. In candidate-led cases (common at BCG and Bain), the candidate must drive the structure, ask their own clarifying questions, and determine what to analyze. Knowing which format you're walking into shapes how you open the case. In candidate-led cases especially, your opening structure — the framework you lay out before diving in — is the highest-stakes moment of the interview.

How to Prepare

  • Learn 2–3 core frameworks: profitability analysis, market entry, and growth strategy — then adapt them rather than applying rigidly.
  • Practice with partners: solo case prep builds knowledge; live practice with another person builds the performance, communication, and pressure-handling the format actually requires.
  • Use established resources: Case in Point (Cosentino), Victor Cheng's LOMS, and firm-specific case libraries available on consulting firm websites.
  • Master mental math: rough estimates and back-of-envelope calculations are expected throughout — practice until calculations are fast and confident.
  • Drill your opening structure: the 60 seconds after you hear the prompt — clarifying questions, framework layout — is the highest-stakes moment in most cases.

What Strong vs. Weak Performance Looks Like

  • Strong: Pauses to structure before speaking, asks one or two sharp clarifying questions, lays out a logical framework, narrows efficiently, and synthesizes clearly at the end.
  • Strong: Does math confidently and checks reasonableness of estimates — 'that implies the market is $2 billion, which seems plausible given X.'
  • Weak: Dives into analysis immediately without structuring the problem — produces a scattered discussion that's hard to follow.
  • Weak: Goes silent under pressure instead of narrating thinking out loud — interviewers can't evaluate reasoning they can't hear.
  • Weak: Rigid framework application — forcing every case into the same template regardless of fit.
  • Weak: Reaching a conclusion without synthesizing — stating facts without recommending an action.

Example

In a McKinsey case interview, the interviewer says: 'Our client is a pharmaceutical company whose profits have declined 20% over three years. How would you begin diagnosing the problem?' The candidate structures a framework: revenue (price × volume, broken down by product line) and cost (COGS, R&D, SG&A), then asks which dimension has driven most of the decline. The interviewer says revenue is the primary driver. The candidate narrows further: 'Is this volume-driven, price-driven, or a mix, and which products are most affected?'