Time since we first saw it
Day 35
Similar jobs usually come down between day 6 and day 54.
At Spotify, jobs usually come down by about day 39.
From 11,453 similar postings that came down, and 43 of Spotify’s. Coming down is not always a hire.
Backend Engineer - Data Platform
Stockholm
Live, first seen by us 35 days ago- Pay
- Pay not listed
- Work setting
- Not stated
- Employment
Permanent — employment source
Employment type Permanent
Employment type in the employer’s posting: Permanent
From the employer’s posting
What you’ll work on
Full postingDesign, build and operate backend services and APIs for the data catalog and lineage
Develop batch and streaming pipelines that keep metadata current from platform events and audit logs
Turn team needs into technical designs and drive them through delivery and rollout
Take part in on-call for critical services and build in observability and quality checks
From the employer’s posting
Design, build and operate the backend services and APIs behind our data catalog, lineage and publishing systems
Develop and run the batch and streaming pipelines that keep our metadata current, processing platform events and audit logs
Turn what the teams using our platform need into technical designs, drive them through delivery and rollout
Take part in on-call for critical services, build in observability and quality checks by default
What you’ll bring
All qualificationsCore experience
- Solid experience building and running backend services and APIs in production with Java
- Comfortable with SQL
- Experience with data pipelines or a cloud data warehouse such as BigQuery, Snowflake or Databricks
- Working understanding of orchestration, metadata management, data quality, governance and lineage
Preferred experience
- Hands-on experience with batch or streaming frameworks like Beam, Flink or Spark is a plus.
Qualification wording
solid experience building and running backend services and APIs in production with Java
You're comfortable with SQL
have worked with data pipelines or a cloud data warehouse such as BigQuery, Snowflake or Databricks
You have a working understanding of data engineering concepts such as orchestration, metadata management, data quality, governance and lineage.
You're comfortable with SQL and have worked with data pipelines or a cloud data warehouse such as BigQuery, Snowflake or Databricks. Hands-on experience with batch or streaming frameworks like Beam, Flink or Spark is a plus.
Posting record
Report an error- Status in our records
- Live
- First seen by us
- Oct 3, 202635 days ago
- Recorded sightings
- 49
- Last seen by us
- Nov 6, 2026
- Employer says posted
- Sep 28, 2026
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
How this job compares
Spotify is hiring
16 open jobs
Open jobs by the week we first saw them, last 12 weeks.
- Hiring at a steady pace
- Takes jobs down at a usual pace
See how this role fits your experience
Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
- Java
- SQL
- BigQuery
- Databricks
- Iceberg
- Snowflake
- Spark
Where the posting names them
Who You Are - You have solid experience building and running backend services and APIs in production with Java, and you care about API design, versioning and backward compatibility. - You're comfortable with SQL and have worked with data pipelines or a cloud data warehouse such as BigQuery, Snowflake or Databricks. Hands-on experience with batch or streaming frameworks like Beam, Flink or Spark is a plus.
- You have solid experience building and running backend services and APIs in production with Java, and you care about API design, versioning and backward compatibility. - You're comfortable with SQL and have worked with data pipelines or a cloud data warehouse such as BigQuery, Snowflake or Databricks. Hands-on experience with batch or streaming frameworks like Beam, Flink or Spark is a plus. - You have a working understanding of data engineering concepts such as orchestration, metadata management, data quality, governance and lineage.
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. What You'll Do
Your next step
Complete your application on jobs.lever.co. The employer’s form will show what is required.
Applying through Lever
- No account needed: one form, and Lever reads your resume into the profile recruiters search.
Already applied? Track this application
Has Spotify posted this job before?
Yes. We’ve followed one other Backend Engineer - Data Platform job there since October 2026. It is still up.
Demand for Data Engineer roles
New Data Engineer postings at the employers we follow are up 8% over the last 5 weeks compared with the 5 before.
Each bar is one week of new postings. The darkest bars are the last 5 weeks.
Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.
About the role
We file this job under Data Engineer, by the work the posting describes.
Data engineers build and run the pipelines that copy data out of apps and outside services into a warehouse or lake, and fix them when a source changes or a load fails.
Expect SQL, Python, a cloud platform, a scheduler such as Airflow, and often tools for large data such as Spark or Kafka.
An analytics engineer works one step later, turning the raw data a data engineer lands into clean tables people can query.
US government figures for database architects
- Median yearly pay, May 2025
- $139,500
- Expected change, 2025 to 2035
- 9.4% more jobsagainst 3.5% for all jobs
The government has no code for data engineers, so these figures are for the closest group, database architects, which includes data integration and data warehousing specialists.
Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.
Job description
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.
What You'll Do
- Build and Evolve Core Services: Design, build and operate the backend services and APIs behind our data catalog, lineage and publishing systems, and evolve them as the platform adopts new storage technologies and new kinds of data. Hold them to a high bar for correctness, performance and reliability.
- Build Data Pipelines: Develop and run the batch and streaming pipelines that keep our metadata current, processing platform events and audit logs to capture how data is created and changed, and turning lineage and metadata into data products other teams build on.
- Own Projects End to End: Turn what the teams using our platform need into technical designs, drive them through delivery and rollout, and own the results once they're in production.
- Keep the Platform Healthy: Take part in on-call for critical services, build in observability and quality checks by default, and use automation, including AI tooling, to reduce toil for the team and our users.
Who You Are
- You have solid experience building and running backend services and APIs in production with Java, and you care about API design, versioning and backward compatibility.
- You're comfortable with SQL and have worked with data pipelines or a cloud data warehouse such as BigQuery, Snowflake or Databricks. Hands-on experience with batch or streaming frameworks like Beam, Flink or Spark is a plus.
- You have a working understanding of data engineering concepts such as orchestration, metadata management, data quality, governance and lineage.
- You break problems down into clear, shippable steps, reasoning through tradeoffs and risks and converging on clear recommendations.
- You own the quality of what you ship, including code written with AI assistance, and you care about operating it well after launch.
- You are a strong communicator and collaborator who enjoys working across teams, and you're comfortable in a dynamic platform environment where many engineers depend on what you build and priorities evolve with the business.
Where You'll Be
- This role is based in Stockholm or London.
- We offer you the flexibility to work where you work best! There will be some in person meetings, but still allows for flexibility to work from home.
Spotify is an equal opportunity employer. You are welcome at Spotify for who you are, no matter where you come from, what you look like, or what’s playing in your headphones. Our platform is for everyone, and so is our workplace. The more voices we have represented and amplified in our business, the more we will all thrive, contribute, and be forward-thinking! So bring us your personal experience, your perspectives, and your background. It’s in our differences that we will find the power to keep revolutionizing the way the world listens.
At Spotify, we are passionate about inclusivity and making sure our entire recruitment process is accessible to everyone. We have ways to request reasonable accommodations during the interview process and help assist in what you need. If you need accommodations at any stage of the application or interview process, please let us know - we’re here to support you in any way we can.
Employment type
Permanent
Source details
Source notes
Source excerptsSelected passages from the saved posting. Check the full description for conditions and exceptions.
- Pay
No pay amount identified in the saved description.
- Location & working pattern
Stockholm
Working pattern and location restrictions need checking in the full posting.
- Work authorization
No clear work-authorization passage found. Eligibility is unconfirmed.