Went through the Spotify TPM interview earlier this year. Didn't take the offer (accepted elsewhere) but the process was thorough enough that I figured I'd write it up.
Background: 8 years in tech, last 4 as a TPM. Previous role was at a mid-size infrastructure company. Spotify's TPM roles sit in the backend/platform orgs mostly, from what I could tell.
Process: Recruiter screen (30 min), hiring manager intro (45 min), 4-round onsite.
Onsite rounds: Technical depth: They asked me to describe a complex distributed systems project I'd driven. Not what I did as PM/TPM, but what the system actually did. How it failed. What the failure modes were. They pushed on specifics. If you can't explain the system you drove at a fairly deep level, this round hurts. Program management: Classic TPM questions. How do you track dependencies across teams? How do you handle a schedule slip that's going to affect a customer commitment? One question I got: "Three teams all need to release changes in the same deployment window. Two of them have a hard dependency. One of them just told you their feature won't be ready. Walk me through what you do." This is a real question, not a gotcha. Just think aloud and don't skip the communication steps. Behavioral / leadership principles: Spotify's Band values again. Emphasis on how you handle ambiguity, how you work without authority. They want to see you've actually moved something difficult without being the one with the title. Cross-functional with PM and Eng director: Largely a "would we want to work with you" round. They described a real ongoing initiative and asked how I'd approach getting it unstuck.
Comp: For a senior TPM in Stockholm my offer was around 900k SEK base. NYC would be higher. Not my intended location so I don't have NYC specifics.
The technical bar is real. Don't apply if you've been a glorified project manager. They want someone who can actually go toe-to-toe with an L5/L6 engineer.