Company interview guide
Spotify interview process and practice questions
Spotify describes its interviews on its careers site: a recruiter call, an interview with one or two team members, and a final round with several 'band members' from across the business. It says interviewers look at your values as well as your skills, asking whether you take ownership and are adaptable, collaborative and driven. For engineering roles, candidates commonly report coding and system design interviews, often in a shared online editor.
As candidates commonly report it; it varies by team, level and year. Last reviewed 18 October 2026.
The interview process
- 1Recruiter call by video or phone
- 2Interview with one or two team members (for engineers, often a technical or coding interview)
- 3Final round with several people from across the business: technical depth, system design for experienced roles, and values
- 4Decision and feedback from the recruiter
What interviewers listen for
- Values that align with Spotify's
- Ownership and pride in what you deliver
- Adaptability
- Collaboration
- Drive
- The thinking behind your results, not just the results
Behavioral questions
Tell me about a piece of work you're proud of. What was your part, and what did it achieve?
A good answer covers
- The work and why it mattered
- Your own part, with the decisions you made
- The result, measured if you can
Tell me about a time plans changed suddenly. How did you adapt?
A good answer covers
- What changed and why
- How you re-planned and kept others informed
- What you delivered and what you learned
Tell me about a time you worked closely with people in other disciplines, such as design or data, to ship something.
A good answer covers
- Who was involved and what each person cared about
- A disagreement or trade-off and how you settled it
- What shipped and how the collaboration improved it
Tell me about a goal you kept pushing towards even when it got hard.
A good answer covers
- The goal and why it mattered to you
- The hardest point and what kept you going
- The outcome and what you'd do differently
Tell me about a time you tried a new approach that didn't work out. What did you learn?
A good answer covers
- Why you tried it and what you expected
- How you found out it wasn't working
- What you kept, what you dropped and what you'd try next
Role and technical questions
How would you design a feature that builds a personalised playlist for each listener every week?
A good answer covers
- Signals: listening history, skips, saves, similar listeners
- Generating playlists in batch, storing them and serving them quickly
- Balancing familiar and new music, and measuring success
How would you make a song start playing quickly, even on a weak mobile connection?
A good answer covers
- Content delivery networks and choosing bitrate to match the connection
- Buffering or pre-fetching the start of likely next tracks
- Caching on the device and measuring time to first play
How would you test whether a new home screen layout makes people listen more?
A good answer covers
- A clear main metric, such as listening time, plus guardrails
- An A/B test with a fair split and enough time to settle
- Checking effects on different listeners, not only the average
Explain the trade-offs of splitting a large app into many small services owned by different teams.
A good answer covers
- Gains: teams ship independently, services scale separately
- Costs: network calls, harder debugging, data spread across services
- What helps: clear ownership, good APIs, shared tooling and monitoring
Play counts for new releases look too low on an artist dashboard. How would you work out whether the data or the product is wrong?
A good answer covers
- Comparing the dashboard with the raw data for one release
- Checking pipeline delays, filters and counting rules
- Telling affected users and fixing the cause
Walk me through a system or project you know well: the design, what broke and what you learned.
A good answer covers
- The goal and a short picture of the design
- A failure and how it was handled
- What you'd design differently now
Why Spotify? Fit and HR questions
Why Spotify? How do you use it, and what would you change?
A good answer covers
- A real habit with the product, as a listener or creator
- One specific change and who it would help
- Why this team and role in particular
What do you want to learn here, and how does this role fit where you're heading?
A good answer covers
- One or two specific things you want to learn
- How the role builds them
- What you'll bring in return
Tips
- Spotify says it tells you who your interviewers are at each stage; look at their teams so your questions fit.
- Make the things Spotify asks about easy to hear: shared values, ownership, adaptability, collaboration and drive. Prepare a story for each.
- Explain the thinking behind your results, not just the results; Spotify says it wants to understand how you got there.
- Technical interviews may use shared tools such as CoderPad; practise coding and explaining in a plain online editor.
Practise it out loud
A mock interview asks the way Spotify's interviewers are known to, follows up on your answers and gives you a report. The warm-up is free, needs no account and checks five of these questions as you answer.
About this guide
Written by Orbit from Spotify's own public pages and what candidates commonly report. Orbit isn't affiliated with Spotify. The questions are practice questions in the style of its interviews, not questions taken from them. Processes change, so check the job post and what your recruiter tells you.