just finished the figma TPM process. sharing the full breakdown because there's basically nothing out there about what the figma technical program manager interview actually looks like versus their PM or SWE loops.
quick context on me: 7 YOE in B2B SaaS, 4 years as a PM, 3 as a TPM at a mid-stage company. applied for a senior TPM role on their platform/infrastructure side.
the process (start to finish: 5.5 weeks): recruiter screen (30 min) hiring manager screen (45 min) technical screen with an eng lead (60 min) virtual onsite: 5 rounds over one day
hiring manager screen: pretty conversational. they want to understand how you think about program scope vs. project execution. the question that caught me off guard: 'what's the difference between a program and a project and how does that change your role?' not a gotcha, just figuring out whether you operate at the right altitude.
technical screen: this was with a senior eng, not a PM. they asked me to walk through how i'd break down a cross-team infrastructure migration into phases, identify dependencies, and communicate risk. no coding, but the conversation was technical enough that if you don't understand eng concepts you'd struggle. know the difference between parallelizable work and sequential blockers. they probed on how i'd work with eng leads who disagree on the sequencing.
onsite round breakdown: program design (60 min): given a scenario: figma is launching a major API versioning overhaul that affects 100+ third-party plugin developers. design the rollout program. this was the hardest and most interesting round. they want: stakeholder map, milestone structure, developer communication plan, risk flags. bring structure but don't be so rigid you miss the human side of external developer relations. technical depth (45 min): how do you work with eng on a systems decision you don't fully understand? they gave me a scenario where two teams disagreed on sync architecture for a new real-time feature. they want to see how you facilitate without pretending to be the technical decision-maker. cross-functional influence (45 min): behavioral round focused on how you've worked across design, eng, and product without direct authority. figma has strong opinions about design culture. answers that treat design as a downstream stakeholder (not a co-equal partner) don't land. leadership/bar-raiser equivalent (45 min): a director-level interviewer. questions about how you've handled programs that went sideways, how you communicate bad news upward. they want specificity, not generalities. values/culture (30 min): shorter, more conversational. mostly about why figma, what kind of environment you do your best work in.
overall read: figma TPMs are expected to be technical enough to earn credibility with eng, structured enough to run complex cross-team programs, and humble enough to work in a very design-led culture. the plugin ecosystem program design question was the biggest differentiator because it combined all three.
offer comp: $215k base, $220k RSU 4-year, senior level. SF but negotiated remote. worth the process.