Okay. Did this loop in Q1 2026 and it was more involved than I expected. Sharing the full breakdown.
Okta's TPM team is split a few ways: some TPMs are embedded with product engineering, some are on Identity Governance, some are on the enterprise side dealing with customer-facing integration complexity. The role I interviewed for was product-adjacent, supporting their Identity Engine migration. If that means nothing to you: they're migrating customers off a legacy auth platform to a newer architecture, and it is a multi-year program with hundreds of enterprise customers. Classic large-scale technical migration program.
Recruiter screen: Standard 30 min. They wanted to know if I had any identity or security domain background (I don't, they said it wasn't required but clearly a plus). They also asked about my experience driving cross-functional programs at scale. They use that phrase specifically.
Hiring manager screen (45 min): This was meaty. It was almost a mini-behavioral interview. Tell me about a program you ran end-to-end with ambiguous requirements. How do you handle scope creep when multiple stakeholders have conflicting definitions of done? What does your status reporting look like on a program with ten plus engineering workstreams?
Technical depth interview (60 min): This is the one TPM candidates underestimate. They asked me to walk through how OAuth 2.0 and OIDC work at a high level. Not to implement it, but to show I understood the handshake well enough to have meaningful conversations with engineers. They also talked through a scenario: a customer's SSO integration breaks after a release, walk me through how you'd triage it. Expect to talk about token lifetimes, redirect URIs, scopes. It's not a systems design interview but it's not purely behavioral either.
Cross-functional simulation (45 min): They gave me a scenario: you're managing a migration of an enterprise customer from Okta Classic to Identity Engine, the customer has a hard deadline and your engineering team just told you you're 3 weeks behind. What do you do. I had to talk through stakeholder communication, risk framing, de-scope options, escalation path. Two interviewers role-played as the engineering lead and the customer success manager.
Behavioral (60 min, four questions): Lots of influence-without-authority scenarios. How do you get engineers to prioritize your program work over their team's own roadmap? Tell me about a time you had to deliver bad news to an executive.
Total time was about 6 weeks. The technical bar for the TPM role is higher than I've seen elsewhere, which makes sense given their product complexity. Offer was strong on base, lighter on RSU relative to a few other offers I had.