Software Engineer - Backend applicants have rated the interview process at Spotify with 2.9 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 53% positive. To compare, the company-average is 47.4% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer - Backend roles take an average of 22 days to get hired, when considering 17 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 - Backend according to 17 Glassdoor interviews include:
Phone interview: 37%
IQ intelligence test: 15%
One on one interview: 11%
Presentation: 11%
Group panel interview: 7%
Other: 7%
Personality test: 7%
Background check: 4%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 2 weeks. I interviewed at Spotify (Stockholm, Stockholm) in Aug 2018
Interview
Quick chat with recruiter, talked about my experience, etc. Asked me to describe one time I made a mistake.
Second part was 1.5h interview with two engineers where they made me talk about the project I was working on. I described high level and also got into specifics. They also asked questions about certain areas of the system. I think I did this part ok but feedback was that I didn't explain well the low level details. This was a bit of a surprised to me as they responded positively to my explanations. In my opinion, it wasn't clear as to how deep they wanted me to go so I'd recommend to keep asking whether your explanation is low level enough or whether you should go further.
Codility test: simple enough (remove duplicates from a list of integers keeping the order). Engineers were nice, gave hints, etc. They asked me how you'd test the code, time/space complexity and a way to make it more optimal. I didn't do great on this part but that's mainly on me as I got stuck, probably for lack of practice.
Interview questions [3]
Question 1
TCP/UDP, difference and what you could use each one for
Was reached out by recruiter after cold apply. Interviewer asked basic questions to know the background as initial screening step, but didnt proceed to next steps after cancelling the scheduled interviews. suspect its bc visa issues
In overall, it was a positive experience. Everybody's nice there. I like every step and challenge.
Everybody was supportive and well informed about the whole interview process which was really long.
I applied online. The process took 3 weeks. I interviewed at Spotify (New York, NY) in Dec 2021
Interview
1) 15min recruiter screening. The recruiter was nice but seem to be in a rush the whole time.
2) 1hr screening with a senior engineer and one person shadowing. The question was pretty easy and dealt with implementing a cache using a language of your choice. The interviewer was super nice and pleasant to work with. He seemed to know a lot and care about D&I.
2 weeks later I asked for a follow up and the recruiter told me the position was closed. Bruh. A waste of my time.
Interview questions [1]
Question 1
Something along the lines of implement a cache.
And a bunch of general questions regarding CS concepts that you either know it or don't. (It won't be hard if you have a CS degree or experience with SWE),