Spotify
Backend Engineer II - Data Platform
Salary not posted. The employer did not include pay in this listing. Ask for the range in your first conversation; it is a fair question.
Posted 6 days ago · listed on Lever
Should you apply?
- Open
- 7 days
- Fresh. First-week applicants get read first.
- Open roles at this company
- 86
- Hiring in volume. Recruiters are busy, so a tailored resume that matches the posting's words gets through the screen.
- Salary
- Not posted
- No range in the posting. Ask early. It is a fair question and it saves everyone time.
Days open comes from the posting date. Fill time and reposting rate come from this company's recent public postings.
About the role
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.