Consulting Case Interviews: A Practical Way to Structure, Calculate and Recommend Under Pressure

Case interviews have a reputation for being mysterious, but the format is fairly predictable once you see what interviewers are scoring. Whether you are applying to a large strategy firm, a boutique, or an in-house strategy team, the interviewer wants to know three things: can you break a messy business problem into logical pieces, can you do quick and accurate maths without panicking, and can you land on a clear recommendation a client could act on. Clarify before you structure The most common early mistake is jumping straight into a framework. Spend the first minute restating the problem in your own words and asking two or three clarifying questions. What exactly does "profitability is declining" mean: margin, absolute profit, or both? Over what time period? Is the client one business unit or the whole company? These questions are not a delay tactic. They narrow the problem and show the interviewer you would not waste a client's money solving the wrong question. Build a structure that fits this case, not a memorised one Interviewers have heard the textbook profitability tree hundreds of times. It is fine to use revenue and cost as your first split, but make the second level specific. For a regional airline, revenue might break into load factor, average fare and number of routes, while costs split into fuel, crew, aircraft leasing and airport fees. Say out loud why each branch matters and which one you would test first. A tailored structure with a clear hypothesis ("I suspect fuel costs, given the timing") beats a generic tree every time. Make the maths visible Case maths is rarely hard, but it is done out loud and under time pressure. Write numbers clearly, round sensibly and tell the interviewer what you are doing: "Let me round 48 million passengers to 50 to keep this quick, and I'll adjust at the end." Always finish a calculation with the "so what". A number on its own earns little credit; "so fuel is now 38 percent of costs versus 30 percent last year, which explains most of the margin drop" earns a lot. Read charts like a consultant Many cases include an exhibit. Before diving into details, state the title, axes and units, then the one or two biggest takeaways. Resist the urge to describe every bar. Interviewers want to see that you can pull out the insight that moves the case forward. Synthesise and recommend At the end, or whenever the interviewer asks "what would you tell the CEO?", lead with the answer. Give a one-sentence recommendation, two or three supporting reasons from the case, and the main risks or next steps. Do not re-walk the whole case. Practise this out loud until a 45-second synthesis feels natural. Practise with realistic pressure Reading casebooks helps, but the real skill comes from live practice with a partner who will interrupt, push back and throw new data at you. Record a few sessions and listen for filler words and long silences. Many candidates now also use AI tools for live support. Linkjob AI (https://linkjob.ai), for example, gives real-time help during job interviews and technical interviews. It can prompt you with a structure or remind you to finish a calculation with its implication when nerves take over. Do not ignore the fit questions Case performance often decides the outcome, but weak fit answers can still sink you. Prepare two or three stories about leadership, teamwork and persuading someone who disagreed with you, each under two minutes. Consulting firms care about how you would come across in front of a client as much as how you solve the case. Treat each case as a conversation with a future colleague, not an exam. Stay structured, keep the maths clean and always end with a clear point of view.