To prepare for a case interview, learn the basic conversation flow, practise solving unfamiliar business problems aloud, drill mental maths and chart reading, and review every attempt with a clear scorecard. Start with official cases from the employer, not a pile of memorised frameworks. Your goal is to show structured thinking, sound judgement, accurate analysis, and clear communication while responding to new information.
Case interviews can feel artificial at first. An interviewer gives you an incomplete business problem, waits while you organise it, and then tests how you work through questions, numbers, exhibits, and trade-offs. The discomfort is part of the exercise. You are not expected to know everything. You are expected to make progress without hiding your reasoning.
This guide gives you a repeatable preparation method that works whether you have several weeks or only a few days.
Understand what a case interview is testing
A case interview is a structured discussion about a business problem. You might be asked why a company's profit is falling, whether it should enter a new market, how it could increase capacity, or whether an investment makes sense.
The case is usually not a trivia test. Bain's official guide describes it as a conversation in which the interviewer watches how you think, structure the problem, and build on ideas, rather than looking for one single correct answer. You can see that definition and Bain's practice material on its case interview preparation page.
Employers vary, so do not assume every case follows the same script. Read your invitation and the firm's careers page. Ask the recruiter whether you should expect a live case, written case, group exercise, online assessment, or presentation.
Across formats, interviewers commonly observe whether you can:
- clarify an ambiguous objective;
- divide a large problem into useful parts;
- choose which analysis matters first;
- work accurately with numbers and exhibits;
- connect calculations to business meaning;
- listen and adapt when new information arrives;
- explain a recommendation with risks and next steps.
BCG's official guidance tells candidates to structure their approach, ask thoughtful questions, analyse data, perform quick calculations, and identify the most important factors. It also stresses listening, clarifying assumptions, and showing your thinking. That is a better preparation brief than trying to memorise fifty industry frameworks. Read BCG's current case interview guidance before practising.
Learn the case conversation flow
Most live cases contain the same broad moves, even when the order changes.
1. Clarify the objective
Listen to the prompt, take brief notes, and restate the goal in your own words. Confirm the decision, metric, time period, and constraints.
Suppose the prompt is: "A regional coffee chain has seen profit fall. What should it do?"
Useful questions include:
- Is the objective to restore profit to a previous level or maximise future profit?
- Over what period did profit decline?
- Is the problem across the chain or concentrated in certain locations?
- Has revenue, cost, or both changed?
- Are there limits on investment, closures, or pricing changes?
Do not interrogate the interviewer for every fact. Ask only what changes how you define or structure the problem.
2. Build a tailored structure
Ask for a short moment to organise your thoughts. Create a small set of distinct branches that cover the likely causes or decisions.
For the coffee-chain problem, you could examine:
- Revenue: customer traffic, items per order, price, and product mix.
- Variable costs: ingredients, packaging, delivery fees, and hourly labour.
- Fixed costs: rent, salaried labour, technology, and overhead.
- Context: competitor moves, customer preferences, operational constraints, and location differences.
This is not impressive because it resembles a formula. It is useful because each branch can produce a decision. Explain why you chose it and say where you would begin.
3. Form a hypothesis and prioritise
A hypothesis is a starting view, not a conclusion you must defend forever. For example:
"I would first compare profit by location and separate the change into revenue and cost. My initial hypothesis is that the decline is concentrated in a subset of stores, because that would point to a local traffic or operating-cost problem rather than a chain-wide pricing issue."
That statement creates a sensible next analysis. If the data disproves it, update your view plainly. Refusing to change direction is not conviction. It is bad analysis wearing a suit.
4. Analyse data and narrate the meaning
When you receive a chart or table, pause before calculating. State what it shows, inspect the labels and units, note the relevant comparison, then do the maths.
Use this sequence:
- Describe the exhibit in one sentence.
- Identify the observation that matters to the objective.
- Perform the required calculation.
- Check the units and whether the result is plausible.
- Explain the business implication.
For example, imagine one store serves 400 orders per day at an average order value of $8. A proposed menu change is expected to add $0.75 per order, with no change in order volume.
Incremental daily revenue is:
`400 orders x $0.75 = $300 per day`
If the store opens 360 days per year, incremental annual revenue is:
`$300 x 360 = $108,000 per year`
Do not stop at the number. Say: "This creates up to $108,000 in annual revenue before considering ingredient cost, implementation cost, or any effect on demand. I would next estimate contribution margin and test whether customers accept the change."
The interpretation is where a calculation becomes a decision.
5. Synthesize as you go
After each section, give a short update:
"So far, the decline appears concentrated in urban stores. Traffic is stable, but ingredient cost per order increased. I would next test which products caused the increase and whether pricing or menu design can recover margin without damaging demand."
These checkpoints keep the interviewer oriented and prove that you can distinguish a finding from a pile of facts.
6. Recommend with evidence and caveats
Finish with the answer, then the reasons, risks, and next step.
A clean final recommendation sounds like this:
"I recommend piloting the menu change in the urban stores. Those locations account for most of the profit decline, customer traffic is stable, and our estimate suggests meaningful revenue upside. The main risks are lower demand and higher ingredient cost. I would run a four-week test, measure contribution margin and order volume against comparable stores, and scale only if both remain healthy."
Do not retell the entire case. The interviewer wants your judgement.
Practise the skills separately before doing full cases
Full mock cases are useful, but they are a slow way to fix a specific weakness. Break the interview into drills.
Structuring drills
Take a business prompt and spend two minutes building a structure. Then check:
- Does every branch relate to the objective?
- Are branches meaningfully distinct?
- Did I tailor the structure to this problem?
- Can I explain what evidence each branch would need?
- Did I choose a starting point?
Practise with different problems: falling hospital capacity, a nonprofit expanding services, a retailer entering a city, or a software company changing prices. Variety stops you from forcing every prompt into the same template.
Mental maths drills
Practise percentages, growth rates, weighted averages, break-even calculations, and unit conversions. Write your setup before calculating. Round only when it is reasonable, and say that you are rounding.
Accuracy matters more than theatrical speed. If you make an error, correct it directly and continue.
Exhibit drills
Use public charts from annual reports or official statistics. Give yourself two minutes to identify:
- the chart's subject, period, unit, and segments;
- the largest change or difference;
- one plausible implication;
- one question the chart cannot answer.
This builds the habit of reading before reacting.
Synthesis drills
Read a short business article, close it, and deliver a 30-second summary with an answer, two supporting facts, one risk, and one next step. Record yourself. If the listener must reconstruct your conclusion, try again.
Use official practice cases first
Official material reveals what an employer has chosen to show candidates. It is more reliable than a stranger's confident claim about a secret scoring formula.
McKinsey calls its version a problem-solving interview and publishes sample client scenarios with suggested reasoning. Its interviewing page currently links to several official practice cases. Bain also publishes its own sample cases, and BCG explains the behaviours it wants candidates to demonstrate.
Attempt a case before reading its answer. Use this process:
- Read only the prompt.
- State clarifying questions and build a structure aloud.
- Work through each exhibit without viewing the solution.
- Give a final recommendation.
- Compare your process with the official material.
- Record one specific change for your next case.
Do not copy the sample wording. Learn the reasoning moves.
Review mocks with a scorecard
"That felt bad" is not feedback. Score each practice case from 1 to 5 on:
- objective clarification;
- structure quality;
- prioritisation;
- quantitative accuracy;
- exhibit interpretation;
- business judgement;
- communication;
- synthesis;
- response to hints;
- final recommendation.
Add two notes: the strongest moment and the single highest-priority correction. Work on that correction before the next full mock.
A useful practice partner should interrupt when you are unclear, challenge unsupported assumptions, and make you explain implications. A partner who supplies answers whenever you pause may make the session pleasant and the interview painful.
A seven-day case interview preparation plan
If your interview is close, chalo, keep the plan focused.
Day 1: Diagnose
Complete one official case aloud. Record it. Score yourself and identify the two weakest skills.
Day 2: Structure and prioritise
Do six short structuring drills. Explain what you would investigate first and why.
Day 3: Maths and exhibits
Practise calculations and interpret five charts. Check every unit. Finish each exercise with a business implication.
Day 4: Full case with feedback
Run one live mock with a partner. Ask for evidence-based feedback using the scorecard.
Day 5: Target the weakness
Repeat the drill connected to your lowest score. If synthesis is weak, do ten short recommendations. If maths is weak, practise setups and checks rather than rushing more cases.
Day 6: Realistic simulation
Complete a case under interview conditions. Use the same medium, stationery, timing, and environment you expect on the day.
Day 7: Light review
Review your error log, practise two openings and two final recommendations, test logistics, then stop. Exhaustion is not a preparation strategy.
If you have more time, repeat the cycle with increasing variety. Track weaknesses, not just the number of cases completed.
Prepare the rest of the interview too
A consulting interview may include experience, motivation, or fit questions alongside the case. Prepare concise examples of leadership, conflict, failure, influence, and measurable impact. The STAR interview method guide can help you organise those examples without turning them into scripts.
Research the employer's work, office, role, and stated interview process. Use the company research checklist to separate useful preparation from random browsing.
Prepare questions for the interviewer as well. Ask about team decisions, learning, project staffing, or what distinguishes strong performance in the role. Generic questions answered on the careers page waste the opportunity. This list of questions to ask at the end of an interview gives you practical starting points.
If you are still building your consulting shortlist, JobFinder AI can help you discover relevant openings and organise the application stage. It will not solve the case for you. That part still needs your judgement and practice.
Case interview day checklist
- Confirm the time, time zone, format, and interviewer details.
- Re-read the employer's official process page and your invitation.
- Bring blank paper, pens, water, and a simple calculator only if permitted.
- Test your camera, microphone, connection, and meeting link.
- Close notifications and unapproved AI or note-taking tools.
- Listen to the full prompt before structuring.
- Clarify the objective, metric, period, and constraints.
- State assumptions and show calculations clearly.
- Connect every important number to the business question.
- Pause to synthesize after each major finding.
- End with a recommendation, reasons, risks, and next step.
Frequently Asked Questions
How long should I prepare for a case interview?
There is no universal number of days or cases. Start with a diagnostic mock, identify your weakest skills, and build a plan around the actual interview date. Someone comfortable with business analysis may need more communication practice; another candidate may need more maths and exhibit work. Readiness is better measured by consistent performance across unfamiliar cases than by a case-count target.
Should I memorise case interview frameworks?
Learn common business relationships such as profit equals revenue minus cost, but do not force every case into a memorised framework. Build a structure around the stated objective, explain why each branch matters, and adapt when evidence changes. A simple tailored structure is more useful than an elaborate generic one.
Can I ask questions during a case interview?
Yes. Case interviews are conversations, and clarifying questions are usually essential. Ask questions that define the objective, resolve ambiguity, or unlock the next analysis. Avoid asking the interviewer to choose your structure or provide every missing fact before you begin.
What should I do if I make a maths mistake?
Pause, identify the error, correct it, and explain whether the conclusion changes. Do not hide it or spiral. You can reduce errors by writing the formula first, keeping units beside each number, estimating the expected range, and checking whether the final result is plausible.
Is it acceptable to use AI for case interview practice?
Use AI only within the employer's rules. It can help generate practice prompts, explain concepts, or critique a recorded answer before the interview. Do not use it to generate live answers or during an assessment unless the employer explicitly permits that use. McKinsey's current policy, for example, allows AI-assisted preparation but prohibits real-time generated interview answers and unpermitted assessment use.
What if I know nothing about the industry in the case?
State reasonable assumptions, ask targeted questions, and use the information provided. Interviewers are generally assessing your reasoning, not expecting specialist knowledge that was never required. If the role does require expertise, the recruiter or invitation should clarify that. Never bluff. A transparent assumption is easier to test than invented knowledge.