Skip to content

Backend Engineer - Data Platform

Spotify (Lever)StockholmHybrid

First seen Sep 28 · open 54 days · posted onceNo pay listed

HirQ verdict

54/100 · Fair. Based on age, reposts, pay, the company's hiring and ghost signals.

Low ghost risk
True age
54 days
Reposts
Posted once

See the evidence behind this score.

Pro shows each part of the score, the reasons, the pay percentile and the listing history.

HirQ's ghost-risk estimate and company labels are automated opinions based on what we observe on employers' public job boards: how long a listing has been open, whether it was re-listed, wording in the description, and how often roles on that board close. They are not statements about an employer's intent, and a high-risk listing can still be a real opening. Figures are as of the date shown. How we measure

At a glance

Pay
No pay listed
Level
Mid level
Type
Permanent
Team
Platform
Work setup
Hybrid

“Stockholm”

Spotify (Lever) hiring

Company page
Actively hiringHiring60· FairMedia, Gaming & Entertainment
Open roles
91
New in 30 days
37
Closed in 30 days
46
Hiring trend, 13 weeksPro
Follow-through: ••%Pro

About the role

From Spotify (Lever)'s careers page, checked Nov 21

Every dataset at Spotify, from the data behind creator royalties to the signals powering recommendations, is registered, published and traced through systems our team builds. We're the source of truth for what data exists at Spotify, where it lives, who owns it, and how it flows from one pipeline to the next.
These systems sit on the critical path of the platform. Data teams use them every day to publish and find data, and other platform teams build on them for access, retention, governance and incident response. That means our work is judged on correctness and reliability, because every system built on top of ours is only as good as the metadata we provide.
This is a backend role focused on data management, working on the problems at the core of any large data platform: running a data catalog that stays accurate at scale, capturing lineage across batch and streaming workloads, managing schemas as they evolve, and guaranteeing that consumers only read complete data. We build on open standards like OpenLineage and Apache Iceberg, and define the internal standards for naming, storage and metadata that the rest of Spotify builds against. As the platform takes on new storage technologies and new kinds of data assets, those standards and the systems behind them have to evolve with it, and you'll help decide how.

Skills mentioned

  • Incident Response
Apply on Spotify (Lever)'s siteOpens Spotify (Lever)'s own application page.

Similar jobs

Same role or field, nearby or remote, ranked by HirQ score.

More at Spotify (Lever)

All roles

Keep exploring

Backend Engineer - Data Platform

No pay listed · HirQ 54

Apply