This interview process was entirely remote.
The first round of interviews with Spotify started with your typical technical phone screen with an engineer. The engineer was courteous and let me work through the problem with only an occasional comment.
The next step was the longer, full-day virtual "on-site" which consisted of five interviews:
The process went smoothly with no technical hangups due to it being completely remote. Thankfully, the schedule also allowed for some breaks between interviews.
The algorithm questions were standard, involving arrays and strings. Nothing was too difficult or couldn't be trained for.
The debugging session was more of a collaborative whiteboarding session (shared screen on Google Hangouts), going through a scenario of figuring out why a service was having issues. The engineers running the interview would give a basic outline of the architecture, and you would need to ask for more information to get to the bottom of the issue.
The systems design question involved architecting a new feature for uploading photos to playlists.
The following metrics were computed from 2 interview experiences for the Spotify Backend Software Engineer role in United States.
Spotify's interview process for their Backend Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Spotify's Backend Software Engineer interview process in United States.