How to present your case interview structure (word for word)

The first minutes after the interviewer asks how you would approach it decide more than any other moment in the case. The four moves interviewers listen for, a word-for-word example, and a drill to make it automatic.

There is one moment in every case interview where the interviewer forms most of their opinion of you. It is not the math and it is not the final recommendation. It is the 90 seconds you spend presenting your structure after they ask "how would you approach this?"

A strong structure presentation has four moves. You take a moment of silence to build. You open with a headline and name all your buckets before you touch any of them. You drill into each one, two levels down, in language that only fits this client. And you close with a hypothesis, where you would start and why, then check in. That is the whole skill. The rest of this guide shows you each move word for word, then gives you a drill to make it automatic.

What the interviewer is actually listening for

Interviewers are not checking your structure against an answer key. They are listening for three signals. Can you think top-down, meaning the big picture comes before the detail? Did you build this for my client, or could this slide into any case? And are you driving, meaning you tell me where we go first instead of waiting to be pushed?

A memorized template fails all three at once. A custom structure delivered as a confident roadmap hits all three, even when a bucket is missing. Prioritization itself is a scored signal. Saying "I would start here, because" earns more credit than a fourth bucket ever will.

The four moves

Move 1: take the silence. By this point you have confirmed the objective with one or two sharp questions. Now ask for a moment to structure your thoughts. Somewhere between one and two minutes is normal, and the prep guides say so in as many words. Rushing into a half-built structure to avoid the pause is the more common and more expensive mistake.

There is one condition on that silence. It reads as work while the interviewer can see you writing, and as being stuck the moment it looks like you are staring into the middle distance. In a voice interview they cannot see your pen at all, which removes the only evidence that you are working. Say what you are doing, and the silence buys you the same credit it would across a table.

Move 2: headline, then the whole map. Two things happen before you go into any detail. First, one sentence on what you are about to walk through and why it has that shape. Then the names of all your buckets, in one breath, before you touch a single one of them.

The headline is where most structures are already lost. The weak version is a bare topic list. The version that gets marked down almost as fast is the accounting identity, "profit equals revenue minus cost, so I will look at revenue and cost." That is true, it is also the shape of every profitability case ever written, and it tells the interviewer nothing about whether you understand this business. The strong version starts from how this client actually earns money. "A bakery chain earns on a lot of small transactions, so I want to look at three things." Same rigour underneath, built for this client on top.

Then name the three. Not one bucket and its details, then the next. All three first. The interviewer now knows the size and shape of what is coming and can follow the detail instead of guessing where it is going.

Move 3: drill into each bucket, two levels down. Now go back to the top and work through them one at a time. Each bucket splits into two or three sub-branches, and each sub-branch names the concrete thing you would actually look at. Bucket, sub-branch, specific item. That is the depth the school casebooks put in their own worked structures, and it is where most candidates stop one level short.

Tailoring lives at those lower levels. "Costs" is generic. "Fuel, crew, and airport fees, since those are an airline's big three" could only be said about an airline. Keep the buckets from overlapping too, so that every finding you make later has exactly one place to land. And never announce a framework name. Saying "I will use the profitability framework" tells the interviewer you are reciting, and the strictest interviewers start discounting you before the sentence ends. The full case against memorized frameworks is its own guide, see why memorizing case frameworks fails.

Move 4: close with a hypothesis, a priority and a check-in. Say what you think is going on, say which bucket you would open first, and give the reason. Then hand the turn back: "does that work as a plan?" This is what makes it a conversation instead of a monologue, and it is the move most candidates skip entirely. A structure without a stated starting point makes the interviewer do the driving.

Word for word: a strong presentation

Here is the whole thing assembled. The case: a regional bakery chain has seen profits fall for two years while revenue held steady.

Read it again and notice the order. All three buckets are named before any of them is opened. That single move is what makes it top-down: the interviewer gets the map first and can then follow the detail instead of guessing where it leads. Interleaving them, one bucket and its details, then the next, is the default and it is a level weaker.

Then look at the depth. Basket splits into price and mix, and mix splits again into coffee and pastries against the plain loaf. Three levels, and the third level is where the bakery actually appears. The first two levels of almost any profitability structure are interchangeable. Only the bottom level proves you were thinking about this client.

Finally, watch where the new stores went. They never became a fourth bucket. They sit inside the cost of keeping the doors open, because that is where they act. Buckets that overlap are the quiet way a structure loses the room, because the interviewer stops being able to tell where a finding is supposed to land.

The same structure, presented badly

Same case, same underlying ideas, delivered the way most first-time candidates deliver it.

This is the version that actually costs people offers, because it sounds fluent. The candidate clearly knows the industry and the details are tailored. It still scores badly, and the reason is the order. There is no headline and no list of buckets, so the interviewer never gets a map. The delivery dives four levels into ingredients before a second bucket exists, which means every detail arrives before the listener knows what it is a detail of. And there is no hypothesis, no priority and no check-in, so the interviewer has to do the driving. Fluency is not structure.

Adjusting for interviewer-led cases

Everything above assumes a candidate-led case, the format most commonly associated with BCG and Bain, where your structure sets the agenda for the next twenty minutes. In an interviewer-led case, the format McKinsey is known for, the opening structure question is scored on its own, so take the full minute and present the full structure there too. What changes is everything after it. Each follow-up prompt gets its own mini-structure, thirty seconds, a headline plus two or three buckets, and then the interviewer takes the wheel again. That is the format, not a signal you structured badly. One caveat on the firm labels: treat them as a rule of thumb, not a rule. Formats vary by office and round, and it is a fair question to ask your recruiter beforehand. If you know where you are interviewing, our firm-by-firm guides say which format that firm actually runs.

Drill this

Structure presentation is a rep skill. You can get noticeably better in five days.

1. Take any case prompt. Any casebook you already own works, and every practice case in CaseRound opens with one.
2. Give yourself 90 seconds of prep, by the clock.
3. Record yourself presenting the structure out loud. Phone voice memo is fine.
4. Score the recording with five yes-or-no checks. Headline in the first sentence? All your buckets named before you opened any of them? Three levels deep, with the bottom level saying something that would be false for a different industry? A priority with the word "because" in it? Under 90 seconds on the timer? Five yeses is a pass.
5. Do the same prompt again immediately. The second take is always sharper. Then move to a new prompt.

One prompt a day, two takes each, five days. The out-loud part is what matters. A structure that reads well on paper regularly falls apart between your brain and your mouth, and interviews happen out loud.

Frequently asked questions

Interviewing somewhere specific?

Read next