Check out your Company Bowl for anonymous work chats.
Bowls
Get actionable career advice tailored to you by joining more bowls.
Followed companies
Stay ahead in opportunities and insider tips by following your dream companies.
Job searches
Get personalized job recommendations and updates by starting your searches.
Spotify interviews FAQs
Data Engineer applicants have rated the interview process at Spotify with 3.2 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 Data Engineer roles take an average of 27 days to get hired, when considering 28 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 Data Engineer according to 28 Glassdoor interviews include:
Phone interview: 43%
One on one interview: 17%
Skills test: 13%
Group panel interview: 9%
Presentation: 7%
Background check: 6%
Personality test: 4%
IQ intelligence test: 2%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 3 weeks. I interviewed at Spotify (New York, NY)
Interview
All done online. The initial screen was quick and efficient. The full panel interview was not - organizer ask for not 1 not 2 but 3 weeks of multi-day availability. Pretty inefficient, and I proposed splitting that into 2 days instead, so organizer finally confirmed on a single day. 2 days before the panel interview, 3 out of 5 of the interviewers on the list changed. And when it didn't work out (even tho my code worked in all tech questions), they only said "misalignment of role and experience". After spending a whole day (5+ hours), most companies would try to give a bit more feedback than that. And as a result I didn't learn anything about my interviewing from spending 5 hours with them.
Interview questions [4]
Question 1
Asked by the interviewer a "Data Engineer" to join 2 tables together to label start/end of a track play , only when I proposed a working solution he diverted me to another solution that he had in mind all along, thinking it was better as it didn't require window functions, but it did require them. He just didn't know they are called window functions. Admittedly, the "Data Engineer" said he hasn't worked on spark in a while, and is quite junior.
2 main algo questions are dynamic-programming requiring recursive implementations. Similar but different questions, and they need you to do everything from implementing helper classes to writing the actual test case AND printing out result in an expected way. Hard to get 100% right given the time limit (but I did just in time)
The interview process was long. I had a positive interview with HR. But the next stage was coding round with 2 senior engineers interview was tough need to good practice before going to the interview.
Interview questions [1]
Question 1
HR process just had general questions. But in coding round. It first started with a few basic questions about what is garbage value. About the distinction between process and program and what is columnar approach in tables.
I applied online. I interviewed at Spotify (Dallas, TX) in May 2026
Interview
Recruiter
Asked about background and visa status, and had secluded for 30 mins but didn't know she was in a rush and wind up in 12 mins and after that got selected for next round tech screen
I applied online. I interviewed at Spotify (New York, NY) in Mar 2026
Interview
Received an offer for an interview with a recruiter around early March, it was 20 minutes and the recruiter was very sweet! I was asked about my background, she asked me to elaborate on specific experiences on my resume, challenges I encountered, what technical frameworks I used, the standard questions. It was very straightforward and I received the offer later that day for the final round interview consisting of a 45 min behavorial interview and a 45 min technical interview.
Interview questions [1]
Question 1
What challenges did you run into on a project and how did you navigate it?