Software Engineer II applicants have rated the interview process at Spotify with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 47.2% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer II roles take an average of 52 days to get hired, when considering 3 user submitted interviews for this role. To compare, the hiring process at Spotify overall takes an average of 39 days.
Common stages of the interview process at Spotify as a Software Engineer II according to 3 Glassdoor interviews include:
Phone interview: 20%
Group panel interview: 20%
Personality test: 20%
One on one interview: 20%
Skills test: 20%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 weeks. I interviewed at Spotify (Stockholm, Stockholm)
Interview
It was a fairly long process, but not particularly hard. Had a recruiter screening, a technical interview (LeetCode Easy), then a day with 4x 1hr interviews. These were values, system design, case study (bug finding session), and technical programming (LeetCode Medium). Then it was a placement meeting, and an offer call. Any decent engineer should be able to do it in my eyes.
Interview questions [1]
Question 1
Find the indices in an array of two non-negative numbers that add up to a third number. Analyze and optimize it.
I applied online. I interviewed at Spotify (New York, NY)
Interview
Phone screen, coding interview/backend specific questions, then a 5 hour long interview session of -
1. coding interview
2. case study
3. system design
4. behavioral/values
Overall had a good experience, the interviewers were all very friendly and the questions were fair.
Interview questions [1]
Question 1
Q: design a system that allows Spotify users to add a custom picture to their playlist. other users should be able to view this picture as well, but only the owner of the playlist can edit the picture
Recruiter screen. Tech Screen.
On-site in four parts.
* Algorithms
* Architecture
* Management / Team
* Incident roleplay
The incident section was really good, very enjoyable.
I absolutely bombed the architecture section because I got stuck on the question of "how would you measure this thing?"
Interview questions [1]
Question 1
Describe a time you had to deal with a conflict in your team?