Spotify Data Scientist candidates reported recruiter, technical, hiring-manager, and case-study stages, with Python, SQL, statistics, business reasoning, and playlist-focused analysis.
$158K
Avg. Base Comp
$199K
Avg. Total Comp
4 rounds
Typical Rounds
4-6 weeks
Process Length
Spotify Data Scientist interview reports point to a process that tests practical analysis alongside product and business judgment. One candidate described a recruiter screen followed by technical, hiring-manager, and case-study stages; another said the recruiter had already outlined the structure. The clearest recurring technical themes are Python, SQL, statistics, and data manipulation.
For the technical screen, candidates reported a Python FizzBuzz prompt, several linked SQL questions on time spent and ranking, and a window-function task requiring LAG. Another report described a coding question similar to Three Sum. Practice explaining a solution as you work, because one candidate found the interview rushed and impatient despite considering the problem simple on paper.
The later interview content was more applied. One candidate reported a hiring-manager discussion of Premium-ad pricing using CLTV and CAC, a resume deep dive, and statistics questions. That same report included a cold-start experiment-design scenario for a grocery shop adding fruit, then a case-study presentation on what makes a playlist successful. Prepare to frame an ambiguous product question, choose an experiment or analysis approach, state assumptions, and communicate the result clearly. The detailed stage sequence comes from one report, so later-stage coverage may vary.
Synthesized from 2 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.
There were four rounds in total: a recruiter screen, a technical screen, a hiring manager round, a case study presentation, and a final round with business stakeholders. I was rejected after the case study round.
The technical screen was fairly straightforward. It included one Python FizzBuzz question, three connected SQL questions, and some chart interpretation and inference questions. The SQL questions were about users with the most time spent, ranking, and a window-function question where I was expected to use LAG.
The hiring manager round included a business question about how much Spotify should pay a platform for Spotify Premium ads, using CLTV and CAC theory. There was also a deep dive into my resume and a heavy focus on applied statistics. One case-style question was: you are a data scientist for a grocery shop that does not sell fruit; how would you start selling fruit, which fruit would you sell, and how would you design the experiment? It was essentially a cold-start experimentation problem.
The case study prompt was about what makes a playlist successful.
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 | |
| Decreasing Comments | |
| The Brackets Problem | |
| Valid Anagram | |
| Hurdles In Data Projects | |
| Third Unique Song | |
| Banner Ad Strategy Success | |
| Count Transactions | |
| Declining Usage After Launch | |
| Data Preparation for Imbalanced Data | |
| A/B Testing a Checkout Button Change | |
| Estimating D | |
| String Palindromes | |
| Three Indexes Adding Zero | |
| Confidence Interval Explanation | |
| Pathfinder in Maze | |
| Check Matching Parentheses | |
| Minimum Directional Path | |
| Duplicate Product Names | |
| Ranking Metrics | |
| Generating Discover Weekly | |
| Podcast Search | |
| Podcast Space | |
| Singly Linked List | |
| Prime Music Integration | |
| Bootstrapping Samples | |
| Third Party Ad Pricing | |
| Empty Neighborhoods | |
| 2nd Highest Salary |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reported that a recruiter explained the interview structure and supplied preparation material. Use this conversation to clarify the role focus and how later discussions will be organized.
Candidates reported Python and SQL alongside chart interpretation, inference, statistics, and data manipulation. Specific examples included FizzBuzz, ranking and time-spent SQL questions, and a `LAG` window-function prompt.
One candidate reported a resume deep dive, applied-statistics focus, and a business question about pricing Spotify Premium ads through CLTV and CAC theory. Expect the discussion to connect analytical choices to a commercial decision.
One candidate reported a case-study prompt on what makes a playlist successful. The same report included a cold-start experimentation scenario, suggesting preparation should include structuring ambiguous product-analysis problems.
