Part 1
Behavioral Questions
Behavioral questions are used in virtually every interview — consulting, banking, tech, PE, corporate strategy. They ask you to describe specific past experiences to predict how you'll perform in the future.
What they are
The premise is simple: past behavior predicts future behavior. An interviewer asking "tell me about a time you led a team through a difficult situation" isn't looking for a hypothetical answer. They want a real story with real stakes, real actions you took, and a real outcome.
Behavioral questions typically start with phrases like "Tell me about a time…", "Describe a situation where…", or "Give me an example of…" McKinsey calls their version the Personal Experience Interview (PEI), same concept, but they'll drill one story for 20–30 minutes rather than collecting several shorter ones.
Common question types
Leadership
"Tell me about a time you led a team through ambiguity or change."
Conflict
"Describe a situation where you disagreed with a colleague or manager. How did you handle it?"
Failure
"Tell me about a time you failed or made a significant mistake. What did you learn?"
Influence
"Give me an example of a time you influenced someone who didn't report to you."
Achievement
"What's the accomplishment you're most proud of? Walk me through it."
Initiative
"Tell me about a time you identified a problem no one else had noticed and took action."
The STAR framework
Most candidates use STAR — Situation, Task, Action, Result — to structure their answers. It works well when applied correctly. The most common mistake is spending too much time on Situation and not enough on Action.
Set the scene briefly. What was the context? What was at stake? Don't over-explain — the interviewer needs just enough to understand why the situation was hard.
What was your specific role or responsibility? What were you personally accountable for? This is where you clarify that the story is about you, not the team.
What did you specifically do? What choices did you make? What was hard about it? This is what interviewers actually want to hear. Be specific about your individual contribution — not "we decided" but "I recommended X because Y."
What happened? Quantify if possible — numbers, percentages, timelines, business impact. Then briefly reflect: what did you learn, or what would you do differently?
What interviewers are evaluating
Personal impact. Did you actually drive the outcome, or were you a bystander in your own story? Interviewers are listening for "I" not "we."
Judgment under pressure. When the situation was hard and you didn't have all the answers, how did you think through it? What tradeoffs did you make?
Self-awareness. Can you assess your own performance honestly, including what went wrong? Generic success stories are less compelling than stories with real tension and reflection.
Communication clarity. Is the story easy to follow? Do you get to the point? At consulting and banking firms especially, how you tell the story signals how you'll communicate with clients.
Fit signals. Does the story reveal the traits the firm values? McKinsey looks for leadership through ambiguity. Bain looks for results-orientation and collaborative instinct. Tech firms often look for ownership and first-principles thinking.
✦ Preparation tips
- Build a story bank of 6–8 experiences that can flex across question types. A good leadership story can also answer conflict and initiative questions with different emphasis.
- Practice going deeper, not just telling the story. Interviewers will ask follow-up questions — "Why did you make that choice?" "What pushback did you get?" Know your stories three levels deep.
- Prepare a specific "why this firm" answer for every firm you're interviewing with. Vague answers ("the culture," "the learning") are a red flag. Know the firm's practice areas, recent work, or alumni you've spoken to.
- Time yourself. A good behavioral answer is 90–120 seconds. Most candidates run long on Situation and short on Action — the opposite of what interviewers want.
Part 2
Case Interviews
A case interview is a business problem-solving exercise conducted in real time with the interviewer. You're given a scenario — a company facing a problem — and asked to analyze it, ask questions, structure your thinking, and arrive at a recommendation.
What they are
Cases are used primarily in consulting (MBB, Big 4 strategy, boutiques) and increasingly in PE, IB, and corporate strategy roles. They're designed to simulate the work you'd actually do — taking ambiguous business problems, structuring them into solvable pieces, analyzing data, and communicating a clear recommendation.
Unlike behavioral questions, there is rarely a single "correct" answer. Interviewers are evaluating your process as much as your conclusion. A candidate who reaches the wrong answer with clear, structured thinking often scores higher than one who guesses the right answer and can't explain why.
Common case types
📉
Profitability
A company's profits are declining. Diagnose why and recommend how to fix it. Tests your ability to break down Revenue and Cost drivers.
🌍
Market Entry
Should a company enter a new market or geography? Covers market sizing, competitive dynamics, and entry strategy.
🔢
Market Sizing
"How many X are there in the US?" Tests structured estimation, logical segmentation, and comfort with approximate math under pressure.
🤝
M&A / Due Diligence
Should a company acquire a target? Covers strategic fit, synergies, valuation logic, and integration risk.
🚀
Growth Strategy
How should a company grow revenue or market share? Often involves evaluating organic vs. inorganic options and prioritizing initiatives.
⚙️
Operations / Cost
How can a company reduce costs or improve operational efficiency? Common in PE and manufacturing-adjacent cases.
What interviewers are evaluating
Structured thinking. Can you break a big, ambiguous problem into a clear, logical structure? Do your buckets make sense and cover the problem space?
Hypothesis-driven approach. Top performers form an initial hypothesis early and update it as they learn more. Interviewers want to see you driving toward a view, not collecting data until an answer appears.
Quantitative comfort. You don't need to be a mathematician, but you need to move through numbers quickly and accurately. Mental math errors under pressure are a signal interviewers notice.
Communication. Are you thinking out loud in a way that's easy to follow? Do you pause to synthesize what you've found before moving on? Can you give a clean recommendation at the end?
Business intuition. Do your conclusions make common sense? Does your recommendation account for real-world constraints? Technically correct analysis paired with a nonsensical recommendation is still a miss.
Composure and coachability. When the interviewer redirects you or offers new information, do you adapt gracefully? Defensiveness or rigidity is a red flag.
How to approach a case
This is the sequence most strong candidates follow. The exact steps vary by firm style (see the next section), but the underlying approach is consistent.
| Step |
What to do |
| 1. Clarify the objective |
Before diving in, confirm what "success" looks like. What exactly is the company trying to achieve? What are the constraints? Take 30 seconds to ask one or two focused questions. |
| 2. Take a moment to structure |
Ask for 60 seconds to think. Use it. Jot down a framework — not a memorized one, but a logical structure tailored to this specific problem. Tell the interviewer what you're going to analyze and why. |
| 3. State your initial hypothesis |
Before analyzing anything, say what you think is most likely going on. "My hypothesis is that the profitability decline is driven by cost inflation, not revenue loss — here's why." Then test it. |
| 4. Drive the analysis |
Ask for specific data. Show your math out loud. When you learn something new, update your hypothesis explicitly: "This changes my view on X because…" |
| 5. Synthesize as you go |
Don't just pile up facts. Pause at key moments to summarize what you've found and what it means. Interviewers notice candidates who can synthesize, not just analyze. |
| 6. Give a clean recommendation |
Structure your closing as: recommendation → top 2-3 supporting reasons → key risk or caveat. Be direct. A confident "I recommend X because Y and Z, with the main risk being W" beats a hedged non-answer every time. |
What a framework looks like in practice
When you ask for 60 seconds to structure, this is what you're building — and what you say when you present it back.
Example — Profitability case
Case prompt
Our client is a mid-size specialty retailer. Profits have declined ~20% over the last two years. The CEO wants to know why and what to do about it.
① Revenue
Volume: units sold
Price: avg. selling price
Mix: product / channel
New vs. existing customers
② Costs
COGS: materials, labor
Fixed overhead: rent, staff
Variable costs: logistics
One-time vs. recurring?
→ Hypothesis: cost inflation likely given macro environment — will test revenue first to rule out
1
Name your buckets before you go in. Say the structure out loud before diving into either branch. Interviewers need to follow your logic — don't make them guess what you're organizing around.
"I'd like to approach this through two lenses — Revenue and Costs. I'll start on the revenue side to understand if this is a volume, price, or mix issue, then move to costs."
2
State your hypothesis upfront. Before you've seen any data, say what you think is most likely. It shows business intuition and keeps you from drifting.
"My initial hypothesis is that this is cost-driven given the inflationary environment over the last two years — but I want to check revenue first to rule it out."
3
Prioritize before you analyze. Don't walk through every sub-bucket mechanically. Tell the interviewer which branch you're going to explore first and why.
"I'll start with revenue — specifically volume — because a 20% profit decline is steep enough that I want to understand whether we're selling fewer units before assuming it's a cost story."
Real interviews often give you no numbers at all. That's intentional. When a prompt says "a retailer's profits have declined" with no figures, you're expected to estimate the numbers yourself using structured logic — not wait for them to be provided.
This is called assumption-setting, and it's a core case skill. A strong candidate might say: "If I assume this is a $500M revenue business with ~15% margins ($75M of profit), a 20% profit decline would represent roughly $15M of lost profit — let me figure out where that's coming from." That baseline makes all your subsequent analysis concrete and testable.
The goal isn't accuracy — it's defensible logic. Interviewers don't expect you to know industry margins. They want to see you reach a reasonable estimate through clear steps, then hold it lightly as you gather more data. Estimating confidently is a green flag. Refusing to guess without data is a red one.
→ Practice estimation in the Case Library
✦ Preparation tips
- Practice cases out loud with a partner, not just in your head. The verbal communication piece is a separate skill from the analysis and it requires reps.
- Don't memorize frameworks. Learn the logic behind them so you can build a structure that fits the specific case in front of you. Interviewers can tell when someone is reciting a framework vs. actually thinking.
- Drill your mental math separately. Practicing 30 minutes of estimation problems before case prep begins pays off disproportionately.
- Record yourself. Most candidates don't realize how many filler words they use, how long their pauses are, or how unclear their synthesis sounds until they hear it back.
Part 3
Candidate-Led vs. Interviewer-Led Cases
Not all case interviews work the same way. The two main formats reward different skills, and candidates who've only practiced one often struggle with the other.
Candidate-led (McKinsey, BCG*)
You drive the case. After the interviewer presents the problem, you decide what to analyze, what questions to ask, and in what order. You're expected to build the structure, request the data you need, and navigate the problem with minimal direction.
This format rewards proactive thinking and comfort with ambiguity. You won't be told if you're on the right track. You have to trust your structure and update as you learn more.
* BCG varies by office. Some BCG offices run interviewer-led formats. Confirm the style with your recruiter or recent interviewees before assuming candidate-led.
Interviewer-led (Bain, some boutiques)
The interviewer guides you through the case with a series of targeted questions — "Let's look at the revenue side. What do you think is driving the decline?" You're responding to prompts rather than steering the analysis.
This format tests precision and directness. You're not expected to build the full structure upfront, but your answers to each prompt need to be crisp and well-reasoned. Candidates who're used to candidate-led cases sometimes feel like they're being "interrogated." That's normal. The format is just different, not harder.
Written cases (BCG Online Case, some Bain offices)
Some firms use a written or digital case exercise as a screening tool before live interviews. You're given data — charts, tables, written materials — and asked to answer questions or prepare a short recommendation. BCG's Online Case is an interactive simulation used in some European offices (format and duration vary by cycle). Bain's written case is a document analysis exercise used in select offices (typically 30 minutes, but confirm with your recruiter).
The skills tested are the same as a live case, but the format is different. Speed, prioritization, and the ability to pull key insights from dense materials matter more in written formats than they do in a conversation.
| Format |
Who uses it |
What it rewards |
| Candidate-led |
McKinsey, BCG |
Structure-building, hypothesis-first thinking, ambiguity tolerance |
| Interviewer-led |
Bain, some boutiques |
Directness, precision, responsiveness under questioning |
| Written / digital |
BCG (some offices), Bain (some offices)* |
Speed, data synthesis, written communication |
* Format varies by office and recruiting cycle. Confirm directly with your recruiter before assuming a written case applies to your process.
What's Next
Where to Practice
Reading about interviews only gets you so far. The gap between knowing the framework and performing it under pressure closes with practice.
Behavioral Practice
Behavioral Question Bank
200+ behavioral questions organized by theme. Elite users can submit their answer (STAR or CAR format) and get it scored against a rubric.
Go to Behavioral →
Case Practice
Case Interview Library
100+ structured cases across 12 industries and 3 difficulty levels, with an AI coach to give feedback on your approach.
Go to Case Library →
Firm Research
Firm Intel
36 firm profiles covering interview style, what they're really evaluating, standout questions to prepare, and insider tips.
Go to Firm Intel →
Application Materials
Resume Tailor
AI-powered resume rewriting. Paste your resume and a job description — CaseEdge rewrites your bullets to match the role.
Go to Resume Tailor →