Spotify 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.

My interview for a Technical Support role at Spotify was a refreshing departure from the typical corporate grill-fest. It felt less like an interrogation and more like a high-stakes jam session. The panel prioritized my problem-solving logic and user empathy over rote memorization of technical manuals. We spent a good portion of the time walking through a complex troubleshooting scenario where they encouraged me to think out loud, treating my ideas with genuine curiosity rather than just looking for a 'correct' checkbox. It was clear they value a culture of collaboration and authenticity, making the entire process feel inclusive and high-energy.

I got to the second interview and was unfortunately rejected, but they sent feedback which was cool of Spotify. The first interview was about my work history, why I'm looking to leave my current job, and my interest in Spotify. The second interview involved discussing a recent project I worked on (or a personal one), what I'd change about it, and how I approach scaling challenges. Then there were some technical questions specific to the web engineer role, covering HTML, CSS, and JavaScript, particularly focusing on `setTimeout` and explaining the execution order, including a coding exercise. The final part was a coding challenge, a LeetCode problem similar to a sliding window type, rated easy to medium.

Spotify's interview process kicked off with a recruiter screening, then led into a 75-minute session with two interviewers. They were super supportive and made the atmosphere really comfortable. We started with introductions, then dove into some theory questions. They asked about eventual consistency, the CAP Theorem, and different data formats like Avro and Parquet. We also discussed Python versus low-level languages, the advantages of the Iceberg table format, and how to explain MapReduce. They also threw in questions about time complexity for linked lists and explaining tree structures. Then there was a live coding challenge: creating a Fibonacci sequence. I managed to solve it, though it took a bit longer than I'd hoped since I'm not super experienced with these types of algorithm questions.