Consulting interview prep: beyond the case

Most consulting candidates over-prepare for the case and under-prepare for everything around it. That's backwards: the case tests a structuring habit you can genuinely drill into reflex, while the fit round and the moments between cases are where strong candidates with good frameworks still lose offers. Here's what the full loop actually tests and how to prepare for the parts people skip.

The loop isn't just the case

A typical consulting loop is a case round (a business problem you structure and work through live, usually interactively with the interviewer), a fit or personal experience round (your stories about leadership, teamwork, and overcoming obstacles, scored just as rigorously as the case), and often a written case or group exercise at later rounds. Firms screen out candidates in the fit round constantly — a sharp case performance paired with a generic, unrehearsed fit story is a common way good candidates lose offers they were otherwise winning.

A framework for structuring any case

1. Restate the question and ask clarifying questions. Confirm what "success" means for this specific prompt before building a structure — the same surface question can imply different real objectives.
2. Build a structure out loud before diving into numbers. Lay out the 3-4 buckets you'll explore (e.g., market, competition, internal capability, financials) and briefly say why those are the right buckets for this problem, not a memorized template applied blindly.
3. Work one branch at a time, narrating as you go. Pick the highest-leverage bucket first and say why, rather than working all branches shallowly.
4. Synthesize before the interviewer asks. At each checkpoint, state what you've learned and what it implies, so the interviewer sees you connecting findings to the recommendation as you go, not just at the very end.

The most common structural failure is building a structure that's technically correct but generic — applying a standard framework without adapting it to what's actually distinctive about this prompt. Interviewers notice immediately when a structure was memorized rather than built for the problem in front of them.

A worked example: opening a market-entry case

"Before I structure this, I want to confirm: when you say 'should they enter,' are we optimizing purely for financial return, or are there strategic reasons — like defending an existing market — that matter here too?" [Interviewer: "Assume it's purely financial for now."] "Got it. Then I'd structure this around three things: the size and growth of the target market, how attractive it is given existing competition, and whether the company has the capabilities to compete there profitably. I'd start with market size and growth, since if that's weak the rest may not be worth exploring in depth — then move to competitive intensity, and finish with capability fit."

Notice the clarifying question up front, the structure stated and briefly justified before any numbers, and an explicit reason for sequencing one bucket first. All three are what separates a structured answer from a memorized one.

Preparing the fit round properly

Build a small bank of 5-6 stories in advance — a time you led under ambiguity, handled conflict with a teammate, and recovered from a real setback — and rehearse each one out loud so the timeline comes out smoothly under pressure rather than being reconstructed live; see behavioral interviews and the STAR method for how to structure each story so it lands in under two minutes. Treat the fit round with the same seriousness as the case: a candidate who nails every case but gives flat, unrehearsed fit answers is a well-known pattern interviewers are trained to catch.

Common mistakes to avoid

• Jumping to numbers before structuring. Diving into calculations before laying out buckets reads as disorganized even when the math is right.
• Applying a memorized framework without adapting it. A generic structure that ignores what's distinctive about the prompt signals pattern-matching, not reasoning.
• Going silent while thinking. Interviewers score the structuring process, not just the final recommendation — narrate your thinking as you go.
• Treating the fit round as a formality. Unrehearsed, generic stories in the fit round sink otherwise strong candidates constantly.
• Skipping synthesis. Working through every branch without ever stating what it implies leaves the interviewer to connect the dots themselves.

Bottom line

The case tests a structuring habit you can genuinely drill; the fit round tests whether your stories are as rehearsed as your frameworks. Prepare both with equal seriousness — clarify the goal, build an adapted structure, narrate as you go, and bring real, practiced stories to the fit round — and you remove the two most common ways strong candidates still lose offers.

Related: How to prepare for a consulting case interview · Behavioral interviews and the STAR method · How to prepare interview stories (a reusable bank)