0 day streak

Spotify interview rounds

Product Global

Pick your level above: the list shows only your rounds, with what interviewers score at that level.

0%ready
  1. Phone / recruiter screen · 30 min

    Recruiter or hiring-manager chat on background, motivation and team fit.

    At : Usually one medium problem. Explain your idea before coding and test by hand at the end.

    At : One or two problems, a little faster. Some companies mix in a design question.

    At : Often a coding problem plus questions about your past systems; some companies (Uber) use it to set your level.

    At : Frequently a hiring-manager conversation about scope and impact instead of pure coding.

  2. Online assessment · 60 min

    Some early-career and intern pipelines start with a timed coding test.

    At : The main filter for new grads and campus drives. Expect two medium problems, sometimes one hard. Passing all test cases on both usually gets you to the next round.

    At : Used by some companies for experienced hires (Amazon, Uber, Salesforce, Oracle). The bar is the same as for SDE 1 but the time is often shorter.

    At : Rare. Most companies replace it with a live screen for senior candidates.

    At : Almost never used.

  3. Coding (DSA) × 2 · 60 min

    Technical screen with engineers, then an onsite DSA round (some loops add another), mostly easy to medium.

    At : The largest part of the loop: often three coding rounds. Medium problems, sometimes one hard. Correct, clean code and clear reasoning matter more than speed.

    At : Two or three rounds at medium to hard level. You are expected to reach the optimal approach with fewer hints and to test without being asked.

    At : Usually two rounds. Same difficulty, but interviewers expect quick, confident problem solving and production-quality code.

    At : One or two rounds, sometimes design-flavoured (build a small class with several methods). Coding is a bar to clear, not where level is decided.

  4. System design (HLD) · 60 min

    Product-flavoured design such as recommendations, a friends activity feed or streaming.

    At : Usually absent, or light design questions inside a coding round.

    At : Present at most companies. A sound end-to-end design with sensible components and basic scaling is enough.

    At : One or two rounds that set your level. Expected to lead, size the system and go deep on two or three hard parts.

    At : Two rounds at many companies. Expected to handle ambiguity, cost, operations and cross-team trade-offs, and to change the design when the interviewer pushes.

  5. Team-specific round · 60 min

    Case study where you troubleshoot a real-world production incident or outage.

    At : Mostly language and CS fundamentals deep dives (Java internals, databases, OS).

    At : Debugging, integration or code review rounds at product companies.

    At : Project deep dives become central: scope, trade-offs and what you would do differently.

    At : Presentations or deep dives on multi-quarter work that crossed teams.

  6. Behavioral · 45 min

    Values interview on collaboration, ownership and handling disagreement.

    At : Stories from internships, projects or your first job are fine. Show learning, ownership and teamwork.

    At : Stories should show you owning features end to end and handling conflict maturely.

    At : Expected scope: projects across quarters, influencing other teams, mentoring.

    At : Expected scope: org-wide impact, setting direction, hard trade-offs with leadership.

What interviewers look for

  • Clean, practical, testable code over clever tricks
  • Collaborative, low-ego problem solving
  • Structured debugging of production incidents
  • Product-aware system design for streaming and recommendations

Worth knowing

  • The loop typically includes a production-incident case study, which is unusual among product companies.
  • Coding difficulty is reported as mostly easy to medium, but at least one 2025 loop used a hard streaming-median problem.
  • End-to-end timelines of two to three months are commonly reported.
  • Technical screens may include networking basics such as TCP versus UDP and DNS.

Sources

Written in our own words from public candidate reports and Spotify's careers pages, checked 2026-11. Company names and logos belong to their owners; AlgoRung is not affiliated with Spotify.

Questions people ask

How many interview rounds does Spotify have for SDE 1 (Engineer I)?

About 4 interviews after the screening: phone / recruiter screen, online assessment, coding (dsa), team-specific round, behavioral. There is usually no separate design round at this level.

How many interview rounds does Spotify have for SDE 2 (Engineer II)?

About 5 interviews after the screening: phone / recruiter screen, coding (dsa), system design (hld), team-specific round, behavioral. Design is part of the loop at this level.

How many interview rounds does Spotify have for SDE 3 (Senior Engineer)?

About 5 interviews after the screening: phone / recruiter screen, coding (dsa), system design (hld), team-specific round, behavioral. Design is part of the loop at this level.

How many interview rounds does Spotify have for staff (Staff Engineer)?

About 5 interviews after the screening: phone / recruiter screen, coding (dsa), system design (hld), team-specific round, behavioral. Design is part of the loop at this level.

What coding questions does Spotify ask?

The most reported are Moving Average from Data Stream, Longest Substring Without Repeating Characters, Two Sum, Valid Parentheses, Kth Largest Element in an Array, Find Median from Data Stream. Candidates say Spotify focuses on strings, hash maps, sliding window, heaps, graphs.

What is the Spotify behavioral interview based on?

Company values (The Bassline): One Team, Human Judgment, Make It Happen. A dedicated values interview probes teamwork and judgment through past stories; candidates report STAR-style answers work well and that low collaboration can cost an offer.