Software Engineer applicants have rated the interview process at Spotify with 3.1 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 46% positive. To compare, the company-average is 47.4% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 29 days to get hired, when considering 72 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 according to 72 Glassdoor interviews include:
Phone interview: 34%
One on one interview: 21%
Skills test: 13%
Presentation: 10%
Group panel interview: 9%
Other: 3%
Background check: 2%
IQ intelligence test: 2%
Drug test: 2%
Personality test: 2%
Here are the most commonly searched roles for interview reports -
Background and work related questions followed by coding portion.
The coding portion I solved using a fixed size array that wrapped around. The interviewer was adamant that the performance was O(n), but it was O(1) because it wrapped around with a running index.
He later agreed with me after realizing he was wrong and ran some tests.
He asked me to change it to what he wanted which was a growing linked list up to size n instead. His reasoning was that an array was too big to allocate for and the linked list was better.
I went with his "desired" and "correct" solution.
In my head, I'm thinking: "Hold on now. You're telling me to grow a linked list up to size n instead of a fixed array of size n? you didn't specify that we were running multiple instances and can't expect size n for every instance..."
I guess it was not clear to me that he had a specific use scenario in mind when he asked the question.
I did not pass because I did not conform to the answer he knew.
Interview questions [1]
Question 1
Tell me about some of the technologies you've used?
One of the most disrespectful interview processes I've ever been a part of. First stage was a call with a recruiter, which went fine although there was more than a whiff of wannabe silicon valley waffle from his end.
I progressed and was booked in for a 2nd stage with an engineer. However on the day of the interview it was cancelled as I was told there were scheduling conflicts. Ok fine, it happens. The interview was rearranged for the following week - when the same thing happened again! Interview cancelled on the day due to scheduling conflicts. Booked in again for the following week (third time lucky?) and this time it wasn't cancelled on the day. BUT I joined the call and no-one showed up! After 10-15 minutes I emailed the recruiter who told me the interviewer was off sick but apparently hadn't told anyone?
Finally at the fourth attempt I had my interview with an engineer. It was 75 minutes and consisted of a discussion about a recent project as well as some technical questions and a leetcode task (2 largest elements). It seemed to go ok and I was told I would hear back soon. However after 2 weeks I hadn't heard anything so I decided to email the recruiter asking for an update. That was almost a month ago and as of yet I've still heard nothing back. I'm fine with not passing an interview but I expect at least a cursory "thanks but no thanks" but apparently even that is asking too much.
This whole experience has left me almost glad I wasn't progressed - if this is an insight into life at Spotify I'm happy to not work there. This kind of behaviour shows a complete lack of respect for candidates and their time, so I dread to think how they treat their employees.
I applied online. I interviewed at Spotify (New York, NY) in May 2026
Interview
Spoke with a recruiter, was ghosted after the interview. He asked all the standard questions - why Spotify, expected level, salary expectation, what are the priorities, why left previous company, etc.
Interview questions [1]
Question 1
What was the most complicated project you were working on in your previous company?
Initial HR Call and screening, then arround two weeks later leet code task, followed by on-site architectural/design test and the final culture fit check with HR/Managers. Overall the process was 3-4 weeks.