Spotify interview guide¶
Audio streaming platform; loops pair a project-plus-trivia tech screen with coding, Spotify-feature system design, a production-debugging case study, and values interviews. Updated October 2026.
| Spotify at a glance | |
|---|---|
| Category | Big Tech |
| Intern level | Global Summer Internship Program: 10 weeks, June to August, office-based in London, Stockholm or NYC only. |
| New grad level | Associate Engineer or Engineer I (Levels.fyi ladder: Associate Engineer, Engineer I, Engineer II, Senior Engineer, Staff Engineer). Graduated P&T interns can join the 8-month Emerging Talent Program. |
| 0 to 3 years | Engineer I for about 0 to 3 yrs, Engineer II for roughly 3 to 6 yrs (job titles look like 'Backend Engineer II'). Level is set after the loop and can be reduced (a 2025 MLE was moved from Senior to MLE II). |
| Online assessment | Not standardized; when used, the platform is not named in reviews. Live screens use CoderPad (official) or HackerRank. : Reported OA: LeetCode easy-medium plus a logic puzzle (NYC SWE, 2025); LeetCode medium-hard (US SWE intern, Oct 2025). Data engineering screens are 75 min with theory (eventual consistency, CAP, Avro vs Parquet, Iceberg, MapReduce) plus live coding (2025). |
| Coding rounds | Interns: 1 to 2 technical interviews. Full-time: 1 technical screen (60 to 75 min) plus 1 onsite coding round (some loops have 2 DSA rounds). |
| Behavioral | Spotify's careers site (Oct 2026) lists 3 values called 'The Bassline': One Team, Human Judgment, Make It Happen. Older guides (e.g. interviewing.io) still list five values: Innovative, Collaborative, Sincere, Passionate, Playful. Prepare stories for the current three. |
| Timeline | Official: interview rounds are recruiter screen, second interview with one or two team members, then a final round with multiple people; reply targeted within a few days after the final. Reported: 3 weeks (London backend offer, 2025) to 3 to 4 weeks (Mar 2026 review); London 2.5 months (Jun 2025) and another 2.5 months with repeated reschedules (Dec 2025); NYC up to 3 months; long silences between rounds and some candidates ghosted. Internships: 10 weeks June to August; 2027 recruitment details not yet published as of Oct 2026. CHANGE: Spotify moved to co-CEOs (Alex Norstrom and Gustav Soderstrom) with Daniel Ek as executive chairman (Wikipedia), and its careers site now lists three values instead of the older five. |
| New grad pay | Levels.fyi (read 2026-10-04): US Associate Engineer average total comp $137,729 (21 data points, none in the last 12 months, mostly 2022 to 2023), US Engineer I average $161,823 (2 points in the last 12 months), US Engineer II average $226,620; Spotify pay is base-heavy with small stock. UK Associate Engineer average about GBP 57k; Sweden Engineer I average about SEK 637k (stale). Treat US and Sweden entry-level numbers as low-confidence. |
| Official links | Careers, Students, Official interview prep, Values |
Interview process¶
New grad¶
- Entry route. Spotify had no standing new grad SWE program posting on 2026-10-04; the official early-career path is the Global Summer Internship Program plus the 8-month Emerging Talent Program (fixed term) for graduated Product and Technology interns. Engineer I roles follow the standard engineering process below.
- Recruiter screen. Official: video or phone call with a recruiter about your background and the role (Google Meet). Candidates report 15 to 30 min with 'why Spotify', expected level, salary expectations and work authorization or visa status (a NYC 2026 candidate says Spotify does sponsor but wants it flagged early).
- Technical screen (60 to 75 min). With one or two engineers: discuss a past or side project, answer domain or CS trivia (Java garbage collection, threads, TCP vs UDP, CAP, eventual consistency), then 1 to 2 LeetCode easy-medium problems on CoderPad or HackerRank. A Feb 2026 LeetCode post, a Jul 2025 review and an Amsterdam May 2026 review all describe a 75-min screen.
- Final loop (about 4 x 60 min, virtual). Coding (LeetCode medium, sometimes hard, e.g. Find Median from Data Stream), system design of a Spotify-style feature, a case study (debug a failing production service as the on-call engineer using logs and Linux commands), and a values (behavioral) interview. Official: one interviewer leads while others observe. Mobile and web roles swap in an IDE build round or a frontend task.
- Decision. Official: Spotify aims to reply within a few days of the final interview. Candidates report weeks between rounds and 3 weeks to 3 months overall.
Intern¶
- Application. Students in their graduating or penultimate year (Associates, Bachelor's, Master's, PhD, or bootcamp). Apply only through Spotify's jobs site; no late applications accepted; referrals not required. On 2026-10-04 the page said 'Information regarding our 2027 internship opportunities coming soon.'
- Recruiter call (15 to 30 min). CV walkthrough, why Spotify, what music means to you, logistics.
- Online assessment (some candidates). An intern (Oct 2025 review, location not stated) and a NYC SWE hire (Feb 2025 review) report an OA with LeetCode easy to hard problems (the NYC hire's OA also had a logic puzzle). Not reported in most UK or Sweden intern reviews.
- Technical interview. One technical with one or two engineers: LeetCode easy-medium (e.g. Kth largest element; a string medium in 25 min; two problems in Stockholm) plus domain or CS questions (what is a thread) and resume discussion. One 2025 intern loop (location not stated) had two technicals: one on data structures, one on system design basics.
- Values / hiring manager interview. Culture and values or hiring manager conversation, sometimes the same day as the technical (London 2025).
With 1 to 3 years of experience¶
For 1 to 3 yrs (Engineer I/II) the loop is the same shape as above with higher bars: the tech screen leans more on domain trivia for your stack (Java/JVM, Kotlin, JavaScript), the onsite coding may be LeetCode hard, system design is a full Spotify feature (friends activity feed, playlist images, ad server, recommendations, appointment booking), and the case study simulates an incident or latency investigation. Mobile loops include an IDE round (build an Android app or views from scratch, NYC 2025) and, for senior iOS, rounds on system design, iOS domain, coding standards and values (London 2026). A Stockholm candidate (2026) was required to code in Kotlin, a language listed in the posting but not their strongest.
Online assessment¶
- Platform: Not standardized; when used, the platform is not named in reviews. Live screens use CoderPad (official) or HackerRank.
- Format: Reported OA: LeetCode easy-medium plus a logic puzzle (NYC SWE, 2025); LeetCode medium-hard (US SWE intern, Oct 2025). Data engineering screens are 75 min with theory (eventual consistency, CAP, Avro vs Parquet, Iceberg, MapReduce) plus live coding (2025).
- Notes: Most Spotify candidates go straight from recruiter call to a live technical screen; do not expect an OA by default.
Prepare with How to pass an OA and compare formats in OA formats by company.
Coding rounds¶
- Rounds: Interns: 1 to 2 technical interviews. Full-time: 1 technical screen (60 to 75 min) plus 1 onsite coding round (some loops have 2 DSA rounds).
- Style: LeetCode easy to medium in screens, medium to hard onsite (heaps, BFS on graphs, backtracking such as Combination Sum II, strings and hash maps), often themed on music: playlists, songs, listening counts. Screens mix in quiz-style CS questions.
- Environment: CoderPad (named on Spotify's FAQ) or HackerRank for coding; Google Meet or Zoom for video; Mural for design whiteboarding; mobile roles use a real IDE.
- Graded on: Working solution and complexity, clear communication, collaboration with the interviewer (a 2025 London candidate was rejected as 'not being collaborative enough'), plus depth on your own project.
- Reported focus topics: Heaps and order statistics (median stream, kth largest), Backtracking (combination sums over song durations), Strings and hash maps (play counts, visit patterns), Graphs and trees (BFS, LCA in org charts), CS fundamentals trivia: GC, threads, stack vs heap, TCP vs UDP, CAP, Production debugging with logs, metrics and Linux commands, System design of Spotify features (feeds, images, ads, recommendations), Behavioral mapped to One Team, Human Judgment, Make It Happen
Run every practice problem through the 45-minute framework and the code quality rubric.
What they ask (data)¶
Based on 5 distinct problems tagged to Spotify in the last 6 months (0 in the last 30 days, 5 in the last 3 months, 12 all-time) across two open datasets of LeetCode company tags. Tags are user-reported, so treat frequency as a signal, not a promise.
Difficulty mix (last 6 months): Medium 60%, Easy 20%, Hard 20%
Most tagged topics (share of problems): Array 60%, Sorting 60%, Hash Table 40%, String 40%, Design 40%, Data Stream 40%, Heap (Priority Queue) 40%, Sliding Window 20%, Queue 20%, Divide and Conquer 20%
Watch out: Spotify has thin LeetCode data. Weight the reported questions and the format notes above more than this list.
Most frequent problems¶
Ranked by frequency, weighted toward the last 30 days. Classics like Two Sum sit near the top of almost every company's list because users tag them everywhere. Solve those fast. The signature list below is more specific to this company.
| # | Problem | Difficulty | Last seen | Topics |
|---|---|---|---|---|
| 1 | Longest Substring Without Repeating Characters | Medium | 3 months | Hash Table, String, Sliding Window |
| 2 | Moving Average from Data Stream | Easy | 3 months | Array, Design, Queue, Data Stream |
| 3 | Analyze User Website Visit Pattern | Medium | 3 months | Array, Hash Table, String, Sorting |
| 4 | Kth Largest Element in an Array | Medium | 3 months | Array, Divide and Conquer, Sorting, Heap (Priority Queue) |
| 5 | Find Median from Data Stream | Hard | 3 months | Two Pointers, Design, Sorting, Heap (Priority Queue) |
Signature problems¶
Problems where Spotify accounts for a large share of all recent tags across companies. These are the most Spotify-specific questions in the data.
| # | Problem | Difficulty | Last seen | Topics |
|---|---|---|---|---|
| 1 | Moving Average from Data Stream | Easy | 3 months | Array, Design, Queue, Data Stream |
| 2 | Analyze User Website Visit Pattern | Medium | 3 months | Array, Hash Table, String, Sorting |
Reported in 2025 to 2026 interviews¶
Questions candidates said they got, each linked to the post where it was reported.
| Question | Role | When | Source |
|---|---|---|---|
| Given song durations and a target playlist length, find all combinations that sum to the target | Software Engineer Intern (location not stated) | 2025-10 | post |
| LeetCode string-manipulation medium in 25 minutes, then resume discussion | Software Engineering Intern, NYC (offer) | 2026-03 | post |
| Kth largest element in an array | Software Engineer Intern (offer; location not stated) | 2025-04 | post |
| Two LeetCode problems plus 'What is a thread?' | Software Engineer Intern, Stockholm | 2025-04 | post |
| Domain questions, a LeetCode problem and culture fit in one day | Software Engineer Intern, London | 2025-11 | post |
| Find median from a data stream (onsite coding, LeetCode hard) | Software Engineer, London | 2025-06 | post |
| Design a Spotify friends activity feed | Software Engineer, London | 2025-06 | post |
| Case study: debug a production system with logs and Linux commands | Software Engineer (location not stated) | 2025-12 | post |
| Case study: observe a latency issue and troubleshoot it | Software Engineer, London | 2025-12 | post |
| Case study: debug a failing service like an on-call engineer | Software Engineer (offer; location not stated) | 2025-02 | post |
| Design a recommendation engine for a music streaming service | Software Engineer, NYC (offer) | 2025-02 | post |
| Combination Sum II variation (each candidate used once, unique combinations) | Android Engineer onsite, NYC | 2025-05 | post |
| How does Java garbage collection work? | Software Engineer, Amsterdam | 2026-05 | post |
| What is eventual consistency? Explain the CAP theorem. | Data Engineer tech screen (location not stated) | 2025-12 | post |
| Simulate traffic lights using plain HTML, JS and CSS | Software Engineer (frontend), NYC | 2025-02 | post |
| Most played songs: build a playlist of a user's most frequently played songs | Mid-level (Hello Interview; Spotify report, other reports are Amazon) | 2025-09 | post |
| Second largest digit in a string | Mid-level (Hello Interview) | 2025-03 | post |
| Analyze user website visit pattern (LC 1152 is Premium) | Mid-level (Hello Interview; Spotify reports May and Jul 2026) | 2026-07 | post |
| Design a playlist image service (upload and manage custom playlist images) | Mid-level (Hello Interview) | 2026-06 | post |
| Design a low-latency ad banner delivery system for the Spotify desktop app | Mid-level (Hello Interview) | 2026-05 | post |
| Difference between TCP and UDP (domain question in the tech screen) | Backend Engineer, London (offer) | 2025-04 | post |
| Find the two largest elements (LeetCode task in a 75-min tech screen, after project discussion and technical questions) | Software Engineer, Amsterdam | 2026-05 | post |
| Merge two playlists together (LeetCode style) | Senior iOS Engineer, London | 2026-05 | post |
| Lowest common parent of a list of employees in an org chart; expected to build the graph on your local machine and run the code | Senior (Hello Interview; 3 reports, Spotify Jan and Sep 2026) | 2026-09 | post |
Beyond LeetCode¶
Case study: live production troubleshooting or on-call role play (debug a failing service using logs and Linux commands; investigate a latency issue). Domain trivia in the tech screen (Java GC, threads, stack vs heap, TCP vs UDP, CAP). Mobile IDE rounds (build an Android app or views from scratch). Frontend tasks (simulate traffic lights in plain HTML, JS and CSS). Data engineering: theory-heavy 75-min screen (formats, table formats, consistency). MLE: loop mostly case studies (recommendation backend, most popular artists per country pipeline, predict MAU).
System design¶
Part of full-time loops including Engineer I/II (Glassdoor 2025 to 2026), and one 2025 intern report mentions a 'system design basics' round. Prompts are Spotify product features: friends listening activity feed, playlist image upload and generation service, banner ad server rotating ads every 30 seconds on desktop, music recommendation engine, appointment booking backend. Expect follow-ups on scale and trade-offs. Senior mobile loops still include a system design round (London iOS 2026).
Start with who needs system design, then the framework.
Behavioral¶
Framework: Spotify's careers site (Oct 2026) lists 3 values called 'The Bassline': One Team, Human Judgment, Make It Happen. Older guides (e.g. interviewing.io) still list five values: Innovative, Collaborative, Sincere, Passionate, Playful. Prepare stories for the current three. (official page)
What they look for:
- Values alignment, ownership and pride in your work, adaptability and collaboration, drive (official interview tips)
- One Team: sharing context, breaking silos, winning together
- Human Judgment: thoughtful risk-taking, learning from mistakes
- Make It Happen: bias to action, execution and urgency
- Framing achievements as team wins rather than solo heroics
- How you use and promote AI tools in your work (2026 reports)
Questions to prepare:
- Why Spotify? What does music mean to you? (SWE Intern, NYC, 2026)
- Tell me about yourself and why Spotify. (SWE Intern recruiter call, London, offer, Mar 2026)
- Describe an architectural decision you made. What would you have done differently? (SWE, Jun 2025)
- Introduce a side project you worked on. (SWE tech screen, Jul 2025)
- What was the most complicated project at your previous company? (SWE recruiter call, NYC, May 2026)
- Tell me about work you are proud of. (SWE, Mar 2026)
- Tell me about a new process you welcomed and why. (Hello Interview, senior, 2026-01)
- How have you promoted AI usage in your team? (Hello Interview, mid-level, 2026-06)
- What do you think of diversity and inclusivity? (Hello Interview, 2025-01)
Build your answers with the story bank. Company detail: behavioral guide.
Tips¶
- Prepare for 10 to 15 minutes of CS trivia in the tech screen in your main language: garbage collection, threads vs processes, stack vs heap, TCP vs UDP, CAP and eventual consistency.
- Pick one project you can discuss for 15 minutes; screens open with it and interviewers ask what you would change.
- Practice an on-call case study: from an alert and some logs, narrow the cause with Linux commands, mitigate first, then find the root cause and explain the fix.
- Practice designing Spotify features (friends activity, playlist images, ad rotation, recommendations, appointment booking) end to end with APIs and data models.
- Map 6 to 8 stories to the current three values (One Team, Human Judgment, Make It Happen); older five-value lists are outdated.
- Talk through your thinking and invite input during coding and design; candidates report rejections for not being collaborative enough.
- Internships are only in London, Stockholm and NYC and late applications are rejected; check the students page for 2027 dates.
- Expect slow replies; follow up politely with your recruiter and keep other interviews going.
- International candidates: recruiter calls ask about work authorization; a NYC 2026 candidate reports Spotify sponsors visas but wants it raised early, so state your status in the first call.
4-week plan for Spotify¶
Do this after you finish a core list like Grind 75 or NeetCode 150.
- Week 1: Solve problems 1 to 20 from the most frequent list. Time-box each at 30 minutes.
- Week 2: Solve problems 21 to 40. Re-solve any you failed in week 1 without looking.
- Week 3: Solve the signature problems and every reported question above. Do 2 timed mock interviews.
- Week 4: Write 8 stories for the Spotify's careers site (Oct 2026) lists 3 values called 'The Bassline': One Team, Human Judgment, Make It Happen. Older guides (e.g. interviewing.io) still list five values: Innovative, Collaborative, Sincere, Passionate, Playful. Prepare stories for the current three. round. Do 2 full mock loops. Review the online assessment and system design notes above.
Sources¶
- Question data: liquidslr/leetcode-company-wise-problems and snehasishroy/leetcode-companywise-interview-questions, merged and ranked by scripts/build_question_data.py.
Watch out: Strong: official process stages, tools (Google Meet, CoderPad, Mural), internship rules (10 weeks, London/Stockholm/NYC, eligibility, no late applications), and the new three-value 'Bassline' (verified on lifeatspotify.com; the change date is not stated). Medium: loop composition varies by team and office (some loops have 2 DSA rounds, some have the case study, mobile/web loops differ); OA use is occasional. Weak: entry-level compensation (US and Sweden Levels.fyi data is old and sparse) and the exact new grad level name (Associate Engineer vs Engineer I). LeetCode discuss has very few 2025 to 2026 Spotify SWE posts, so most questions come from Glassdoor (permalinks confirmed in a browser) and Hello Interview community reports. Spotify 2027 internship dates were not published as of 2026-10-04. Reddit and Blind were not covered because the web search budget ran out. FACT-CHECK (2026-10-04, second agent): all URLs re-fetched (lifeatspotify.com, Levels.fyi and Lever via curl; LeetCode via GraphQL; Glassdoor permalinks and Hello Interview timelines rendered in a browser). Fixed: many Glassdoor reviews do not state a location, so 'US', 'UK', 'UAE', 'Canada' and 'Sweden' labels were removed; several Hello Interview dates were off by a month (playlist image service Jun 2026, ad server May 2025, process-change Jan 2026, diversity Jan 2025); behavioral questions that had no source now cite Glassdoor permalinks; LC 1152 is Premium. Removed unverifiable specifics ('parse data into a table view', 'SQL window functions', 'Spotify Wrapped' design): not found in 2024 to 2026 Glassdoor pages 1 to 36 or the cited sources.
Next: All companies