Notion · Primly Community

Notion technical program manager (TPM) interview: what I learned going through it in 2026

intl_isla · 5 replies

Completed Notion's TPM interview process last quarter and wanted to share the breakdown. I'm a PM with a technical background, coming from a SaaS company in the UK, applying for a remote-eligible role. The process was a bit unusual compared to other TPM loops I'd been through.

First thing: Notion doesn't seem to have a huge TPM function. The team is lean and the roles are broad. If you're used to a PM-heavy environment where TPMs are basically project coordinators, recalibrate. Here it looked more like TPMs are expected to drive roadmap conversations with a lot of autonomy.

Process overview:

Recruiter screen, then a 45-minute hiring manager call (this one was pretty substantive, not just a vibe check), then a virtual onsite with 4 rounds.

HM call (45 min): He asked me to walk through a program I'd managed end-to-end, specifically where I had to make a technical tradeoff call. He pushed on the tradeoff itself: what were the options, how did I evaluate them, what did I give up. He was clearly checking whether I had genuine technical depth or was going to need to rely on eng to make every call.

Virtual onsite:

Round 1: Technical problem solving (60 min). Not coding. More of a structured technical discussion. I was given a scenario about a feature rollout that was hitting performance issues post-launch and asked to walk through how I'd diagnose and fix it. They wanted me to name specific hypotheses and explain how I'd test each one.

Round 2: Cross-functional collaboration (60 min). Classic TPM territory. How do you manage a deadline when two teams have conflicting priorities? How do you handle a situation where eng thinks the PM's requirements are technically infeasible? I got really specific situations, not vague generalities.

Round 3: Program design (60 min). Design a program for shipping a major API change across 6 product teams. This one was interesting. I had to think about dependency mapping, stakeholder comms, rollback strategy, and how I'd measure success. It felt like a real program they might have run.

Round 4: Executive presence (45 min). Someone senior who basically stress-tested whether I could hold my own in a room with VPs. They gave me pushback on my answers to see if I'd fold or hold my ground. I held my ground on two things and walked back one when they made a valid point. I think that balance was the right call.

Overall: more rigorous than I expected. They're looking for someone who can operate with minimal structure. If you need a lot of process scaffolding you'll struggle here. But if you're comfortable owning outcomes in an ambiguous environment it's a good fit.

Oh, and one thing: they asked me how I actually use Notion and what I'd change. Have a real answer to that. Not a diplomatic non-answer.

5 replies

jordan_pm

The executive presence round is something I've only seen at certain companies. Most TPM loops skip it. The 'hold your ground vs walk back' dynamic is actually a great skill to have ready: know which things you'll defend and which things you'll concede based on new information, not based on who's pushing back.

consultant_cam

Program design questions are case-style if you squint. The structure I'd use: clarify scope, identify stakeholders and dependencies, define success metrics upfront, then walk through the phases. Sounds obvious but most people skip the success metrics step and it shows.

intl_isla

That's exactly what I did and I think it helped. I framed it almost like a mini project kickoff. The rollback strategy piece is where I added something extra that they seemed to appreciate since most candidates apparently don't go there.

apm_aisha

Is this the TPM role or more of a PM-with-technical-depth role? I ask because the lines feel blurry in the description. Are they actually calling it TPM or something else?

sam_recovering

The 'how do you actually use Notion' question is so Notion. I've heard of other companies doing this too, like asking Figma candidates how they use Figma in their own work. Makes sense but you have to actually have an answer that's real, not rehearsed.