Operations Turnaround Cost Reduction Case round·Consulting·Hard·20 min

McKinsey EM Interview — Operations Turnaround Cost Reduction Case

20 min · 1 credit · scorecard at the end

Take this on a laptop or desktop — not your phone. The live interview needs a full screen and keyboard (including a sketch whiteboard on coding rounds). You can buy now, but start it from a computer.

Z
ZeroPitch Research Desk
Updated 2026-05-23 · Newly added · be among the first to take it
Field
Consulting
Company
McKinsey & Company
Role
Engagement Manager
Duration
20 min
Difficulty
Hard
Completions
New
Updated
2026-05-23

How to prepare

What this round tests, what strong and weak answers sound like, and the traps to sidestep.

What this round is about

  • Topic focus. A Krakow back-office shared-services unit of a global insurer must cut its unit cost base by one fifth in twelve months without breaking claims and policy SLAs, and you must decompose where the money actually sits before any lever is named.
  • Conversation dynamic. The Partner runs it interviewer-led, drops four to five exhibits verbally one slice at a time, introduces a constraint mid-case to test recalculation, and pushes back harder than an EM would.
  • What gets tested. Structural cost decomposition, impact-effort prioritisation tied to change-readiness, hundred-day sequencing, holding a position under pushback, and an opinion-led recommendation with the SLA risk named.
  • Round format. A single continuous case of roughly twenty minutes that escalates from cost structure to lever prioritisation to a pressured recommendation with sequencing, then a short judgement question.

What strong answers look like

  • Structural decomposition first. You split cost on fixed versus variable AND direct versus SG&A AND people versus non-people before any lever is named, then state which slice you suspect holds the largest addressable pool.
  • Impact-effort with change-readiness. You build an impact-versus-effort view that explicitly defers a high-impact lever because the organisation cannot absorb it in month one.
  • Sequenced hundred-day plan. You name no-regret moves in weeks one to four such as vendor renegotiation and demand management, span-of-control work in weeks five to eight, and structural moves later.
  • Opinion-led recommendation. You give the COO a headline savings number, the sequencing logic, the change cost in money, the SLA risk named specifically, and what you would validate in week one.

What weak answers look like (and how to avoid them)

  • Layoff-first thinking. Recommending a headcount cut before decomposing the cost base: pause and lay out the structural axes before any lever.
  • Flat lever list. Listing eight cost levers with no impact-effort view: rank them by impact and effort and call out change-readiness on each.
  • Bundled sequencing. Putting every lever into month one: defer at least one high-impact lever to month four with the change-readiness reason.
  • Capitulating under pushback. Folding when the Partner pushes back on your sequencing: hold the position with reasoning or recalculate transparently with the new constraint.

Pre-interview checklist (2 minutes before you start)

  • Recall the cost axes. Be ready to split cost on fixed versus variable, direct versus SG&A, and people versus non-people in one breath.
  • Have a lever taxonomy ready. Demand management, vendor consolidation, process automation, span-of-control, delayering, footprint, targeted headcount, in roughly that sequence by readiness.
  • Re-read the EBITDA bridge basics. Practise converting unit cost moves into run-rate savings and translating savings into a percentage of the base.
  • Pre-stage change-readiness language. Plan to name SLA risk and change cost explicitly in money, not as a footnote.
  • Pull up the hundred-day shape. Have the no-regret-then-structural sequencing pattern ready to deploy, not invent live.

How the AI behaves

  • Probes every claim. It asks for your structural axes and the change-readiness logic, not just the headline savings number.
  • No mid-interview praise. It will not say great answer or tell you how you are doing, exactly like a real Partner round.
  • Interrupts on layoff-first thinking and bundled sequencing. It cuts in when you reach for headcount before decomposing or bundle every lever into month one.
  • Drives the sequence and introduces a constraint mid-case. It drops exhibits one slice at a time and adds a layoff freeze or an SLA red line to test whether you recalculate or rationalise.

