How to practise the consultant case study round

A typical case is a 20 to 40 minute dialogue built around a real-ish client problem: falling profits, a market-entry decision, a pricing question, an operations bottleneck. The interviewer plays the client and feeds you data only when you ask the right question, so the round is genuinely interactive rather than a monologue.

• Opening prompt a one or two line brief, often deliberately vague on scope.
• Clarification you confirm the objective, timeframe and success metric before diving in.
• Structure you lay out a MECE breakdown of what would drive the answer.
• Analysis you work through branches, request data, and do mental maths.
• Synthesis you close with a crisp recommendation, risks and next steps.

Interviewer-led firms (McKinsey style) steer you between prompts; candidate-led firms (Bain, BCG style) expect you to drive. Either way the interviewer is watching how you think, not whether you reach one magic number.

Most firms grade on a small set of dimensions that repeat across cases:

• Structure is your framework tailored to this problem and genuinely mutually exclusive, or a memorised template bolted on?
• Quantitative comfort can you set up a calculation, estimate cleanly, and sanity-check the order of magnitude without a calculator?
• Business judgement do your insights sound like they come from someone who understands how companies make money?
• Communication are you signposting, staying concise, and bringing the interviewer along?

A common failure is a beautiful structure followed by no insight. The strongest candidates keep asking so what does this mean for the client after every branch.

Prompt: a regional bakery chain has seen profit fall 15% over two years though revenue is flat. Diagnose why.

Weak start: jumping straight to cost-cutting ideas. That skips diagnosis and guesses at the answer.

Strong start: "Profit is revenue minus cost. Revenue is flat, so I'd first isolate whether the profit fall sits on the cost side, then within cost split fixed versus variable, then drill into the largest movers." You have just built a driver tree the interviewer can hang data on.

Suppose ingredient cost per unit rose while volumes held. You would quantify the impact, ask whether pricing could pass it through, and check customer sensitivity before recommending a selective price rise on low-elasticity lines plus supplier renegotiation. Note how the recommendation is specific, sized, and risk-aware rather than a generic "cut costs".

Weeks 1 to 2: drill the building blocks in isolation. Do 15 market-sizing questions (how many EV chargers does Pune need) and 20 quick mental-maths sets so arithmetic stops eating your working memory.

Week 3: full cases, one profitability, one market entry, one pricing, one operations. After each, write the driver tree you should have used and compare.

Week 4: rehearse out loud with a partner or a mock, because silent solving hides your worst habit, thinking without narrating.

A free AI voice mock interview from InterviewPrep is a low-stakes way to do that last step. It builds a case-style session from your CV and a target job description, then scores your answers, speaking pace and filler words, so you can hear where your structure wobbles before a real partner does.

A case is a two-way conversation, so a large part of your score comes from how you use the interviewer, not just how you solve. Treat every data point they offer as a signal about where the answer lies, and every raised eyebrow as a nudge to reconsider. Strong candidates check in without seeking approval: "I'll start with the cost side since revenue is flat, does that scope work for you?" This keeps you aligned and lets the interviewer redirect early rather than watching you go down a blind alley.

When you are handed a chart or table, pause and read it out loud before interpreting, name the axes, the units, the trend, then say what it implies for the client. Rushing to a number before understanding the exhibit is a classic error. If you get stuck, narrate your thinking rather than going silent; interviewers reward a candidate who reasons through uncertainty over one who freezes.

Watch your airtime too. Consultants have to be concise with busy clients, so keep each point tight, signpost with first, second, third, and resist the urge to over-explain. If you sense you are rambling, stop and synthesise. The habit to build is a rhythm of structure, analyse, so-what, check-in, repeated until you reach a recommendation, which keeps the interviewer engaged and confident in your judgement throughout.

Consultant openings are typically mirrored on Naukri Jobs within a day or two of appearing on firm careers sites, so setting alerts there is a low-effort way to see cases the moment they open.