IntervYou logoIntervYou
consultingcase-studyframeworks

How to Prepare for a Consulting Case Interview at MBB

Case interviews at McKinsey, BCG, and Bain test structured reasoning under pressure, not framework memorization. Here's a real prep plan with worked examples.

IIntervYou
··9 min read

The dirty secret about MBB case interviews is that most candidates study the wrong thing. They memorize frameworks, practice frameworks, and walk into the room ready to recite frameworks. Then they get a case about a European airline's fuel-hedging strategy and freeze because no framework they memorized covers it cleanly.

Case interviews aren't a test of whether you know frameworks. They're a test of whether you can structure ambiguous problems under pressure while making the interviewer feel like the conversation is worth their time.

What Is the Case Interview, and Why Does Structure Matter?

A case interview is a live problem-solving exercise where a candidate talks through a business situation with an interviewer, typically lasting 20–40 minutes. The problem is intentionally underspecified. McKinsey, BCG, and Bain use it as their primary hiring filter because it surfaces, faster than any other format, whether someone can hold a structured conversation about an unstructured problem.

How to prepare for a consulting case interview at MBB firms: Start with four core frameworks — issue tree, profitability, 4Ps, and Porter's Five Forces. Internalize the logic behind each, not just the labels. Weeks 1–2 are for framework study; weeks 3–4 for live practice at volume (2–3 cases per week); weeks 5–6 for timed full mocks with no notes. The most important practice is live practice with a partner who gives real feedback — not solo drills with a timer. According to a 2023 analysis by Management Consulted, candidates who completed 30+ live cases before their MBB interview had a pass rate roughly double those who completed fewer than 15, regardless of GPA. The hardest skill to build is synthesizing a clear recommendation under real pressure. Practice closing every mock case with a one-position statement before you walk into the room.

The structure isn't there to constrain your thinking — it's there to make your thinking legible to someone else while you're still forming it.

According to McKinsey's publicly available career site, candidates who pass first-round case interviews advance to offer at a rate suggesting roughly 1 in 10 applicants makes it past initial screening. The numbers vary by office and year, but the filter is consistently aggressive.

What Are the Main Frameworks Used in Case Interviews?

The four structures every serious candidate internalizes before the case room:

Issue tree. Break a problem into mutually exclusive, collectively exhaustive (MECE) buckets. This is the default starting point for most cases.

Profitability framework. Revenue minus cost. Simple, but most candidates apply it too literally — they list all revenue drivers and all cost drivers rather than isolating the one that changed.

4Ps (marketing). Product, price, place, promotion. Useful for market-entry and brand cases, often poorly applied to situations it doesn't fit.

Porter's Five Forces. Used primarily for industry attractiveness cases, though BCG interviewers will sometimes penalize you for reaching for it when a simpler structure would work.

The real test isn't whether you know these frameworks — it's whether you can adapt them when the case doesn't fit the template.

A candidate at Bain described being given a case where the "company" was a fictional hospital network. She tried applying a standard profitability tree and the interviewer cut her off after 90 seconds to ask her to think about the problem differently. She pivoted to a patient-flow analysis. She got the offer.

Three Worked Examples: How the Framework Actually Runs

Example 1 — Retail profitability (operations domain)

Interviewer: "Our client is a European shoe retailer. Profits fell 15% last year despite flat revenue. Where do you start?"

Candidate: "Flat revenue with falling profit means the cost structure changed. I'd split costs into fixed and variable. Fixed costs — rent, staff — are harder to cut quickly. Variable costs — COGS, shipping — are the first place to look for a sudden change. Can you tell me if the product mix shifted at all last year?"

Interviewer: "Yes — they added a premium line."

Candidate: "That changes things. Premium products often carry higher COGS as a percentage of revenue. I'd want gross margin by product line to confirm whether the premium line is dragging down the blended margin, or whether we have a separate cost problem elsewhere."

The candidate didn't recite the profitability framework. They used the logic of the framework to drive a specific, testable question.

Example 2 — Market entry (strategy domain)

Interviewer: "A logistics firm in Saudi Arabia wants to enter the same-day delivery market. Should they?"

Candidate: "Market entry needs two questions answered: is the market attractive, and can this company win in it? Let me take them separately. For attractiveness — what's the current same-day delivery market size in the Kingdom, and what's the growth rate?"

Interviewer: "Market is around 2 billion SAR, growing at 18% annually."

Candidate: "That's compelling on its own, but growth is meaningless if margins are thin. Same-day delivery in competitive markets often runs on 3–5% EBITDA. If that holds here, the investment case becomes capital-intensive and unattractive unless this company has a structural cost advantage — which brings me to the second question: what assets does this company already have?"

Example 3 — Organizational change (HR domain)

Interviewer: "A major consulting firm's internal operations team has 40% annual attrition. How do you approach diagnosing this?"

Candidate: "Before I assume this is a pay or culture problem, I'd want to know whether 40% is unusual for this type of role, and whether it's above peer firms. Attrition always looks alarming in isolation. If the benchmark is 35%, this is a real problem. If the benchmark is 50%, you might actually be outperforming."

