did the Perplexity TPM loop a couple months ago. there's almost nothing written about this role there so putting it out there.
i have 5 YOE in BizOps / TPM-adjacent work. recently moved fully into TPM at a Series B. took a shot at Perplexity because the company moves fast and i wanted to see if i could cut it at that level.
the process four rounds total after a recruiter call. fully virtual.
round 1, technical depth: this was harder than i expected for a TPM role. they asked me to describe a technically complex project i'd managed. not just the PM side (milestones, stakeholders) but what was technically hard and how i made decisions when engineers disagreed. they dug into the tradeoffs. my answer was a real-time data sync problem i'd worked on and i had to actually explain the consistency vs. availability tradeoff clearly. if you have a shallow technical vocabulary this round will be rough.
round 2, cross-functional coordination: scenario-based. "you're a TPM on a team where the ML team and the infra team both think the other is the bottleneck. how do you move this forward." they weren't looking for a magic process answer, they wanted to see if i'd go gather data first or assume.
round 3, prioritization and tradeoffs: classic but good. limited eng bandwidth, three competing requests from three internal teams, ship date is fixed. walk them through how you'd decide. i used a rough impact/effort matrix and they pushed back on my assumptions.
round 4, hiring-side/exec: 30 min, bigger-picture. what's the difference between a TPM at a startup and a FAANG. i said something like: at a startup the TPM often has to invent the process, not just run it. they seemed to like that.
overall: they want someone technical enough to hold engineers accountable and adaptive enough to work in a company that changes direction fast. the role is real, not just a project coordinator with a fancy title.
i got to final stage but they went with an internal candidate. still think it was a good process.