In this guide
Interviews and salary conversations
Case interviews: how to structure your thinking out loud
A plain introduction to case interviews: how to clarify the problem, build a structure, work through numbers aloud and give a clear recommendation.
What a case looks like
Cases are common in consulting and increasingly used for strategy, analyst, product and operations roles. A typical prompt is short and open: a cafe chain's profits have fallen, a hospital wants to reduce waiting times, a software company is deciding whether to enter a new market. You are expected to ask questions and lead the analysis.
Four steps that work for most cases
- Clarify: restate the problem and ask what success looks like, the time frame and any constraints.
- Structure: say how you will break the problem down before you start analysing, and check the interviewer is happy with it.
- Analyse: work through each branch, asking for data, doing the arithmetic aloud and saying what each finding means.
- Recommend: give a clear answer first, then the two or three reasons, then the main risk and what you would check next.
A short worked case
Illustrative example
A regional cafe chain's profit has fallen over a year
- Clarify: “Is the goal to restore profit to last year's level? Is the fall across all branches or some? Has anything changed in the market?”
- Structure: “Profit is revenue minus costs, so I'd look at each. Revenue splits into customers and spend per visit; costs into ingredients, staff and premises.”
- Analyse: the interviewer says visits are flat, spend per visit is flat, but ingredient costs are up sharply. “So the problem is mainly costs. Is the increase across all ingredients, or a few?” Dairy and coffee beans account for most of it.
- Recommend: “I'd focus on supplier terms for dairy and coffee first, then test a modest price change on the drinks most affected. The risk is losing price-sensitive customers, so I'd trial it in a few branches before rolling it out.”
The numbers in a real case come from the interviewer. You are not expected to know them.
Doing numbers aloud
Round sensibly and say so (“I'll call that roughly a third”). Write down intermediate results so you do not lose them. After every calculation, say what it means for the problem: a number with no interpretation does not move the case forward.
Habits interviewers notice
- I asked clarifying questions before diving in.
- I said my structure out loud and checked it.
- I summarised where I was before moving to the next branch.
- I interpreted each number rather than just calculating it.
- I gave a recommendation even though the information was incomplete.
How to practise
Practise with a partner who reads the case and holds the data, because cases are interactive. Many firms publish example cases and explain their own format on their careers pages, so check the employer's site first. After each practice case, ask your partner where you lost the thread, not just whether the answer was right.
Common questions
Is there a right answer to a case interview?
Sometimes there is a stronger answer, but interviewers mostly assess the structure, reasoning and communication. A well-reasoned recommendation that differs from the expected one can still score well.
Should I memorise case frameworks?
Know a few ways of breaking down problems, but adapt them to the case. Forcing a memorised framework onto the wrong problem is easy for interviewers to spot.
Put it into practice
Prepare with interview practiceDrafted with AI assistance and checked against Luceria’s editorial standards. Examples are illustrative, not real people’s results. Spotted something out of date? Tell us.