If you've been told your interview includes a case study and you're not interviewing at McKinsey, you might be surprised. Case-style interviews have spread well beyond consulting. Product managers, operations leaders, strategy roles at tech companies, and even some startup generalist positions now include them.
The good news: if you're not going into consulting, you don't need the six-month consulting prep routine. You just need to understand the basics and know what they're actually evaluating.
Where Case Interviews Show Up Outside Consulting
Product management: Companies like Google, Meta, Airbnb, and countless others give product case questions in PM interviews. "How would you improve YouTube's homepage?" or "You're the PM for Gmail. What metric would you optimize and why?" are the kind of cases you'd see.
Operations and supply chain: "A fulfillment center is running at X% efficiency. What would you do to improve it?" is an operations case. These test analytical thinking and process knowledge.
Business strategy and corporate development: Internal strategy roles at larger companies often mirror consulting interview formats because the people hiring for them often came from consulting.
Startups - growth and general roles: Especially at growth-stage companies, it's not uncommon to get a mini case: "We're thinking about entering the European market. Walk me through how you'd think about it."
Analytics and data roles: Some data and analytics interviews include cases where you're given data and asked to analyze it or draw conclusions.
The format varies. Sometimes it's in the interview itself, conversational. Sometimes it's a written exercise you do ahead of time. Sometimes it involves a dataset. Know which format to expect and ask the recruiter if it's not clear.
The Basic Structure of a Case
Most case interviews follow a loose structure:
1. You're given a problem. "Our client is a mid-sized grocery chain whose profitability has been declining. What would you look at?"
2. You ask a few clarifying questions. You don't want to charge ahead without making sure you understand the scope. "Is the revenue declining or just margins?" "Is this in a specific region or across all stores?" Asking good questions shows structured thinking.
3. You structure your approach. Before diving in, lay out how you're going to think about it. "I'd want to look at this from a revenue side and a cost side. On the revenue side, I'd look at traffic, basket size, and pricing. On the cost side, I'd look at COGS, labor, and overhead." This shows the interviewer you're organized, not just guessing.
4. You work through it with their input. Cases are dialogues, not monologues. The interviewer will give you data, redirect you, or ask follow-up questions. Stay flexible.
5. You give a recommendation. Most cases end with "so what would you recommend?" They want a clear, confident answer - even if it's a simple one. "Based on what we've found, I'd prioritize reducing shrinkage and piloting a loyalty program in the top two markets" is better than "it depends."
Frameworks That Actually Help
Consulting prep often teaches frameworks as recipes: use BCG Matrix here, Porter's Five Forces there. For non-consulting roles, you don't need to memorize a list of frameworks. You need a few flexible ones.
Profitability framework: Revenue minus cost. If something is less profitable than expected, you look at what changed on each side. Simple, but it's the backbone of most business problem cases.
Revenue = Volume x Price Cost = Fixed + Variable
Start here for any financial problem.
Market sizing: Break a large, unknown number into smaller, estimable pieces.
Example: "How many coffee shops are in the US?"
Start with population (roughly 330 million). Roughly 100 million households. Maybe 30% of households include a regular coffee shop visitor. So around 30 million regular visitors. If each coffee shop serves some number of customers per day, and each shop serves a local area... and you work toward a rough number.
Market sizing is about showing you can think through ambiguity systematically. Your final number matters less than your process.
Customer funnel: Awareness, acquisition, conversion, retention. Useful when the problem is about growth or engagement. Where in the funnel is the drop-off?
First principles thinking: When there's no obvious framework, break the problem down to its basic components and reason from there. "What is this actually trying to accomplish? What are all the inputs and outputs? What would change if we changed X?"
What Interviewers Are Actually Testing
In non-consulting settings, case interviews are usually evaluating three things:
Structured thinking. Can you break a messy problem into clear parts? Can you organize your thinking out loud? People who can do this are easier to work with and more likely to communicate clearly.
Comfort with ambiguity. You're often given incomplete information and asked to reason through it anyway. The question isn't "do you know the answer?" It's "how do you approach problems when you don't have all the data?"
Communication. Are you easy to follow? Can you explain your reasoning in a way that a stakeholder could act on? Cases often reveal communication weaknesses that behavioral interviews don't.
What they're usually not testing: deep industry knowledge, memorized frameworks, or your ability to produce the "correct" answer. There usually isn't one correct answer.
How to Practice Without the Full Consulting Prep Routine
You don't need to do 200 practice cases. For non-consulting roles, 10 to 20 is usually plenty. Here's how to use that time:
Practice market sizing out loud. Pick a random object or market and estimate its size. How many piano tuners are in Chicago? How large is the US dog food market? Do this regularly and you'll get comfortable quickly.
Look up example case questions for your specific role. PM cases are different from ops cases. Find examples specific to the kind of role you're interviewing for.
Practice giving recommendations. One thing people struggle with is making a crisp recommendation at the end of a case. After every practice case, make yourself state a clear "I would recommend X because..." and commit to it.
Do a few with another person. Cases practiced alone aren't the same as cases with someone asking follow-up questions. Even one or two sessions with a friend helps a lot.
The goal for non-consulting roles isn't to be flawless. It's to show you can think clearly, structure your reasoning, and communicate well under mild pressure. That's it.
Vidal Graupera
October 11, 2025