What the interview tests
You are typically given a business problem and expected to lead the discussion independently. The interviewer can share information when you ask for it, but ownership stays with you. The strongest performances combine management-consulting rigour with operator judgement: structured enough to isolate the cause, practical enough to act on it.
A strong problem-solving arc
1. Clarify the objective
Define the outcome, metric, timeline and any ambiguous terms. A precise problem statement prevents you from solving the wrong issue.
2. Build a diagnostic structure
Break the problem into relevant segments, levers or funnel stages. State what you need to learn and why, rather than listing a memorised framework.
3. Use data to update your view
Request information deliberately, interpret it aloud and eliminate hypotheses. Keep synthesising what the evidence means for the next question.
4. Solve the root cause
Move to solutions only when the diagnosis is strong enough. Recommend a small number of targeted actions and prioritise them by impact, speed and feasibility.
5. Show implementation judgement
Consider commercial impact, user experience, technical implications, dependencies, risks and how you would measure whether the action worked.
Common failure patterns
- Producing a generic issue tree without a clear hypothesis or purpose.
- Asking broad questions and expecting the interviewer to decide where to go next.
- Jumping to solutions before validating the root cause.
- Generating ideas without prioritisation, economics or implementation detail.
- Failing to synthesise what the data changed.
How the coaching session works
You lead a complete original case under interview conditions. The debrief focuses on the few behaviours most likely to change your result: how you frame the problem, direct the analysis, handle numbers, synthesise, prioritise and translate insight into action. You leave with specific practice priorities rather than a generic scorecard.