Spotify · Software engineer · All levels
Warm and conversational
The question shapes this round uses. Larpy does not read these out. It builds each one from your own resume, because the generic version is the one you have already rehearsed.
Spotify’s published process. Lime marks the stage this round runs.
Built from what Spotify publishes about its own process and from real interview data. No leaked question lists. The questions you get are generated against your own resume, so they are not from anyone else's interview.
The three stages (apply, interview, decision) and the interview sequence: a video or telephone interview with a recruiter, a second interview with one or two team members, then a final round meeting multiple band members across the business. Also the lead-and-shadow interviewer setup, virtual interviews on Google Meet with role-specific tools such as CoderPad, the five things interviewers weigh, the 'few weeks' and 'few days' response times, and that the recruiter owns the compensation conversation.
The same three interview stages under dedicated headings; CoderPad and Mural named as the tools for the more technical stuff; the five assessment questions (values alignment, ownership, adaptability, collaboration, drive); and the feedback policy.
Spotify uses AI and other automated tools to assist recruiters, but states that all decisions on interview selection, advancement and hiring are made by human recruiters and hiring managers, and that AI tools do not make final or fully automated employment decisions.
The engineering disciplines a loop is tailored to: Backend, Mobile, Client C++, Machine Learning, Data, Web, Developer Tools & Infrastructure, Network Engineering & IT, Security and Tech Research.
The level titles Spotify posts against in live engineering roles (Engineer I, Senior, Staff, Senior Staff), corroborating the ladder.
Spotify's SWE level ladder: Associate Engineer (entry level), Engineer I, Engineer II, Senior Engineer, up to Staff Engineer, plus compensation structure.
The four dimensions coding rounds are scored on across big tech (communication, problem solving, technical competency, testing) and the strong hire / hire / no hire bands.
System design rounds are typically reserved for candidates with a few years of experience, which is why this round is gated to Engineer II and Senior.
Sources last checked . Hiring loops change, so this date is the honest limit on everything above.
STAR-style probing against the five things Spotify says it weighs
A spoken design conversation, either an open-ended system or one you built
One engineer in CoderPad
The same live-coding style, inside the final loop