How to Prepare for a Case Interview

To prepare for a case interview, learn the format, practice breaking unfamiliar business problems into a few logical parts, brush up on quick math, and rehearse out loud with another person. The round tests how you think, not whether you reach one correct answer, so your practice should focus on structure, clear assumptions, and a firm recommendation at the end.

Case interviews are best known from consulting, but they also show up in strategy, product, operations, business analyst, and some finance hiring, often in a shorter and less formal version. If a recruiter tells you to expect a case, this guide covers what will happen and how to get ready without buying a stack of courses.

What a case interview actually tests

You get a situation, a little information, and a question. A regional grocery chain's profit has fallen for two years: why, and what should it do? A software company is thinking about launching a cheaper plan: should it? The interviewer holds extra data and hands it over when you ask for the right thing.

Most interviewers are watching for four things:

• Structure. Can you split a messy question into sensible parts and work through them in an order that makes sense?
• Comfort with numbers. Can you estimate, calculate, and say what a result means for the decision?
• Judgment. Do you focus on what matters most, and notice when a number looks wrong?
• Communication. Could this person explain their thinking to a colleague or client without losing them?

That is why a wrong turn rarely ends your chances. A candidate who spots a dead end and redirects can look stronger than one who recites a tidy but generic answer.

How the round usually runs

Formats vary, so ask the recruiter what to expect. A live case commonly follows this sequence.

1. The prompt

Write down the key facts as you hear them. Then play the question back in one sentence and confirm the goal. "So we want to know why profit fell and what would restore it within two years. Is that right?" This takes seconds and protects you from solving the wrong problem.

2. Clarifying questions

Ask only what would change your approach: which markets, what time frame, what the company means by success. Skip questions that just fill the silence.

3. Your structure

Ask for a minute to think, sketch three or four branches, and walk the interviewer through them. Explain why you are starting with one branch instead of another.

4. Analysis

Ask for data, run the numbers, and say what each result tells you. Keep referring back to your structure so the interviewer can follow where you are.

5. Recommendation

Lead with the answer, give two or three reasons, name the main risk, and suggest a next step. Do not retell the whole case in order.

Some employers use a different format, including a written case with a data pack, a take-home, or a presentation. For those, our guides to take-home assignments and presentation interviews will help alongside this one.

Build a structure that fits the question

You will find plenty of named frameworks online. They are useful as vocabulary, but they become a problem when you force every question into the same template. Interviewers have heard those templates many times, and a generic one tells them little about you.

A better habit is to ask, "What would have to be true for this decision to be right?" Then turn the answer into branches. Take the question of whether a gym chain should open in a new city:

• The market: Are there enough likely members, and how well served are they already?
• The economics: What would a location cost to open and run, and how many members would it need to break even?
• The company's ability: Can it staff, manage, and fund this without hurting existing locations?
• The risks: How might competitors respond, and how hard would it be to exit if the location fails?

Consultants often describe a good structure as MECE, short for mutually exclusive and collectively exhaustive. In plain terms, your branches should not overlap and should not leave out anything major. You do not need to say the term aloud. You just need to avoid having two branches that cover the same issue.

A few basic building blocks are worth knowing because they appear so often:

• Profit = revenue minus costs
• Revenue = price times quantity sold
• Costs = fixed costs plus variable costs
• Break-even volume = fixed costs divided by contribution per unit (price minus variable cost per unit)

The math to brush up on

Case math is usually simple arithmetic done under mild pressure. The difficulty comes from doing it out loud and connecting it to the decision. Practice these:

• Percentages and percentage change, including going from a growth rate to a dollar amount
• Multiplying and dividing with large numbers by tracking zeros, such as 40 million times 3 percent
• Margins, break-even, and simple payback periods
• Market sizing, where you estimate a number from reasonable assumptions

Here is a made-up break-even example of the kind you might see. A new product has $600,000 in annual fixed costs, sells for $50, and costs $20 per unit to make. Each unit contributes $30, so the company needs to sell 20,000 units a year to break even. Do not stop at 20,000. Say what it means: "If the addressable market is only 100,000 buyers, we would need a 20 percent share just to break even, which looks aggressive for a new entrant."

That last sentence is where a lot of candidates separate themselves. Round when you can, say that you are rounding, and sanity-check any result that looks surprisingly large or small.

A two-week practice plan

Adjust this to your timeline. The point is to spend most of your hours talking through cases, not reading about them.

• Days 1-2: Learn the format. Read through a few published sample cases. Many large consulting firms post examples and guidance on their careers pages, and those are worth using even if you are not applying there. Note how the good answers are organized.
• Days 3-5: Practice structuring alone. Take ten business questions from the news and give yourself two minutes to sketch a structure for each. Do not solve them.
• Days 3-14: Do ten minutes of math daily. Short, regular sessions beat one long cram.
• Days 6-12: Run live cases with a partner. Aim for several full cases with someone who can play the interviewer, ideally a person who has done these before. Record one and listen back for filler words and long silences.
• Days 13-14: Tailor to the employer. Practice problems close to the role and the company's actual business. Research how the company makes money, and rehearse your closing recommendation until it comes out cleanly.

After each practice case, write down one thing to fix next time. Repeating cases without feedback mostly makes you faster at the same mistakes.

If the role is not in consulting

Outside consulting, the case is usually closer to the job itself. A product candidate might be asked how to improve activation for an app. An operations candidate might be asked why a warehouse is missing delivery targets. A business analyst might get a small data set and be asked what they would tell a manager.

Before you prepare, ask the recruiter three questions:

• Is the case live, written, or presented?
• Will it be about this company's business, or a general one?
• Is a calculator, spreadsheet, or laptop allowed?

These are normal logistics questions and they can change how you practice. The job description is also a good guide. If it emphasizes pricing, retention, or forecasting, expect the case to lean that way. Career changers can treat this round as a real opportunity, because it lets you show how you think when your resume does not yet show the industry. Pair that with a clear account of why you are changing careers.

Common mistakes and how to avoid them

• Starting before you confirm the goal. Play the question back first.
• Going silent. Taking a moment to think is fine if you say so. Long stretches of unexplained silence leave the interviewer nothing to assess.
• Analyzing everything equally. Say which branch you think matters most and start there.
• Reporting numbers without a "so what." Each calculation should change or support what you think.
• Ignoring hints. If the interviewer steers you, follow it. They are often trying to help you reach the part of the case that counts.
• Refusing to commit. "It depends" is not a recommendation. Pick a position based on what you know and state what would change your mind.

How to prepare the day before

Do one light practice case and some math, then stop. Prepare paper, pens, and, for a video round, a tested camera and a clean background (our live video interview guide has a full checklist). Have two or three questions ready about how the team makes decisions. If your interview also includes a resume or behavioral section, review the STAR method and your best stories. And if you tend to freeze under pressure, our guide on how to calm interview nerves has techniques you can practice alongside your cases.