Spotify has no L-codes.
Seven named bands, and the top two publish no pay.

The entry rung as levels.fyi renders it: a new individual contributor executing well-scoped work with close support while learning the codebase, the release process, and the domain. Treat this band as the least certain on the page. It appears on levels.fyi but has not been observed in any Spotify job ad, so it may be a normalization rather than a band Spotify hires into under that name.

Lead with internships, projects, and open-source work, each paired with a measurable result rather than a tool list. levels.fyi reports an average total compensation of $137,729 (base $122,419, stock $15,310 a year, no bonus reported) in a range of $120K to $170K+. That is a self-reported average, not a median, accessed 2026-08-04, and not official Spotify compensation. Because the rung itself is unconfirmed in Spotify postings, treat this as the weakest figure on the page.

The first band that appears in Spotify's own reqs, for example iOS Engineer I, Subscriptions. Owns well-defined pieces of a product surface with review and support around them, and is building context on the systems rather than setting their direction.

Show that you shipped something users touched, end to end, with one number attached to it. levels.fyi reports an average total compensation of $160,666 (base $140,197, stock $19,787 a year, bonus $682) in a range of $133K to $181K+. Self-reported average, accessed 2026-08-04, not official Spotify compensation.

The mid-level individual contributor band, confirmed in postings such as Machine Learning Engineer II, Personalization. Owns features and components independently, is a dependable reviewer for part of the codebase, and starts making design calls without being asked to.

Ownership plus judgment: a component you owned, a decision you made and the reason behind it, and the result in numbers. levels.fyi reports an average of $224,218 (base $185,640, stock $37,752 a year, bonus $826) in a range of $195K to $247K+. Self-reported average, accessed 2026-08-04, not official Spotify compensation.

Confirmed in postings such as Senior Engineer, User Platform. Owns systems rather than features, sets the technical approach inside a team, and raises the quality of the engineers around them. The scope question shifts from what you built to what you decided.

Write at system altitude: the system you owned, the decision you made, the load or the users it served, and the measured outcome. levels.fyi reports an average of $283,179 (base $240,396, stock $42,604 a year, bonus $179) in a range of $240K to $334K+, with a New York cut averaging $282,205. Spotify's own posted range for Senior Software Engineer, Platform Infrastructure in New York was $164,448 to $234,926 base plus equity before that req was removed on 2026-06-25. The levels.fyi numbers are self-reported averages accessed 2026-08-04; the posted range is base only and comes from Spotify.

Confirmed in live postings and in Spotify engineering blog bylines, including Anna Smith as Staff Engineer. The reqs describe driving technical direction in ambiguous problem spaces, contributing to long-term platform architecture, and mentoring engineers to raise the bar across the team; that mentoring line is verbatim from a Staff machine learning req, so read the discipline wording as job-family specific. This is also where Spotify's own posted numbers stop behaving like a single band.

Lead with ambiguity resolved and architecture set, not volume shipped. levels.fyi reports an average of $403,809 (base $292,698, stock $111,111 a year, no bonus reported) in a range of $306K to $516K+, with a New York cut averaging $416,897 ($360K to $516K+). Spotify's own posted Staff base ranges span $203,410 to $324,993 across three verified New York reqs, roughly a $120K spread depending on the job family. levels.fyi figures are self-reported averages accessed 2026-08-04; the posted ranges are base only and come from Spotify.

Spotify engineering blog bylines carry this band twice: Dave Zolotusky as Senior Staff Engineer in 2020, and Max Charas as Senior Staff Engineer on 2025-11-06. It appears in Spotify reqs, and one Staff req describes the hire collaborating with Engineering Managers, Staff and Senior Staff Engineers, so the two bands demonstrably coexist inside one org. The reqs put this band on strategy: shaping the machine learning strategy for content understanding and platform-level decisioning, at global scale.

Write about the strategy you set and the systems other teams built against, at a scale you can name. No compensation figure is stated here. levels.fyi renders no number for Senior Staff Engineer and its submission table is empty, so there is nothing to average and nothing to interpolate from the band below. The only public number attached to this band is Spotify's own posted base range on a single New York machine learning req, which appears in the posted ranges table further down this page.

The top of the verified ladder, and the only band with zero open reqs on Spotify's board. Its existence is settled by bylines rather than postings: Marc Bruggmann is credited as Principal Engineer on Spotify's engineering blog on 2025-11-06, and Dave Zolotusky is billed at KubeCon as Principal Engineer, Spotify. Nothing above Principal is verified, so nothing above it is listed here.

There is no external application path to price at this band and no compensation figure is stated. levels.fyi renders no number for Principal Engineer and its submission table is empty. Zero open reqs alongside two named Principal Engineers is the pattern of a band filled by internal promotion rather than external hire, and absence of a req is not absence of the level.