did the Block TPM interview loop last quarter. i'm not going to sugarcoat it: the TPM bar at Block is legitimately high and some of the questions blindsided me.
background: i'm a senior TPM with 8 YOE, mostly infrastructure and platform work. applied for a TPM role on the Square developer platform team.
phone screen (45 min) technical depth check immediately. the recruiter said "the hiring manager wants to calibrate your backend systems understanding before investing in an onsite." they asked me to walk through how i'd approach launching a new API endpoint to external developers: versioning, backward compatibility, rollout strategy, monitoring. this was not a behavioral question.
they also asked one operational question: "a developer reports our API has 3x latency spikes on monday mornings. walk me through your triage plan." this is pure TPM territory: who do you pull in, what do you look at first, how do you communicate to external partners while you're still investigating.
onsite (5 rounds) technical systems: design a developer webhook system. reliability, ordering guarantees, retry semantics, scaling. i had to talk about at-least-once vs. at-most-once delivery and when each matters for financial webhooks. program execution: describe a complex multi-team program you drove end-to-end. they pushed on dependencies, what slipped and why, how you handled it. concrete details required. cross-functional influence: "how do you get alignment when two engineering teams have conflicting priorities and you don't have authority over either?" this is a core TPM question and they want real tactics, not "i facilitated a discussion." metrics and data: given a drop in payment success rate on a specific merchant segment, how would you triage? this is where data fluency matters. you should know basic SQL concepts even as a TPM at block. stakeholder communication: given a regulatory deadline in 6 weeks with scope that takes 10 weeks at current pace, how do you present options to leadership? this is judgment, not template.
they want TPMs who are technically credible enough to talk to engineers without a translator. if you've coasted on being a "connector," this loop will be uncomfortable. in a good way, probably.