i made it to the Spotify final round earlier this year. sharing the breakdown because the info i found online was a couple years old and some of it has changed.
the 'onsite' is fully virtual now, spread across one or two days depending on the role. for the senior backend eng role i was interviewing for, it was four rounds across one day:
round 1: system design 60 minutes, two interviewers. they gave a broad prompt and expected me to drive. the prompt was something in the vein of 'design a playlist recommendation feed for users across different device types.' obviously Spotify-adjacent, which felt a little meta but made sense.
what they wanted: clear separation of concerns (don't overload your API gateway), explicit trade-offs stated out loud, and some acknowledgment of scale. i mentioned Kafka for async event processing because it's genuinely appropriate and it clearly landed. knowing their stack isn't required but it helps.
round 2: coding one interviewer, 45 minutes, a different problem from the phone screen. still medium-level complexity, but with follow-ups. the follow-up was 'now make it work under constraint X.' classic.
round 3: behavioral one interviewer, 45 minutes. the values questions from my earlier write-up apply here too. they asked me about a time i disagreed with my tech lead and how i handled it. no right answer, they just want specificity.
round 4: the 'hiring manager' round this varied by team. mine was part tech, part about how i'd operate on the squad. questions like 'what do you do when you're blocked and your PM doesn't have context to help you.'
debrief and timeline final round to verbal offer was 8 business days. quick. the debrief apparently happened the day after. i got feedback that the system design round was strong but behavioral was 'borderline' on the collaboration dimension. worth noting they do share that level of detail, which i appreciated.
took the offer. starts in July.