Interviewer: "Let's assume it's a problem. What are the drivers?"

Candidate: "I'd structure this as push versus pull factors. Push factors — things that make people leave, like poor management or unclear advancement paths. Pull factors — external opportunities drawing them away. Which side does the exit interview data point to?"

What Are the Most Common Mistakes Candidates Make?

Jumping to the solution. The most frequent failure at McKinsey first-round cases is a candidate who hears the prompt and immediately proposes an answer. The interviewer wants to watch you think, not hear your conclusion. Slow down. Acknowledge the problem. Ask one clarifying question. Then structure.

Using frameworks as a script. Saying "I'll use the profitability framework" and then listing every revenue and cost driver on the page is not analysis — it's a template. BCG interviewers have been direct about wanting "hypotheses, not headings." Structure your analysis around a hypothesis about what's causing the problem, not a blank taxonomy.

Ignoring interviewer signals. When an interviewer says "interesting, but let's focus on the cost side," that's a redirect. Candidates who plow ahead with their own structure are signaling exactly the behavior that makes a bad consultant: prioritizing your own plan over what the client wants.

Not sizing your analysis. "If revenue is $500M and gross margin dropped 2%, that's $10M — meaningful." A candidate who identifies the right issue but can't quantify it leaves the interviewer with nothing to prioritize.

Practicing too much alone. You can't develop case skills by reading books or drilling solo. The real skill is built through live cases with a partner who gives real-time feedback. IntervYou's mock case interviews simulate the interviewer-candidate dynamic that solo practice simply can't replicate.

The core mistake across all of these: treating case prep as memorization when it's actually motor-skill development.

How Does Case Interview Prep Compare to Other Interview Types?

Dimension Case Interview Behavioral Interview Technical Interview
Primary skill tested Structured reasoning Communication + self-awareness Domain knowledge
Preparation format Live practice, frameworks Story bank, STAR method Coding / domain drills
Time pressure High (real-time synthesis) Moderate (narrative recall) High (algorithmic)
Spontaneity required High Low-medium Moderate
Feedback loop Immediate (interviewer cues) Delayed (post-interview) Immediate (test output)
Transferable to real work High (consulting is cases) Moderate High (for technical roles)

Case prep is the most expensive in time per quality point gained — because you're building a cognitive reflex, not memorizing facts.

Case prep takes more deliberate practice per quality point than either of the others. The skill you're building — structured real-time reasoning — doesn't transfer from reading. It requires reps with feedback.

What Does a Good 6-Week Prep Schedule Look Like?

Weeks 1–2: Foundation. Read one case book cover to cover. Victor Cheng's Case Interview Secrets is the clearest on framework logic. Internalize why each structure exists — don't just memorize it. Do no live cases yet.

Weeks 3–4: Live practice, high volume. Two to three live cases per week. Use BCG's published case library and McKinsey's case interview app. After each case, spend 15 minutes reviewing where your structure broke down and where you responded well to redirects.

Weeks 5–6: Full simulation. Timed, full-mock sessions with no notes. One case per day where possible. Focus on the hardest transitions: structuring the initial problem cleanly in under three minutes, and synthesizing a final recommendation in under two.

A 2023 analysis by Management Consulted found candidates who completed 30+ live cases before their MBB interview passed first-round at roughly double the rate of those who completed fewer than 15 — regardless of GPA or undergraduate school.

Volume matters, but only if the practice is structured and the feedback is real.

IntervYou's AI-driven mock case platform gives you the feedback loop you can't build alone: a simulated interviewer that responds to your structure, flags when you're scripting rather than thinking, and scores your synthesis quality at the end of each session.

How Do You Close a Case Well?

The final two minutes of a case interview carry disproportionate weight. This is where candidates lose offers they earned in the first 25 minutes.

A good close is a recommendation with a rationale, not a summary of your work. "Based on the analysis, I'd recommend the client exits the premium product line. The gross margin data shows it's contributing less than 8% of profit on 22% of SKUs — a resource drain. The key risk is customer perception, which would need a careful communication plan." Three sentences: a position, a number, and a risk acknowledgment.

Most candidates close by recapping what they analyzed. That's not a recommendation — it's a travelogue. Practice ending every mock case with a one-position statement before you get to the room.

The interviewers aren't grading your analysis — they're deciding whether they'd trust you in front of a client.

The fundamentals don't change between McKinsey, BCG, and Bain — but the cultural register does. McKinsey pushes harder on logical rigor. BCG rewards creative hypotheses that get disproven gracefully. Bain cares most about whether the candidate is enjoyable to work with, which shows up in how well they manage the conversational back-and-forth. Same underlying skills, different emphasis.

Start a free mock →


Share this post

Related guides

Ready to practice?

Stop reading about interviews and start acing them. Get a realistic AI mock interview tailored to your target role — completely free.

Or explore plans & pricing

Get weekly MENA interview tips

Actionable strategies for landing roles at top companies across the Middle East.