How to prepare for a consulting case interview — beyond the math

Slaydit · October 2026 · 7 min read

A case interview looks like a math test and feels like a pop quiz, which is exactly why so many strong candidates bomb it. The arithmetic is almost never the hard part. What's actually being graded is whether you can take a vague, messy business question and impose a clear structure on it out loud, under time pressure, while the interviewer watches you think. That's a learnable skill, and it's almost entirely separate from "being good at consulting."

What the case is actually testing

Firms use cases because a resume can't show how someone reasons. The interviewer is watching four things: whether you ask clarifying questions instead of diving in blind, whether you build a structure before you build an answer, whether your math is clean enough that you can trust your own numbers, and whether you can land on a recommendation instead of trailing off in analysis. Candidates who prep by memorizing frameworks often fail on the last point — they produce a tidy structure and then never actually answer the question.

The framework: Clarify, Structure, Synthesize

Clarify. Before you say anything resembling an approach, restate the problem in your own words and ask two or three sharp questions — what's the goal, what's in scope, what do we already know. This buys you thinking time and stops you from solving the wrong problem.
Structure. Build a simple, visible framework — usually a profit tree, a market-sizing breakdown, or a short list of hypotheses — and say it out loud before you dive into any one branch. The interviewer should be able to follow your logic without you explaining it twice.
Synthesize. After the analysis, stop and answer the actual question in one or two sentences: here's my recommendation, here's why, here's the biggest risk. Most candidates run out of time to do this. Budget for it on purpose.

Each step is short on its own. Together they turn a vague prompt into a structured fifteen-minute conversation instead of a scramble.

A worked example

"Before I start building anything, can I confirm the goal — are we deciding whether to enter this market at all, or assuming we're in and figuring out how to grow? And when you say profitability is down, is that company-wide or specific to this one business line? ... Okay, given that, I'd want to break this into price, volume, and cost, and start with volume since that's where the recent changes seem to be concentrated. ... So pulling this together: the volume drop is almost entirely in one customer segment that a competitor just started targeting directly, so I'd recommend a retention offer for that segment specifically rather than an across-the-board price cut, which would hurt margin on customers who aren't actually at risk of leaving."

Notice the shape: a clarifying question before any structure, a structure stated before any numbers, and a closing recommendation that directly answers what was asked — not just a summary of what was calculated.

The mental math nobody tells you to practice

Most case prep focuses on frameworks and skips the actual arithmetic, which is where composure quietly falls apart. Practice rounding aggressively (treat 97 as 100, say so, and move on), doing percentage math by converting to easy fractions, and narrating your math as you go so a small error is visible and fixable instead of silently compounding. Five minutes of mental math drills a day for a week will do more for your composure than another hour of framework theory.

Common mistakes to avoid

Jumping straight to a framework. Skipping the clarifying questions means you might structure the wrong problem entirely.
A framework with no priority. Listing every possible branch with no sense of which one matters most reads as unfocused, not thorough.
Silent math. Crunching numbers quietly in your head hides your process from the interviewer, who can only grade what they can see.
No final recommendation. Running out of time before synthesizing is the single most common way a technically solid case still falls flat.
Treating it like a behavioral interview. A case rewards live structured reasoning, not a rehearsed story — don't try to force one in.

The bottom line

A case interview rewards visible structure, clean math, and an actual answer at the end — in that order. Clarify the question before you touch a framework, structure it out loud, and leave enough time to synthesize a real recommendation. Most candidates lose points on the first and last steps, not the middle one, which is exactly why they're worth deliberately practicing.

Walk into the case with your reasoning ready, not rehearsed.

Slaydit helps you prep grounded answers from your real experience — never generic, never invented — for the questions that come before and after the case itself.

Try Slaydit free →