Data Engineer 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 45% positive. This is according to Glassdoor user ratings.
Candidates applying for Data Engineer roles take an average of 14 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at Spotify overall takes an average of 36 days.
Common stages of the interview process at Spotify as a Data Engineer according to 1 Glassdoor interviews include:
One on one interview: 33%
Skills test: 33%
Phone interview: 33%
Here are the most commonly searched roles for interview reports -
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?