Spotify Software Engineer Interview Questions
& Process

I applied to Spotify knowing I had another offer and asked them to expedite their process, which they said normally takes 3 weeks but they would try for 2. The process ended up taking much longer than expected due to delays from recruiters in Singapore causing ~24h email delays, issues with their scheduling platform, and a company-wide "wellbeing week" that added another week. Even after I did well in all rounds, I waited nearly 2 more weeks to hear back. When I followed up after 5 weeks, I was rejected for being "in a hurry," which I communicated upfront (1-2 week availability). I think this is unacceptable and unprofessional, especially since I would have likely gotten an offer based on my performance and fit if the timeline hadn't been so poorly managed. It was a disappointing experience with many stressful hours of preparation and interviews, ultimately leading to rejection due to process issues rather than merit, which has negatively impacted my view of Spotify.

The whole interview process spanned approximately 2.5 months. It started with a tech screening where I had to talk about a favorite project and solve an easy coding problem. Then came the main loop, which included rounds for coding, system design, values (behavioral), and a case study focused on production troubleshooting. The system design question, which was about a Spotify app feature, was quite challenging. Unfortunately, I didn't make it through because they felt I wasn't collaborative enough. The coding problem in the main loop was a Leetcode Hard, comparable to LC295.

Recruiter hit me up on LinkedIn. The whole thing took about 3 months. First, there was an OA with some LC easy-medium stuff and a logic puzzle. Then a recruiter screen asking about my background and such. After that, a tech screening had one coding round (LC medium, using strings and hashmaps) and a few simple system design questions. The onsite had 4 parts: one coding round focused on graphs/trees, another sys design round where I had to design a music recommendation system, a behavioral round about Spotify culture and past teamwork, and a case study about dealing with a live service outage. The case study was pretty intense, felt like live debugging under pressure. So yeah, grinding LeetCode is crucial, but you also need a good grasp of system design – practice it a lot. I found grokking system design and doing mock interviews with an ex-Spotify coach on Prepfully really helpful. The process was a bit drawn out but went smoothly, no issues.