Common traps in this type of round

  • Layoff-first reflex. Reaching for a twenty percent headcount cut in month one before any structural decomposition.
  • Single-axis cost tree. Splitting cost only on direct versus SG&A and missing fixed versus variable or people versus non-people.
  • Change-management as footnote. Mentioning change risk once at the end rather than building it into the sequencing logic.
  • Bundled sequencing. Putting every lever into month one because they all look attractive on impact-effort.
  • Capitulating under pushback. Folding the moment the Partner pushes on a defensible position rather than holding or recalculating.
  • Vague recommendation. Closing with a directional statement rather than a quantified opinion with sequencing, change cost and SLA risk named.
Reference

The full breakdown

How you're scored, the questions candidates ask most, and the research this interview is built on. Skim it — or just start the interview.

Interview framework

You will be scored on these 6 dimensions. The full rubric with definitions is below.

Structural Cost Decomposition
Whether you split the cost base on at least two structural axes such as fixed versus variable and direct versus SG&A before naming any lever.
20%
Impact-effort Prioritisation
Whether you rank levers on impact and effort and embed change-management readiness as a sequencing input.
15%
Hundred-day Sequencing
Whether you sequence no-regret moves early and defer structural moves with a named change-readiness reason.
20%
Judgement Under Pushback
Whether you hold a defended position when the Partner pushes back and recalculate transparently under new constraints.
15%
Opinion-led Synthesis
Whether you close with a quantified opinion-led recommendation naming the headline savings, the change cost in money and the SLA risk.
20%
Case Math On The Ebitda Bridge
Whether you convert unit cost moves into run-rate savings and reconcile to the twenty percent target out loud.
10%

What we evaluate

Your final scorecard breaks down across these dimensions. The full rubric and tier criteria are revealed inside the interview itself.

  • Structural Cost Decomposition Rigor20%
  • Impact-Effort Prioritisation With Change Readiness17%
  • Hundred-Day Sequencing Discipline18%
  • Judgement Under Partner Pushback15%
  • Opinion-Led Synthesis With Named Risk20%
  • EBITDA Bridge Case Math Discipline10%

Common questions

