Did the Twilio TPM loop in January 2026. Five rounds, roughly three weeks total. Sharing because when I searched for TPM-specific Twilio prep, I got almost nothing useful.
First: this is actually a technical role at Twilio. They're not looking for project managers who schedule standups. They want people who can read a technical design doc, identify risks, and drive cross-team coordination on complex API infrastructure. Know the difference going in.
Technical screen (60 min). One of their senior engineers. They walked me through a scenario: a product team wants to launch a new Twilio feature but it requires changes to the core messaging API that three other teams depend on. How do you manage this? We talked through dependency mapping, API versioning strategy, risk signaling to leadership, and rollback planning. Not coding, but genuinely technical.
Program execution round. A case-study style interview. Given a scenario with a slipping timeline and a vendor integration that isn't ready. How do you triage, communicate, and make tradeoffs. Be specific. They don't want "I'd hold a meeting." They want to hear the actual decision framework.
Cross-functional leadership round. Two questions about working with engineering leads who have competing priorities. Classic TPM territory. I talked about a time I had to negotiate scope with four different teams and how I built alignment without formal authority.
Hiring manager + culture round. Why Twilio. What do you know about developer experience programs. How do you stay current technically without coding full-time. Don't wing the "why Twilio" question, they'll notice.
Skip-level conversation. Director-level. Shorter (30 min), more conversational. They were checking whether I could communicate up effectively and whether I'd fit in terms of communication style.
Comp for senior TPM in SF: my offer was base around $185k, RSUs over four years, bonus target 15%. Industry middle. Not FAANG-level but the scope and product complexity were genuine.