I'm a PM with 7 years in B2B SaaS who just went through KP's PM interview process for a senior product manager role on their digital experience side. The process is different enough from typical tech PM loops that it's worth writing up.
The structure: Recruiter screen (30 min): background, salary, motivation Hiring manager call (45 min): mostly behavioral, one product case question Written case study (sent home, ~1 week turnaround, 5-6 pages) Virtual panel onsite (4 rounds: product sense, strategy, execution, cross-functional leadership)
The written case study was the biggest surprise. They gave me a hypothetical: design a feature to improve medication adherence for chronic disease patients on KP's mobile app. I had to produce a mock PRD-style doc covering the problem definition, solution options, success metrics, and rollout plan. They want you to write it like a real PM would, not like a case interview answer.
Onsite questions I remember: How would you prioritize a backlog with 3 competing stakeholder groups and no clear revenue signal? Tell me about a product decision you made that turned out to be wrong. What did you learn? How would you measure the success of our member-facing health records feature? Give me an example of when you had to kill a project or feature you'd championed. What happened? Design a new feature for a KP member who was just diagnosed with Type 2 diabetes (product sense round)
The health literacy angle matters here. They asked me explicitly about designing for a diverse member base, including older adults, people with low digital literacy, and non-English speakers. That's not a question I've gotten in SaaS PM interviews.
The panel was a mix of PMs, engineers, and a clinical lead (yes, an actual clinician was on the panel). Be ready for that. The clinical perspective changes what matters in the room.