What does the McKinsey Engagement Manager Partner-round operations turnaround case actually test?
It tests whether you can think like a future Partner on a cost-reduction turnaround under ambiguity, not whether you can recite a cost tree. The Partner judges five things: a structural decomposition of the cost base into fixed versus variable and direct versus SG&A before naming any lever, an impact-effort prioritisation that explicitly accounts for change-management readiness, a hundred-day plan with no-regret moves early and structural moves sequenced later, holding a position when you are pushed back on a hard trade-off, and a crisp recommendation that names the SLA risk and the change cost in numbers not platitudes. It is an opinion-led round, not an analysis round.
How should I structure the cost base before discussing levers?
Take up to a minute, then present a structural decomposition in about forty-five seconds. Split the cost base on at least two axes: fixed versus variable so you can see what scales with volume, and direct versus SG&A so you can see what touches the customer versus overhead. Then split each by people versus non-people, because in a back-office shared service centre people cost is usually the largest single line. State which slice you suspect holds the largest addressable pool and ask for the cost waterfall that confirms it. The Partner is listening for the structural axes before any lever, not a recited cost tree.
Why is jumping to headcount reduction a red flag in this round?
Because it signals you have never actually run a turnaround. A twenty percent headcount cut in month one without decomposing the cost base typically destroys SLAs, triggers regulatory escalation in regulated industries like insurance, and the political cost can swamp the savings. Partners want to see you treat headcount as one lever among several, sequenced after process automation, vendor consolidation, span-of-control and demand-management moves have done their work. Naming the change-management cost of badly sequenced layoffs as a real risk is one of the strongest positive signals in this round.
What does a hundred-day plan look like for this case?
It sequences levers by impact, effort and change-readiness rather than bundling them all into month one. Weeks one to four are no-regret moves: vendor contract renegotiation, demand management on low-value reports, capacity-utilisation quick wins, and the baseline cost waterfall itself. Weeks five to eight are span-of-control and delayering moves where evidence is already strong. Weeks nine to twelve open the structural workstreams: process automation pilots, offshoring or footprint changes, and only then the targeted headcount actions tied to redesigned processes. The Partner rewards a sequence that defers a high-impact lever explicitly because the organisation cannot absorb it yet.
How is the Partner round different from a first-round case at McKinsey?
First-round cases test structuring, math and exhibit reading; Partner rounds test judgement under ambiguity. The Partner will not tell you which branch matters, will push back harder on every assumption, will introduce a constraint mid-case to see if you recalculate or rationalise, and will ask you for an opinion you have to hold. EM-track candidates are expected to think like a future Partner, which means an opinion-led recommendation rather than a flat lever list. The Partner round is also the gate to an offer at the EM level.
How is this AI interviewer different from a real McKinsey Partner?
It behaves like a Partner-round operations interviewer: opinion-led, harder pushback than an EM would deliver, drip-feeds exhibits verbally one slice at a time, and introduces a constraint mid-case to test whether you recalculate or rationalise. It never praises mid-case and never tells you how you are doing, exactly like a real Partner. The differences are that it is available on demand, it stays perfectly consistent across attempts, and it produces a transcript-backed scorecard naming the precise turn where your sequencing or your structural decomposition broke, which a human Partner rarely gives you in that detail.
How is the scoring done in this mock interview?
Your transcript is scored against six EM-level dimensions: structural cost decomposition before levers, impact-effort prioritisation tied to change-readiness, hundred-day sequencing with no-regret moves early, holding a position under Partner pushback, opinion-led synthesis with the SLA and change cost named in numbers, and case math discipline on the EBITDA bridge. Each dimension has observable signals quoted from your turns. You get a scorecard that names the precise moment your sequencing went flat or your structure collapsed, so the feedback is concrete rather than a vague rating.
What should I do in the first three minutes of this case?
Listen to the full prompt, then take up to a minute of structuring time and use it. Confirm the goal and the constraint in one line, namely twenty percent cost reduction in twelve months without breaking SLAs. Decide your structural axes before any lever, present the decomposition in about forty-five seconds naming fixed versus variable and direct versus SG&A and people versus non-people, then state which slice you suspect holds the largest addressable pool and ask for the cost waterfall that tests it. Driving from turn one signals you can run a workstream as an Engagement Manager.
How do I handle the Partner pushing back on a position I have taken?
Hold the position calmly if your reasoning is sound, and recalculate transparently if the new information changes the answer. Partners are not testing whether you fold; they are testing whether you have judgement under pressure. If they introduce a constraint such as a freeze on layoffs for six months, recompute the achievable savings out loud, name what you would now defer, and state the residual gap. If they push on your sequencing, defend it with the change-readiness logic. Capitulating under pressure is a stronger negative signal at EM level than the original answer being slightly off.
What does a strong recommendation sound like in the close?
It is opinion-led and quantified. Lead with the headline number, for example we can deliver around sixteen percent run-rate savings in twelve months by sequencing vendor and demand levers in months one to three, span-of-control and process automation in months four to eight, and targeted role consolidation in months nine to twelve, holding the residual four percent for year two because the organisation cannot absorb deeper cuts without breaking claims SLAs. Name the change cost in money, name the SLA risk specifically, and state the one thing you would validate in week one. Vague recommendations fail this round.
Is this Partner round candidate-led or interviewer-led?
McKinsey Partner rounds at EM level are interviewer-led but the Partner expects the candidate to take ownership of the agenda within the structure. The Partner drives the question sequence and drops exhibits one at a time verbally, but expects the candidate to state hypotheses, ask for the specific data that tests them, and propose the sequencing rather than waiting to be walked. Practically this means you present a tight structural decomposition, state a hypothesis on where the addressable pool sits, then ask for the exhibit that confirms or kills it. Passive driving is a fail at this seniority.
Who is the interviewer persona in this McKinsey EM Partner-round practice?
You speak with Sandeep Talwar, a fictional Senior Partner in McKinsey's Operations practice based in London who has personally led seven to ten operational turnarounds across European manufacturing, African mining and Indian back-office services. He is measured at the open and pushes hard from minute three, drip-feeds exhibits verbally, and never tells you how you are doing. He is designed to mirror how a real Partner-round operations interviewer at this seniority actually behaves with an EM-track experienced hire, including the silences when he wants you to fill the air.

Sources this interview is built on

Real candidate-report URLs (Glassdoor / AmbitionBox / PrepInsta / GeeksforGeeks / Medium) reviewed when authoring the questions, persona, and rubric. Verify the realism yourself.