How to Prepare for a Case Interview (Internship)

You have a consulting or finance internship interview coming up, and "just do 50 cases" is the only advice anyone's given you, which is both vague and a little terrifying. Here's the reframe: a case interview is a structured conversation, not a test with one right answer, and you can get functional in the weeks or even days you have left. This guide gives you one repeatable loop that works on any case, the reasoning habit interviewers are actually grading, an honest take on the math, and a prep plan keyed to how much time is on the clock. No paid coach required.

What a case interview actually is

The interviewer hands you an open-ended business problem and watches how you take it apart. "Our client is a coffee chain and their profits are falling. Why, and what should they do?" There's no single correct answer waiting in an answer key. They're watching how you break the problem down, do quick math when the numbers show up, and land on a recommendation you can defend.

It's a dialogue, not a monologue. The interviewer will feed you data, react to your logic, and nudge you when you drift. In the interview loop, the case round usually sits after the recruiter phone screen and alongside a behavioral or fit round, so it's rarely the first thing you face. Finance internships sometimes run their own version, often called a case study or a group case, and the underlying skill is the same: structure a messy problem and reason through it out loud.

One note on group cases. If you're put in a room with other candidates to crack a case together, you're being graded on collaboration too. Steamrolling the group to show how smart you are is the fastest way to fail one of those. Build on other people's points, pull in the quiet person, and move the group toward an answer.

The one thing interviewers are grading: your reasoning out loud

Here's the counterintuitive part. They are not primarily grading your final number. They're grading your structured thinking and your communication, and the only way they can see either is if you say your reasoning out loud.

Picture two candidates given the same profit problem. One goes silent, scribbles for two minutes, and announces "cut the marketing budget." The interviewer has no idea how they got there, so they can't give credit for the thinking and can't help when it goes sideways. The second candidate says, "Profit is revenue minus cost, so falling profit means revenue dropped, costs rose, or both. Let me check which before I guess at a fix." Same starting point, but now the interviewer can follow along, agree, and steer. The second candidate is winning even before any math happens.

So thread this habit through everything: narrate your structure, narrate your assumptions, narrate your arithmetic. Silence is the enemy. This is the same principle that runs technical problem-solving rounds, where thinking out loud beats a silent perfect answer, and it matters even more in a case.

A structure-first approach that beats memorizing frameworks

The internet will try to sell you a deck of named frameworks: the 4 Cs, Porter's Five Forces, the profitability tree. Memorizing them and force-fitting one onto every case is a well-known tell. Interviewers have seen the "let me apply the 4 Cs" opener a thousand times, and reaching for a canned template signals you're pattern-matching to a script instead of thinking about this specific client. Frameworks are thinking aids, not answers.

What works instead is one repeatable loop you can run on any problem. Learn this, not a deck.

1. Clarify

Repeat the goal back in your own words so you and the interviewer are solving the same problem. Then ask two or three sharp questions before you dive in. "When you say profits are falling, over what time period, and is it profit or revenue?" "What does the client actually sell, and to whom?" Good clarifying questions aren't stalling. They show you don't blindly charge at a problem, which is exactly the instinct the firm wants.

2. Structure

Build a simple breakdown tailored to this problem, not a template you memorized. For a profit case, start from the plain identity: profit equals revenue minus cost. Then split each side. Revenue is price times volume; cost is fixed plus variable. Aim for buckets that don't overlap and roughly cover the problem (the "MECE" idea, mutually exclusive and collectively exhaustive), but keep it simple. Write it on paper, then turn it around and walk the interviewer through it: "I want to look at revenue and cost separately, and I'd start on the cost side because you mentioned a new supplier." That last line is you driving the case.

3. Work the math out loud

When numbers appear, state your assumptions, show your steps, and sanity-check the result. More on this below, but the rule is the same as everywhere else: say it out loud so your logic is visible even if you fumble the arithmetic.

4. Recommend

Lead with the recommendation, then support it. "I'd advise the client to renegotiate the supplier contract." Then give two or three reasons and one risk or next step. "It's the biggest cost increase we found, it's addressable in the near term, and the risk is supplier concentration, so I'd also line up a backup vendor." Recommendation first, evidence second, is how you sound like a consultant instead of a student narrating a calculation.

You'll start to recognize common types of case you meet: profitability ("why are profits down"), market entry ("should the client launch in a new country"), and market sizing ("how many X are there"). Treat these as patterns you recognize, not scripts you recite. The loop above handles all of them.

