What a case interview actually is

Intuition

A case interview is a business problem with the answer deliberately removed. The interviewer hands you a messy situation ("a regional airline is losing money, why?") and watches how you think your way toward an answer rather than whether you already know one.

Think of it like a cooking test where they hand you a fridge full of random ingredients. They are not checking whether you memorized a recipe. They want to see whether you can look at what you have, decide on a dish, and cook it without panicking.

Framework

Every case is really testing four things at once:

• Structure, can you break a vague problem into clean, logical pieces?
• Analysis, can you do the math and read the data without errors?
• Judgment, do your conclusions actually make business sense?
• Communication, can the interviewer follow your logic the whole way?

A weak candidate jumps to answers. A strong candidate makes their thinking visible at every step.

Worked Example

"Should a coffee chain add delivery?" A weak start: "Yes, delivery is growing." A strong start: "Let me structure this around three things, the size of the delivery opportunity, whether our economics work once we add delivery fees and commissions, and how it affects our existing in-store experience. Can I start with the economics?"

Same question. The second answer already sounds like someone you'd trust in a client meeting.

Now a heavier industry, same divide. "A steel producer's output fell 12%." Weak: "Maybe machines are breaking down?", a guess wearing a question mark. Strong: "Output is line-hours run times tons per hour. So either we lost run-time, downtime, staffing gaps, or the lines slowed. Which does the data show?" The weak answer hopes it's right; the strong one builds a small machine that finds the answer whatever the data says.

In the room

The first two minutes decide how the interviewer reads everything after. Three sentences to have ready, verbatim. After the prompt: "Just to confirm the objective, our client is the coffee chain, and we're deciding whether delivery grows profit, not just revenue. Is that right?" Then: "Could I take thirty seconds to organize my thoughts?" The answer is always yes; asking signals control, not weakness. When you return: "I'd structure this around three things…", and name them for this client, not for consulting in general. While you do this, the interviewer is scoring exactly one thing: faced with ambiguity, did you reach for structure or for an answer? Say those three sentences in that order and you've passed the opening test before any analysis begins.

Pitfalls

• Reciting a framework name instead of adapting to the actual question.
• Going silent to do math, the interviewer can't follow you.
• Answering before you've structured the problem.