Notion · Primly Community

Notion product manager interview questions: what they test across the full PM loop

pm_priya · 5 replies

Went through Notion's PM interview process in Q1 2026 for a senior PM role. Posting because the PM loop was different enough from my previous Meta and Figma interviews that I had to recalibrate my prep.

The loop structure (for a senior PM). Recruiter screen, one PM portfolio/background round, one product sense round, one metrics/analytical round, and a cross-functional panel. I did not get a written case or take-home.

Portfolio round. More like a career conversation. They wanted to hear about a product I'd owned end-to-end and go deep. Not a quick two-minute answer. They pushed on: how did you decide what to build first, what did you get wrong in your initial assumptions, and how did you update the roadmap based on what you learned. Having a tight product narrative for 1-2 things you've built matters a lot here.

Product sense round. This is where it felt distinctly Notion. The question wasn't "design a new feature for Spotify." I was asked to think about a real problem Notion users face and how I'd approach it. The interviewer had clear opinions and pushed back. It wasn't a case where any coherent answer was good. They wanted to see if my instincts aligned with their taste on what a product should do and not do. Research Notion's actual design philosophy before this round.

Metrics round. Standard PM metrics interview structure. Define success, pick a north star metric, diagnose a drop. They did ask about an A/B testing scenario. If you know your stats basics you're fine.

What I'd tell other PMs. Use Notion heavily before your loop. Know what decisions they've made that other products haven't. Be ready to defend your product opinions, not just describe them. And nail the "what would you NOT build" framing. I heard it in three different rounds in different forms.

5 replies

apm_aisha

The product sense round sounds genuinely hard. How deep into Notion's actual product did you go in your prep? Like, were you using it daily for weeks before or more like a focused review of their design decisions?

pm_priya

Both. I'd used it for work for a year already, but two weeks before the loop I did a more focused audit. I read their public changelogs, watched some of Ivan's old talks on product philosophy, and wrote down 5 decisions Notion made that I found interesting or surprising. That exercise is what gave me material to pull from in the interview.

jordan_pm

The no take-home thing is interesting. A lot of companies have been moving to take-homes for PM loops because the in-person product sense rounds are noisy. I wonder if Notion gets more signal from the live conversation on purpose.

growth_gabe

"What would you NOT build" is basically Notion's version of the product-sense filter. The answer reveals whether you understand their philosophy or whether you just have good product instincts in general. Two very different things for this specific company.

intl_isla

Did they test for technical depth at all for the PM role? Some companies that build developer/power-user products expect their PMs to have a higher technical baseline.