Candidates describe a recruiter or manager screen, a technical screen, and a final loop of about four interviews covering coding, system design, values and often an incident case study. Timelines and communication vary widely.
$160K
Avg. Base Comp
$230K
Avg. Total Comp
3-8 rounds
Typical Rounds
3-12 weeks
Process Length
Candidates describe a fairly conventional Spotify Software Engineer loop with a few Spotify-specific twists. Most accounts begin with a recruiter or hiring-manager call, then a technical screen, then a final loop of about four interviews. The screens differ by team. One candidate got easy-to-medium coding plus JavaScript trivia. Another walked through a recent project and then took TCP/UDP and DNS questions. A third was asked about garbage collection and the difference between a process and a program. Fundamentals questions show up alongside LeetCode-style coding in several accounts, so practice explaining core concepts out loud, not only solving problems.
In the final loop, candidates report coding at roughly LeetCode-medium level, including graph, tree and BFS problems, plus a system design round and a values or behavioral round. Four candidates also describe an incident or production-debugging case study, which one offer recipient called the most stressful round. System design prompts varied: a music recommendation engine, extending an existing feature, and a feature inside the Spotify app. One rejected candidate said the feedback centered on collaboration and wished they had asked more questions during design. Treat design as a dialogue, and be ready to say how you would measure whether a system works.
Check the team and stack named in your invite. One candidate's screen was relabeled from backend to web and turned into front-end questions. Frontend candidates should expect design questions tailored to that space.
Timing and communication are the most common complaints. Reports range from roughly three to four weeks to about three months, and several candidates describe weeks of silence between rounds or after the final interview. Follow up in writing and keep other processes moving.
Synthesized from 20 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Spotify process.
My interview process started with an HR screen, followed by a conversation with the hiring manager. Then came three back-to-back interviews with different people, and finally a round with someone more senior. Throughout, I was asked about previous experience and past projects, including why I wanted to work at Spotify. The coding questions were relatively straightforward—the kind you'd encounter during day-to-day work for a mid-level role, like a Spotify-type application question. The interviewers themselves were nice and easy going, casual rather than overly formal, which made the conversations feel more natural.
The real challenge wasn't the technical bar—it was the process itself. Spotify took an incredibly long time between rounds and was not very communicative about timelines. I had to follow up so many times and went weeks without hearing anything. I made it to the final round and my recruiter told me they wanted to schedule my interviews ASAP, which gave me hope. But then the recruiter stopped responding entirely, leaving me in limbo.
In the end, I received a rejection with no real explanation. The interviews themselves were fine and the bar seemed fair, but the lack of respect for my time and the communication breakdown throughout left a sour taste.
Prep tip from this candidate
Expect a multi-stage process: HR screen, hiring manager interview, three back-to-back technical interviews, and a final senior round. Questions focus on past experience and projects with medium-difficulty coding challenges. Be prepared for significant delays between rounds and poor communication—follow up proactively and get everything in writing, as recruiters may ghost after promising quick scheduling.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Spotify
Given an integer N, write a function that returns all of the prime numbers up to N
| Question | |
|---|---|
| Top 3 Users | |
| The Brackets Problem | |
| Valid Anagram | |
| Hurdles In Data Projects | |
| Third Unique Song | |
| Count Transactions | |
| Check Matching Parentheses | |
| A/B Testing a Checkout Button Change | |
| String Palindromes | |
| Three Indexes Adding Zero | |
| Confidence Interval Explanation | |
| Pathfinder in Maze | |
| Safe Deployments | |
| Minimum Directional Path | |
| Duplicate Product Names | |
| Ranking Metrics | |
| Generating Discover Weekly | |
| Singly Linked List | |
| Podcast Search | |
| Bootstrapping Samples | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Empty Neighborhoods | |
| Monthly Customer Report | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Rolling Bank Transactions | |
| Comments Histogram |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an opening call with a recruiter or, in some cases, the hiring manager. It typically covers your background, the role and what the process will involve. Reported lengths range from a short 20-30 minute call to a fuller conversation. Some candidates were unsure of the exact process or role title at this stage, so it is worth confirming the team, stack and stages early.
Candidates report a technical screen of about an hour to 75 minutes with one or two engineers. Reported content includes a walkthrough of a recent or side project and an easy-to-medium coding problem. Fundamentals questions also appear in several accounts: JavaScript trivia, garbage collection, TCP/UDP and DNS, and process versus program. One candidate's screen was web/front-end focused, so the content may depend on the team.
Several candidates describe a final stage of about four interviews, sometimes in one day and sometimes spread over two days. Reported components include a medium-level algorithms round (graphs, trees, BFS), a system design or architecture round, and a values or behavioral round. Design prompts reportedly ranged from a music recommendation system to extending an existing feature. Behavioral questions included conflict on a team, why Spotify, and work you are proud of.
Four candidates describe a case study or roleplay in which they diagnosed a production incident, and one said it was based on a real incident at the company. Candidates describe it as a live, on-call-style exercise rather than a textbook question. It may reward calm reasoning and stating your assumptions out loud. Not every candidate mentions this round, so treat it as likely rather than guaranteed.
Outcomes in the reports are mixed, with several offers and several rejections. Candidates commonly describe slow or uneven communication. Some waited a week or more between stages, and a few heard nothing for weeks after the final round. Others received generic rejections with little feedback. Reported total timelines run from about three to four weeks to roughly three months, so it may help to follow up in writing.
