went through the Affirm TPM loop for a role on their payments infrastructure side. i've done TPM interviews at a handful of fintechs and this one was notably more technical than most.
the upfront context: affirm's TPM team is embedded across engineering and product. the expectation is that you can hold your own in an architecture conversation, not just track milestones. they said multiple times in recruiting that their TPMs "write PRDs, not just RAID logs."
loop structure: recruiter screen: 30 min. she asked about my experience owning cross-functional programs, specifically ones with compliance or regulatory milestones. fintech experience is valued but not required. technical screen: 45 min with a senior engineer. they gave me a system design scenario (something like: you're launching affirm checkout for a new merchant category with stricter data privacy requirements). they want to see you ask good clarifying questions, identify dependencies, and think about risk. it's a PM-flavored system design, not a SWE deep-dive, but you need to understand what an API gateway is. program management case: they gave me a scenario where an engineering team is blocked 6 weeks from launch. i had to walk through how i'd triage, escalate, and communicate. they pushed on specifics: what would you say to the VP? what slack message do you write? behavioral x2: standard STAR. big themes were influence without authority, managing ambiguity, and delivering hard news to stakeholders. hiring manager final: 30 min, more conversational. he was assessing culture fit and long-term growth trajectory.
things that helped: i referenced specific fintech compliance timelines (CFPB, SOC 2 windows) in my case answers and it clearly resonated. showing you understand why payment systems have hard launch deadlines matters here.
process took about 4 weeks. no BS, they moved fast once scheduling was sorted.