Case Interview Math: Fast, Accurate, and Out Loud

Case interview math tests whether you can drive an analysis with numbers, not whether you can compute. The arithmetic itself rarely goes beyond multiplication, division, and percentages. What interviewers actually evaluate is whether you set up the calculation correctly, keep your audience with you, and know what the answer means once you have it.

This reframing matters for how you practice. Drilling mental arithmetic helps, but the higher-leverage skill is structuring: writing the equation before touching any numbers, so the computation becomes mechanical instead of exploratory.

The single biggest differentiator in case math is announcing your approach before calculating. Say the formula out loud: 'Revenue impact equals stores, times customers per store per day, times conversion, times average ticket.' Then confirm the inputs. Only then compute.

This does three things at once. It lets the interviewer correct a wrong assumption before you waste two minutes on it. It keeps you from losing the thread mid-calculation. And it demonstrates the exact skill consulting firms hire for: turning a vague question into a computable one.

Round early, round hard, and say that you're doing it. Turning 47 million customers into 50 million and $9.20 into $9 makes the arithmetic trivial, and no interviewer objects to rounding that is announced and directionally tracked.

The discipline is keeping a mental note of which way your rounding pushes the answer. If you rounded two inputs up, say so when you present the result: 'roughly $450 million, and slightly high because I rounded up twice.' That single sentence signals more numeracy than a perfectly precise calculation ever could.

Silence is where case math goes to die. Thirty seconds of quiet scribbling feels like three minutes to an interviewer, and it removes their ability to steer you. Narrate the mechanics in a low-key way: '50 million times 9 is 450 million; taking 20 percent of that gives me 90.'

If you need genuine quiet for a hairy step, ask for it: 'Give me twenty seconds to run this multiplication.' Buying silence explicitly reads as control. Drifting into it reads as drowning.

Before presenting any result, run one order-of-magnitude check. Does $450 million in incremental revenue make sense for a client whose total revenue is $2 billion? A 22 percent uplift from one initiative should trigger suspicion, and voicing that suspicion is exactly what a strong candidate does.

Interviewers deliberately build cases where a slipped zero produces an absurd answer. Candidates who present 10x-wrong numbers with confidence fail on judgment, not arithmetic. Candidates who catch their own error—'that seems too high, let me re-check the units'—often score better than those who never erred.

A calculation is only finished when you say what it means for the client's decision. '90 million in savings' is an output. '90 million in savings, which is about half the profit gap we're trying to close—so this lever alone won't get us there' is an answer.

Make the so-what a reflex: every time you land a number, attach one sentence of implication before the interviewer asks. This habit, more than speed, is what separates candidates who feel like future consultants from candidates who feel like calculators.

Ten minutes a day beats a weekend cram. Practice percentages of large numbers, revenue-style multiplications, and breakevens—out loud, standing up, narrating as if an interviewer were present. The narration is the skill; silent drilling doesn't transfer.

Then fold math back into full case practice: take any completed case and redo only its quantitative sections, focusing on setup and so-what rather than speed. Two weeks of this routine removes math as a source of interview anxiety for most candidates.