Strategy Case Interviews: How to Structure Your Answer

Your core business is bleeding 4% a quarter. A side project is growing 30%. The CEO looks at you and says: "I need a recommendation. Where do you start?"

Most candidates I've watched attempt strategy case interview practice get this wrong in the first thirty seconds. They either hedge — "well, it depends on several factors" — or they leap straight to "double down on the growth segment" without doing any maths. Both responses tank the interview. The hedge tells the interviewer you can't commit to a position. The premature leap tells them you can't think.

Strategy cases are the most common format in consulting, strategy, and biz ops interviews. According to a 2024 Management Consulted survey, 78% of consulting firms use case interviews as their primary evaluation method. And yet most candidates prepare by memorising frameworks rather than practising the actual reasoning.

Here's how to stop doing that.

What Makes Strategy Case Interviews So Difficult

A strategy case interview is a structured evaluation where a candidate is presented with a real or simulated business problem — typically involving market dynamics, resource allocation, or competitive positioning — and asked to reason through it live, arriving at a clear recommendation within a limited timeframe.

What makes these brutal is the layering. You're not solving one problem. You're solving three simultaneously: structuring the analysis, performing quantitative reasoning under pressure, and communicating your logic clearly enough that the interviewer can follow every step.

Interviewers are evaluating five things, whether they tell you or not:

1. Did you structure the problem before diving in? If your first instinct is to start talking about solutions, you've already lost credibility.

2. Did you ask sharp clarifying questions instead of assuming? "Is the mid-market decline driven by churn or contraction?" is a vastly better opening than "Let me walk you through a growth framework."

3. Did you reason quantitatively about the segment mix? Saying "the growth segment is growing faster" without calculating when it overtakes the declining segment is the single most common failure mode.

4. Did you land a clear, defensible recommendation? Not "it depends." Not "we could go either way." A position, with reasoning.

5. Did you name the key risk or what would invalidate your recommendation? This is what separates good from exceptional. Anyone can be confident. Showing you've stress-tested your own logic is what senior hires do.

The typical failure looks like this: a candidate hears "shrinking core, growing niche" and immediately says "pivot to the growth segment." They skip the maths entirely. They don't ask what's causing the decline. They don't calculate how long it takes a 30%-growth segment to replace 60% of revenue. They just pattern-match to a framework they memorised.

How to Structure a Strategy Case Answer

Here's the tactical approach that actually works, based on what I've seen separate strong candidates from weak ones across thousands of practice sessions on MORT's interview practice platform.

1. Pause and frame the problem out loud. Before you touch numbers, state the problem back. "So we have a two-segment business where the majority segment is declining and the minority segment is growing. The core question is whether we defend, pivot, or run both — and on what timeline." This takes ten seconds and immediately signals structure.

2. Ask two or three clarifying questions — no more. You're not conducting a discovery workshop. You need to establish: What's driving the decline? (Churn vs. compression vs. competitive loss.) What's the gross margin difference between segments? Is the growth segment's TAM large enough to replace the core? Each question should change how you'd think about the answer.

3. Do the maths on a napkin. If the core is 60% of revenue declining 4% per quarter and the growth segment is, say, 10% of revenue growing 30% per quarter, run the crossover calculation. At those rates, the growth segment doesn't catch up for roughly eight quarters — two full years of declining total revenue. That's not a "just pivot" situation. That's a "defend and invest" situation.

4. Build your recommendation as a portfolio, not a binary. Good looks like: "Stabilise the core through retention plays and selective pricing — buy eighteen months of runway — while accelerating the growth segment with dedicated resources. Target: growth segment at 25% of revenue within four quarters." Bad looks like: "I'd recommend focusing on growth because that's where the momentum is." One is a strategy. The other is a slogan.

5. Name the risk unprompted. "The biggest risk to this recommendation is if competitors start a price war in the core segment, accelerating the decline beyond what retention efforts can offset. If core decline hits 8% per quarter, the timeline collapses and we'd need to accelerate the pivot." This is where most candidates leave marks on the table. According to a Harvard Business Review analysis of hiring decisions, interviewers rate candidates 40% higher when they proactively identify risks rather than waiting to be asked.

6. Handle the curveball without abandoning your structure. When the interviewer says "Board meeting in two weeks — no additional headcount," don't panic. Reframe: "That constrains the investment side but not the strategy. We reallocate existing resources — pull two people from a low-priority initiative in the core segment and assign them to growth. The recommendation holds; the execution timeline shifts."

What good looks like is a candidate who treats the case like a real business decision: structured, quantitative, decisive, and honest about uncertainty. What bad looks like is someone performing a framework from memory without engaging with the actual numbers in front of them.

Practice Makes the Difference

Reading about case structure is like reading about swimming. Useful, but you'll still drown.

The reason strategy cases trip people up isn't that the concepts are hard. It's that the pressure of live reasoning — structuring your thoughts while someone watches, doing mental arithmetic while maintaining a narrative, pivoting when the interviewer throws a complication — is a fundamentally different skill from reading a case book on your sofa.

This is exactly why we built MORT's AI interview practice around dynamic scenarios rather than static question banks. When I was designing the strategy case simulations, the insight that changed everything was this: real interviewers don't follow scripts. They probe your weakest point. If your quantitative reasoning is shaky, they'll push harder on the numbers. If your recommendation is vague, they'll demand specificity. A static practice tool can't do that. An AI interviewer that adapts in real-time can.

From building MORT, I've seen one pattern repeatedly: candidates who practise strategy cases five or more times with adaptive AI feedback improve their structure scores by roughly 2x compared to their first attempt. The improvement isn't from learning new frameworks. It's from getting comfortable with the discomfort of thinking out loud.

The complications matter too. That "competitors are lowering prices" curveball? It's designed to test whether you revise your reasoning or stubbornly defend your initial position. The stakeholder management scenarios test a different muscle — political navigation rather than analytical structure — but the underlying skill is the same: adapting live to new information without losing your thread.

The One Thing to Remember

If you take nothing else from this: do the maths. The single biggest differentiator in strategy case interviews is whether you actually calculate the implications of the numbers you're given or just wave at them directionally. A candidate who can say "at current rates, the growth segment reaches revenue parity in Q3 2028" will always beat one who says "the growth segment is promising."

Similarly, in metric investigation scenarios, the candidates who win are the ones who quantify before they hypothesise. The instinct to calculate rather than narrate is the closest thing to a cheat code in analytical interviews.

Strategy cases don't test whether you know the answer. They test whether you can build one, live, under pressure, and defend it when it gets poked. That's not a knowledge problem. It's a reps problem.