hat I learned prepping for a McKinsey Engagement Manager interview as someone with a technical background

I spent most of my career thinking McKinsey was for MBAs and econ majors. Then a colleague with a CS background made EM and I realised I'd been wrong about the whole thing.
McKinsey actively recruits technically strong people into Engagement Manager roles — and if you have a background in engineering, product, or data, you actually walk in with some real advantages. You can structure complex problems, you're comfortable with ambiguity, and you can cut through vague client requirements faster than most.
But the interview process will still humble you if you go in unprepared. Here's what the EM process actually tests that most technical candidates underestimate:
It's not just case interviews
Most people overprepare the case and underinvest in the Personal Impact Interview (PII). At EM level, McKinsey wants evidence that you've led teams, influenced stakeholders, and driven outcomes — not just solved problems. If your stories are technically impressive but passive ("we built the system that..."), they won't land. You need to show what you specifically decided, changed, or pushed through.
The cases test judgement, not just structure
EM-level cases are less "how many piano tuners are in Chicago" and more "here's a messy enterprise situation with incomplete data and competing priorities — what do you do?" They're evaluating whether you can think like someone who runs client engagements, not just analyse them. Engineers tend to go deep fast — which can actually work against you if you don't zoom out to the business framing first.
They're looking for entrepreneurial drive
This one surprised me. McKinsey EMs are expected to build the business, not just deliver projects. Your stories should show moments where you went beyond the brief — proposed something no one asked for, spotted an opportunity, or changed a direction based on your own initiative.
Technical background is an asset if you position it right
Framing matters a lot. "I built an ML pipeline" is a project update. "I saw that the analytics team was making decisions on stale data and proposed — then led — a shift to real-time scoring that changed how the business priced risk" is an EM-level story. Same underlying work, completely different framing.
If you're exploring this path and want a structured breakdown of the full interview process — what each round tests, how to prep your leadership narratives, and what good looks like at EM level — I've left a link in the comments.
Happy to answer questions from anyone in tech thinking about consulting transitions — it's a weirder and more navigable path than most people assume.
Full McKinsey EM interview guide here — covers the PII, case format, what they're evaluating at this level, and how to structure your prep:
https://interviewbee.ai/resources/interview-guide/mckinsey/engagement-manager