McKinsey · Primly Community

McKinsey product manager interview questions: what to actually prep

jordan_pm · 5 replies

I went through McKinsey's PM loop for a role on their Lilli product team (their internal AI assistant) earlier this year. Here's what the interview actually looked like, not the generic 'design a product for X' stuff you'll read elsewhere.

Background: I'm a senior PM with seven years in B2B SaaS. McKinsey's PM hiring is pretty specific: they want people comfortable working inside a consulting context, where 'the user' is often a consultant, and where speed and trust are everything.

The loop: recruiter screen, one PM skills round, one strategic round, one behavioral, and a final with a partner. Four rounds total, spread over about three weeks.

PM skills round: this felt closest to a traditional PM interview. Questions included: 'How would you prioritize features for an internal tool where you have direct feedback from 1,000 consultants but you also have leadership asking for enterprise features?' 'Tell me about a product decision you made with incomplete data.' They pushed on what 'incomplete' meant and how I weighted the gaps. 'How do you measure success for a feature that's hard to A/B test?'

Notably: no 'how many golf balls fit in a school bus' type questions. They're not doing estimation puzzles.

Strategic round: more about external context. Where do you see AI impacting professional services over the next three years? What's the risk McKinsey's internal tools team faces from external vendors? They want to see that you can zoom out.

Behavioral: standard STAR. Very similar to what consultant_cam wrote in the other thread here: influence, failure, data-driven decisions.

Comp: the PM offer I got was in the $180K-$210K range depending on level, with a performance bonus structure that's different from typical SaaS PM comps. No RSUs in the traditional sense since it's a private partnership.

The culture was collegial, high-trust. They move fast if you're in the funnel. The Lilli team in particular felt like a startup inside a large institution, which suited me.

5 replies

apm_aisha

The prioritization question about internal users vs. leadership pressure is such a hard one to answer well. Did you use any specific framework or just walk through your thinking?

jordan_pm

I walked through my thinking rather than naming a framework. I basically said: I'd segment the consultant requests by frequency and severity, then put the leadership asks through the same lens. Anything that served both groups went to the top. They seemed to care more that I could think out loud than that I cited Impact/Effort matrices.

ux_uma

Do you know if there's a design or research round for PM roles there, or is it all verbal discussion? I've seen some PM loops that include a portfolio or case presentation.

ops_omar

The no-RSU structure is worth flagging more prominently. I've seen people assume MBB roles carry equity similar to tech and then be surprised at offer time. The comp philosophy is genuinely different.

careerveteran

The Lilli team detail is useful context. McKinsey's internal tech org has gotten a lot more product-driven in the last two years as they've tried to differentiate on proprietary tooling rather than just headcount. It's a real PM environment now, not an IT backwater.