The math you actually need (and don't)

The math scares people more than it should. It's arithmetic: percentages, multiplication and division, and estimation. Not statistics, not calculus. The genuinely hard part isn't the calculation, it's interpreting what a number means in business context ("a 12% cost rise on the biggest cost line is the real story here") and staying accurate while someone watches.

Drill the arithmetic until it's boring:

• Mental-math reps. A few minutes a day of multiplying and dividing without a calculator.
• Round and estimate. Turn 19% of 5,300 into "about 20% of 5,000, so roughly 1,000," then refine if needed.
• Percentage conversions. Move fluently between fractions, percentages, and decimals.

Here's a worked market-sizing example. "How many coffee shops are in a city of about one million people?" Say your assumptions out loud and label them as assumptions: "Assume roughly one coffee shop per 1,000 people as a starting guess. That gives about 1,000 shops. Let me sanity-check: a million people, maybe 300,000 are regular coffee buyers, and one shop can serve a few hundred a day, so a few thousand shops feels high and 1,000 feels reasonable." The exact number doesn't matter. The structure, the stated assumptions, and the sanity-check are what earn the marks.

A prep plan by how much time you have left

Find your bucket and start there. This is triage, not a calendar you have to follow perfectly.

About 4 weeks out

You have room to build real fluency. Learn the loop above cold. Work through a handful of firm-published cases solo, out loud, so the four steps become automatic. Do a daily 10-minute math drill. Once the loop feels natural, bring in a practice partner (how to do that is below).

About 1 week out

Stop reading theory. Do timed full cases with a partner, focusing on structure and delivery, not on learning new concepts. After each one, review the exact moment you froze or lost the thread, and fix that. Repetition under mild pressure is the whole game this week.

2 days out and the night before

Do one or two light run-throughs to stay warm, plus a short math warm-up. Sort your logistics: video link tested, quiet room, paper and pen ready. Then rest. Do not cram a new framework the night before. A rested brain that can run the loop beats a tired one holding a deck of half-memorized templates.

How to practice with a partner (for free)

You don't need a paid coach or a subscription. The top firms publish free practice cases on their own careers sites, complete with the logic and suggested answers, and practicing against those means practicing against the real evaluation criteria (McKinsey's practice cases are a good starting point, and BCG and Bain publish their own). University consulting clubs also maintain free casebooks full of practice material.

Run a session like this: one person plays interviewer and reads the case, the other solves it out loud, then you swap. Give feedback on structure and communication, not just whether the final number matched. "You went quiet for a full minute when the exhibit came up" is more useful feedback than "your answer was close." That's the thing self-practice can't catch. Alone, you'll never notice that you go silent under pressure, and a partner will flag it in the first five minutes.

Frequently asked questions

How long does it take to prepare for a case interview?

It varies widely, and anyone quoting you an exact number is guessing. Prep communities generally treat it as several weeks of consistent practice rather than a single cram session. If you have less than that, don't panic: use the time-left plan above and prioritize the loop and delivery over volume.

Do I need a business background to pass a case interview?

No. Firms screen for structured thinking and clear communication, both of which are learnable, and they interview plenty of non-business majors. The handful of concepts you need, like the profit equation or fixed versus variable costs, take only a few hours to grasp. Your ability to break a problem down cleanly matters far more than your major.

How good does my math have to be?

Good enough to do arithmetic reasonably fast and accurately while talking. That means percentages, multiplication, division, and estimation, not advanced math. Approximation is expected and often encouraged. What matters most is explaining each step and sanity-checking the result, so a visible, slightly slower calculation beats a fast silent one.

Should I memorize case interview frameworks?

No. Force-fitting a named framework onto every problem is a common tell that you're running a script. Build a simple custom structure for each case instead, using the clarify-structure-math-recommend loop. Frameworks are thinking aids, not answers, and a breakdown you built for this specific problem always lands better than a template.

Do finance internships use case interviews too?

Some do. Certain finance and banking internships run case studies or group cases as part of the loop, though the exact format and content vary by firm and role, so check what yours actually involves. The structure-first, think-aloud approach transfers directly. Many finance loops also lean hard on fit questions, so it's worth prepping why this firm alongside your casing.

Three things to do today. Pick the loop (clarify, structure, work the math out loud, recommend) and make it the only structure you rely on. Book one partner session this week using a free firm-published case, and start a 10-minute daily math habit so the arithmetic is automatic by interview day. Then keep your pipeline full and browse internships so you have more shots at the rounds you're now ready for.