Case Study Interview: What It Is and How to Pass It

What is a case study interview?

A case study interview is a structured conversation in which you solve a business problem live, with the interviewer playing the client. The problem is usually a situation the interviewer met on a real engagement: a CEO who must cut costs by 15%, a consumer goods firm planning a launch, an industrial company weighing a new market.

You have about 30 minutes and no calculator. The interviewer holds the data and releases it when you ask the right questions. At the end you give a recommendation that a client could act on. For the full recruiting picture, including online assessments and fit interviews, see the complete case interview guide.

Why consulting firms rely on it

Consulting firms rely on the case study interview because it mimics the job. A new consultant joins an unfamiliar industry, faces a messy problem and a skeptical client, and must make sense of it quickly. The case recreates that pressure in half an hour.

The logic is a hypothesis: candidates who handle an unfamiliar problem well in the interview will handle unfamiliar problems well on the job. Firms have never published proof of that link, but they keep using the format because nothing else simulates the work as closely.

The bar is high. In my experience roughly one candidate in ten advances from each round, and most firms run two rounds, sometimes with an extra partner interview. That makes the overall odds after the resume screen small, and it explains why preparation separates candidates more than raw talent.

Stephan's note: When I interviewed candidates, I was rarely checking whether they found "the" answer. I was checking whether I could put them in front of a client next month. A clear structure, a stated hypothesis and clean math told me yes.

Skill 1: be hypothesis-driven

Being hypothesis-driven means you commit to a likely answer early and then test it with data. Consultants work this way because it saves time: you collect only the data that could prove or kill your idea.

Worked example: a falling-profits case

The interviewer says: "Our client, a mid-sized furniture maker, has seen profits drop 25% over three years. Revenue has been roughly stable. What is going on?"

A weak candidate starts listing everything that could affect profit. A strong candidate does three things:

1. Makes the thinking explicit. "Profit equals revenue minus costs. You mentioned revenue is stable, so the drop most likely sits on the cost side."
2. States the hypothesis. "My hypothesis is that variable costs, probably wood and freight, have risen faster than prices."
3. Requests the data to test it. "Could I see the cost breakdown for the last three years, split into materials, labor, freight and overhead?"

The interviewer shows that materials rose 30% while overhead stayed flat. The hypothesis holds, and the candidate moves straight to the next question: can the client pass the increase on through prices, or switch suppliers? If the data had shown flat materials, the candidate would have dropped the hypothesis and tested the next branch. A disproved hypothesis still moves the case forward, because it rules out a branch.

Skill 2: break the problem down

Breaking a problem into segments reveals patterns that averages hide. A company total can look stable while one part collapses and another grows.

Three segmentations come up again and again:

• By business unit. Overall profit is flat, but one unit makes healthy money while two others lose it. The answer is about portfolio choices, which the company total never showed.
• By market segment. Total market sales are flat, but the premium segment grows 12% a year while the budget segment shrinks. The client's position in each segment matters more than the total.
• By customer group. Large accounts buy on price and small accounts buy on service. One strategy for both groups fails both.

Good segmentation follows the MECE principle: no overlap between groups and nothing left out. Ask the interviewer whether data exists by segment as soon as a total number looks suspicious.

Skill 3: get the math right without a calculator

Fast, accurate mental math is part of the consultant's daily toolkit. In a client meeting, a partner who spots that a growth figure "cannot be right" earns trust; a consultant who needs a spreadsheet to check it does not.

Interviewers test this deliberately. Expect percentages, growth rates, break-even calculations and market-sizing chains with many zeros. The most useful habits are simple: round to friendly numbers, say your approach before you calculate, and check the order of magnitude at the end. My case interview math guide has worked examples and drills.

How the three skills fit together

The three skills form one loop. You segment the problem to find where the answer could be, form a hypothesis about the most likely segment, then use numbers to confirm or reject it. Each pass through the loop narrows the problem until you can make a recommendation.

How to practice

Practice live, with another person, out loud. Reading solved cases teaches you the patterns, but only live practice trains the communication and the pressure. Find a partner, take turns as interviewer and candidate, and review each case for structure, math and synthesis.

Free case collections from university consulting clubs are a good start, and I wrote 20 original prompts for you in case interview questions. A structured six-week schedule is in case interview preparation.

If you want worked solutions to compare against, my book Cracking the Case contains three business-case frameworks and three fully worked candidate cases, written from the interviewer's side of the table.