★
Typical Case Interview Structure
The 7-step flow every MBB interview follows — internalize this before anything else
Why this matters
Case interviews test how you think, not just what you know. Every firm — McKinsey, BCG, Bain — follows broadly this same structure. Internalizing this flow lets you stay oriented and calm under pressure, and signal to the interviewer that you are a structured, hypothesis-driven problem solver.
1
Case Background
2
Clarifying Questions
3
Structure Framework
4
Starting the Case
5
Solve Quant
6
Answer Qual Q's
7
Deliver Recommendation
Golden Rule
You will not always go through every step, and not always in order. Interviewers may jump to a step, test you on a specific area, or cut the case short. But knowing this map means you always know where you are in the case.
1
Understanding & Synthesising the Case Background
Your first impression — a former Bain interviewer can tell in 2 minutes if you'll pass
Why this is harder than it looks
This step sets the tone for everything that follows. If you mess it up, you're digging a hole you may never climb out of. Get it right, and you're already ahead of 50% of candidates before the real case even begins. The synthesis is your first impression — treat it like one.
The 3 things that separate good from great
- 1Show enthusiasm. Sound like you actually want to be there. "This sounds like an interesting case — I'm excited to dive in." This single sentence costs you nothing and immediately sets a positive tone.
- 2Speak confidently. Cut all filler words — "um," "uh," "like," "you know." Record yourself once in practice and you'll be shocked how often they appear. Filler words signal uncertainty; absence of them signals control.
- 3Be concise. Trim your summary to its core: client identity, key financial facts, and the specific objective. Ruthlessly cut any repetition or fluff. Every word should earn its place.
Candidate comparison — same case, night and day delivery
Candidate A — What NOT to do
"Okay, um, for this case we are working with a company that makes, um, drinks. They're called Lemon Co. and they, you know, make lemonade for people to drink... Revenue, err I mean profits, have gone down, and so we've been hired to help figure out why the profits have like gone down. I forgot — profits have gone down in the wholesale channel. So, am I missing anything?"
❌ Filler words · Disorganised · No confidence · Repeated itself
Candidate B — What to aim for
"This sounds like an interesting case — I'm excited to dive in. To confirm, our client is Lemon Co., a lemonade company that sells through online, retail, and wholesale channels. Profits are down in wholesale and our goal is to identify the cause and how to fix it. Does that sound right to you?"
✓ Enthusiastic · Confident · Concise · Confirms objective
Example case prompt
Interviewer:
Our client is a large manufacturer and retailer of non-alcoholic beverages, such as sodas, juices, sports drinks, and teas. They have annual revenues of roughly $30B and an operating margin of 30%. Our client is looking to grow and is considering entering the beer market in the United States. Should they enter?
Your synthesis checklist
- 1Open with energy. "This is a great case — excited to get into it."
- 2State the client clearly. Who they are, what they do, key scale metrics (revenue, margins if given).
- 3State the objective cleanly. One sentence, no hedging. "Our goal is to determine whether they should enter the US beer market."
- 4Confirm with the interviewer. "Does that capture everything correctly?" This prevents wasted effort on a misunderstood prompt.
ROI insight from Taylor Warfield (ex-Bain)
You don't need to be a genius to do this well. With just 30 minutes of deliberate practice on this single step, you can make one of the highest ROI improvements in your entire case prep. It's the cheapest upgrade available — nail your first impression every single time.
2
Asking Clarifying Questions
You don't get points for asking — only ask what you truly need
The honest truth
50% of candidates overthink this step. They ask too many questions or try to impress with complex ones. This wastes time and signals poor prioritisation. Your goal is not to impress — it's to clarify the one or two things you genuinely need to build a solid framework. Nothing more.
The one question you should ask in every single case
"Do we have a specific, measurable target for [goal]?"
Example: If the company's profits are down, ask:
"Do we know how much profit the company is aiming to regain, and by when?"
"Do we know how much profit the company is aiming to regain, and by when?"
It gives you
A clear, measurable goal to anchor your recommendation
It signals
Quantitative thinking — you already want a number, not just a direction
It sets up
A stronger, specific final recommendation tied to a real target
The 4 types of clarifying questions (when more are needed)
- 1Definition clarification. Ask for the definition of a term you are genuinely unfamiliar with. Example: "When you say 'enter the beer market' — does that include craft, premium, and mass-market segments?"
- 2Company/situation understanding. Ask for information that strengthens your model of the business. Example: "Does the client have existing distribution infrastructure for alcoholic beverages, or would this be entirely new?"
- 3Objective clarification. Clarify what success looks like — ideally with a number and a timeline. Example: "Is the primary objective profitability within a specific time horizon, or market share growth?"
- 4Missed information. Politely ask to repeat something you did not catch. Use this sparingly — once at most.
The top 25% rule
If you nail the case summary (Step 1) and ask focused, purposeful clarifying questions (Step 2), you're already in the top 25% of candidates within the first 5 minutes of the case. These two steps cost you zero analytical ability — they're entirely about discipline and preparation.
3
Structuring a Framework
The step 80% of candidates get wrong — here's how to be in the other 20%
Two traps to avoid — both are obvious to interviewers
Bad Strategy 1 — Memorising 30 frameworks
Cramming 10–30 frameworks hoping one fits. Interviewers see through this immediately — you'll sound scripted, not sharp. This is the "Case in Point" trap.
Bad Strategy 2 — Same framework every case
The one-size-fits-all approach. It's lazy and generic. If interviewers compare notes and realise you used the same structure in every case, that's a serious red flag.
The right approach — two strategies depending on your level
Beginner Strategy — Build from common elements (gets you B+)
Memorise 10–12 common framework elements. When you receive a case, run through this list mentally and pick the 4 most relevant. Fast, reliable, and solid.
Market
Competition
Customer
Company
Product
Profitability
Synergies
Risks
Alternatives
Supply Chain
Stakeholders
Financials
Advanced Strategy — Reverse-engineer the recommendation (gets you A+)
Ask yourself: "What 4 things need to be true for me to confidently say YES to the recommendation?" These become your buckets.
Example: Lemonade Co. is considering acquiring Sparkle Co. Should they?
1. The sparkling water market is attractive
2. Sparkle Co. itself is performing well
3. There are meaningful synergies to leverage
4. The acquisition financials are attractive
2. Sparkle Co. itself is performing well
3. There are meaningful synergies to leverage
4. The acquisition financials are attractive
Example framework — beer market entry case
① Market Attractiveness
- What is the total market size?
- What is the market growth rate?
- What are average profit margins?
② Competitive Landscape
- How many competitors are there?
- How much market share do they hold?
- What are their competitive advantages?
③ Our Capabilities
- Are there significant capability gaps?
- Do we have synergies to leverage?
- What needs to be built vs. acquired?
④ Profitability
- What are expected revenues and costs?
- How long to break even?
- What is the risk-adjusted return?
Bonus: MECE two-bucket pairs — guaranteed 100% MECE
The X / Not-X principle
A two-bucket framework of the form "X / Not X" is always perfectly MECE by construction. Combine two pairs to create an instant guaranteed-MECE 4-bucket framework. Example: Short-term benefits / Long-term benefits / Short-term costs / Long-term costs.
Internal / External
Company-side vs market-side
Direct / Indirect
Primary vs secondary effects
Short-term / Long-term
Immediate vs structural impacts
Supply-side / Demand-side
Production vs customer factors
Economic / Non-economic
Financial vs strategic/reputational
Upside / Downside
Benefits vs risks
Quantitative / Qualitative
Measurable vs intangible
Benefits / Costs
Value created vs resources consumed
Domestic / International
Local vs global scope
Financial / Non-financial
P&L vs strategic factors
Primary / Secondary
Core vs supporting factors
Existing / New
Current state vs potential state
The 8 universal framework buckets — always available as a fallback
Market Attractiveness
Profitability / Financials
Competitive Landscape
Strategic Alternatives
Company Capabilities
Risks & Mitigations
Customer Segments / Needs
Create Your Own
Critical principles
MECE: No overlaps, no gaps. 3–4 buckets max. Tailor every time — the reverse-engineering method is your best tool. Lead with the most important bucket — structure implies priority.
4
Starting the Case
Drive the analysis — don't wait to be led
- 1State where you are starting and why. "I'd like to begin with market attractiveness, as this is the threshold question — if the market isn't attractive, the other buckets become less relevant."
- 2Form a hypothesis early. Good consultants don't just explore — they hypothesize. "My working hypothesis is that the US beer market is attractive given its scale, though margin pressure from incumbents may be significant."
- 3Ask for data to validate or invalidate your hypothesis. "What information do we have on total US beer market revenues and growth rates?"
- 4Synthesise as you go. After each data point, say what it means: "The market growing at 3% annually suggests moderate but stable demand — this supports entry from a macro standpoint."
What "driving the case" means
The interviewer should feel like a client being guided by a confident consultant — not a teacher pulling answers out of a student. You ask what data you need. You say what it means. You state your evolving view. You propose what to explore next. You are always ahead of the analysis, not behind it.
5
Solving Quantitative Problems
Three types — each has a repeatable approach
Market Sizing Questions
Estimate total market value or volume from first principles using segmentation and reasonable assumptions
Profit Questions
Diagnose or calculate profitability using revenue and cost structures, margin analysis, and breakeven logic
Charts & Graphs Questions
Read, interpret, and draw insight from charts — identify trends, anomalies, and the business implication
Market sizing — step-by-step approach (beer market example)
- 1Start with population. US population ≈ 330 million people.
- 2Filter to legal drinking age. ~78% aged 21+. 330M × 0.78 ≈ 257 million legal-age adults.
- 3Estimate beer drinkers. ~50% of legal-age adults. 257M × 0.50 ≈ 128 million beer drinkers.
- 4Estimate frequency. ~2× per week ≈ 104 occasions per year.
- 5Estimate spend per occasion. ~$1.50 retail. 128M × 104 × $1.50 ≈ $20 billion total market.
Market sizing principles
State assumptions aloud. Show your logic. Round aggressively. Then sanity-check: "Does $20B feel right for the US beer market?" The interviewer is evaluating your logic, not just your arithmetic.
Core profit formulas — memorise these
Basic Profit Identity
Profit = Revenue − Costs
Revenue Decomposition
Revenue = Price × Volume (Units Sold)
Cost Decomposition
Costs = Fixed Costs + Variable Costs
Profit Margin
Profit Margin = (Revenue − Costs) / Revenue
Breakeven Point
Breakeven: Profit = $0 → Revenue = Costs
Breakeven Units
Breakeven Units = Fixed Costs / (Price − Variable Cost per Unit)
When diagnosing a profit problem
Always start top-down: Revenue side or cost side? If revenue: price or volume? If cost: fixed or variable? Narrow down systematically before jumping to solutions.
6
Answering Qualitative Questions
Use binary structuring pairs — they prevent rambling and reveal sharp thinking
The core technique
Qualitative questions can feel open-ended and scary. Structure your answer using one of the binary pairs below — they create instant MECE structure without needing a pre-built framework. Always name the dimension before you start listing points.
Internal / External
Company-side vs market-side
Direct / Indirect
Primary vs secondary effects
Short-term / Long-term
Immediate vs structural impacts
Supply-side / Demand-side
Production vs customer factors
Economic / Non-economic
Financial vs strategic/reputational
Upside / Downside
Benefits vs risks
Quantitative / Qualitative
Measurable vs intangible
Benefits / Costs
Value created vs resources consumed
Applied example — beer market entry
Q: "What risks should our client consider when entering the beer market?"
A: "I'd organise the risks into internal and external categories. Internally, the client faces execution risk — they have no experience producing or distributing alcoholic beverages, which means significant capability gaps and upfront capex. They also risk brand dilution if a failed beer entry damages their existing beverage brand equity. Externally, the US beer market is highly consolidated — AB InBev and Molson Coors control over 60% of volume — so competitive retaliation could be severe. There is also regulatory risk: US alcohol distribution is heavily state-regulated under the three-tier system, adding complexity."
Delivery principle
Always lead with "I'd structure my answer as X and Y" before you start listing points. This signals structure before content — exactly what MBB interviewers are testing for.
7
Delivering a Recommendation
Be direct, be confident, and show you've earned your view
The principle
Your recommendation must be clear, definitive, and supported by exactly three reasons. Then offer two next steps to show you are already thinking ahead.
Recommendation template — memorise this structure
"I recommend that INSERT RECOMMENDATION for the following three reasons:"
One... [most important reason, with evidence]
Two... [second reason, with evidence]
Three... [third reason, with evidence]
"For next steps, I would like to look into the following two areas:"
One... [framework bucket not yet fully explored]
Two... [open question or risk to investigate]
What to put in next steps
Applied example — beer market entry
"Based on our analysis, I recommend that our client enter the US beer market, but through acquisition rather than organic entry, for the following three reasons:"
One: The US beer market at roughly $100 billion in retail value represents a significant growth opportunity, and the client's existing beverage distribution network provides a structural cost advantage.
Two: Organic entry faces insurmountable barriers — the three-tier distribution system, state-by-state licensing, and entrenched competition from AB InBev and Molson Coors. Acquisition bypasses these and provides an existing brand.
Three: A well-chosen acquisition target with EBITDA margins of 15–20% could achieve breakeven within 3–4 years given distribution synergies.
"For next steps: One, map mid-sized UK and European breweries trading at attractive multiples; and Two, quantify distribution synergies to build the full DCF business case."
Never hedge without data
Saying "it depends" without immediately specifying what it depends on is a red flag. Say: "My recommendation is X, conditional on [specific condition] — if that condition does not hold, I would instead recommend Y."
★
Quick Reference — 10 Non-Negotiable Principles
Read this before every mock case. Internalize, don't just memorize.
Structured Thinking Standards
1Synthesise the case with enthusiasm, no filler words, and one clean sentence per key fact. A Bain interviewer can tell in 2 minutes if you'll pass.
2One clarifying question: "Do we have a specific, measurable target for [goal]?" You get zero points for more.
3Build frameworks by reverse-engineering: "What 4 things need to be true to confidently say yes?" = A+ framework.
4Every framework must be MECE. Use X / Not-X pairs as a guaranteed shortcut when stuck.
5Always signal structure before content: "I'll approach this through two lenses: X and Y."
6Hypothesize before you analyze. Drive the case — don't wait to be led.
7Synthesise data, don't just repeat it. "3% growth annually supports the entry hypothesis."
8For quant: state assumptions aloud → show logic → round → sanity-check. Logic matters more than arithmetic.
9Recommendation = 3 evidence-backed reasons + 2 concrete next steps. Be direct.
10Never say "it depends" without specifying what it depends on and why it changes your answer.