Networking gets you the consulting interview. The case interview gets you the offer. It is the single biggest differentiator in MBB and top-firm recruiting, and it is also the most learnable, because it rewards structured practice. This guide covers what a case interview is, how to prepare efficiently, and the mistakes that quietly sink otherwise strong candidates.
What a case interview is
A case interview is a business problem you solve out loud with the interviewer, usually in 20 to 40 minutes. You might be asked how a client can improve profitability, whether to enter a new market, or why sales are falling. There is rarely a single right answer. The interviewer is testing how you think: whether you can structure an ambiguous problem, work with data and basic math, and communicate a clear, logical recommendation under a little pressure.
Most firms use one of two formats. In an interviewer-led case (the classic McKinsey style), the interviewer steers you question by question. In a candidate-led case (long associated with BCG), you drive the structure and decide where to dig. Bain was historically known for candidate-led cases but has been shifting toward interviewer-led ones, and in practice the format depends heavily on your specific interviewer. Both reward the same underlying skills, so prepare for both.
The skills a case actually tests
- Structure: breaking a messy problem into clear, logical, non-overlapping parts.
- Quantitative ability: doing clean mental math and interpreting charts and data without a calculator.
- Business judgment: knowing which levers actually move the answer.
- Communication: walking the interviewer through your thinking clearly, and ending with a crisp recommendation.
- Poise: staying composed and adaptable when the interviewer pushes back.
Frameworks: useful starting points, not scripts
Frameworks are common ways to break down recurring problem types, such as profitability, market entry, or pricing. They are genuinely useful as a starting point, but the biggest trap in case prep is memorizing frameworks and forcing them onto every case. Interviewers can spot a canned structure instantly, and it signals you are pattern-matching rather than thinking. Learn the common structures, then practice building a tailored structure for the specific problem in front of you.
A simple profitability lens is a good example: profit equals revenue minus costs, so you can break the problem into revenue drivers and cost drivers and then dig into whichever side the data points to. Use that as scaffolding, not a cage.
How to practice efficiently
- Learn the fundamentals first: how cases work, the common problem types, and how to structure cleanly. Casebooks from university consulting clubs are a standard free resource.
- Drill your math separately. Quick, accurate mental math, percentages, and chart reading are worth practicing on their own so they do not slow you down mid-case.
- Do live cases with partners, ideally peers also recruiting or people who have been through it. Most candidates do roughly 30 to 50 practice cases over one to two months, and live reps matter far more than reading.
- Get specific feedback after each case and target your weak spots, whether that is structure, math, or synthesis.
- Practice saying your recommendation out loud, since a strong answer delivered poorly still loses.
Case prep and networking run in parallel, and both are easy to let slip. OfferPath keeps your networking pipeline organized, who you have spoken to and who is due for a follow-up, so you can focus your energy on cases without letting warm relationships go cold. Free to start, up to 50 contacts. See our guide on how to network for consulting for the outreach side.
Try the Free TrackerHow to structure your thinking in the room
- Take a moment up front to structure before you dive in. A short, organized pause beats rushing into the first idea.
- Lay out your approach clearly, then ask for the data you need rather than guessing.
- Narrate your logic so the interviewer can follow you, and check in as you move between branches.
- When you reach an answer, lead with the recommendation, then give the two or three reasons that support it.
Common mistakes to avoid
- Memorizing frameworks and forcing them onto cases that do not fit.
- Diving into calculations before structuring the problem.
- Going silent during math so the interviewer cannot follow your thinking.
- Getting lost in detail and never returning to the client's actual question.
- Ending with scattered observations instead of a clear, confident recommendation.
- Practicing only by reading, instead of doing live, timed cases with feedback.
Frequently asked questions
How many cases should I practice before consulting interviews?
Most successful candidates do roughly 30 to 50 practice cases over one to two months, ideally live with partners rather than alone. Quality and honest feedback matter more than raw volume, so target your weak spots rather than just running up a count.
Are case interview frameworks worth memorizing?
Learn the common frameworks as starting points, but do not memorize and force them onto every case. Interviewers can spot a canned structure, and it signals pattern-matching over thinking. Practice building a tailored structure for the specific problem instead.
What is the difference between interviewer-led and candidate-led cases?
In an interviewer-led case, common at McKinsey, the interviewer drives you through specific questions. In a candidate-led case, long associated with BCG, you set the structure and decide where to dig. Bain was historically candidate-led but has shifted toward interviewer-led, and the format often depends on your specific interviewer. Both test the same core skills, so prepare for both.
Do I still need to network if I am good at cases?
Yes. Networking gets you the interview, and the case gets you the offer. At firms with acceptance rates around or below one percent, a referral that gets your resume a real look is worth the effort, so run networking and case prep in parallel.