Went through Zoom's TPM interview earlier this year. This role sits at the intersection of program management and technical depth, and their loop reflects that. Sharing the breakdown for anyone prepping.
Loop: recruiter screen, hiring manager call, then four rounds in a virtual onsite. Total loop was about 5 weeks start to finish.
Recruiter screen: background check, comp alignment (they share a range early, which is nice), basic "why Zoom" question. The recruiter asked specifically about experience coordinating cross-functional engineering programs at scale. Scope matters here: they're not looking for project managers who use Jira, they want program-level thinking.
HM call: the meat of early-stage screening. My HM asked me to walk through the largest cross-functional program I'd ever run: how I structured milestones, how I managed dependency risk, how I handled slippage when an eng team was blocked on an external API. He kept asking "what would you have done differently." Have a real answer to that.
Onsite round 1: Technical depth. They asked me to walk through how Zoom's client-server architecture works at a high level and identify where a TPM should focus during a major feature launch. No coding, but they want you to understand things like latency, WebRTC basics, how media processing pipelines work. If you're a pure program manager with no technical background this round will be rough.
Onsite round 2: Program execution. Walk through a program you ran that hit a significant risk event. How did you identify it, escalate it, resolve it. They like concrete timelines and actual outcomes.
Onsite round 3: Cross-functional leadership. Basically: how do you work with eng, PM, and leadership simultaneously when priorities conflict? I got a scenario question: two VP-level stakeholders disagree on a feature priority that's blocking your program. Walk me through it. This is not a "correct answer" question, they want to see how you think.
Onsite round 4: Behavioral. STAR method, 4-5 questions, heavier on leadership and influence-without-authority themes.
The technical depth requirement surprised me relative to TPM roles elsewhere. If you're coming from a pure PM or non-technical background, prep at least one layer deeper on networking and distributed systems basics.