S

Spotify

Streams music, podcasts and audiobooks

Staff Backend Engineer - Content Platform

Backend EngineeringConfirmed live in the last 24 hours
Full-timeNo salary listed

About the Job

Requirements

  • Deep experience designing and operating large-scale distributed systems, APIs, event-driven pipelines, rule engines, and decision systems in production across high-throughput environments.
  • Proficiency in backend engineering at scale, with strong command of languages such as Java, Kotlin, or Go, and ability to own data models, service contracts, and storage-layer decisions.
  • Experience with stream processing and event-driven architectures such as Kafka, Pub/Sub, or equivalent, and understanding of tradeoffs between batch and real-time enforcement pipelines.
  • Experience designing systems where schema and contract stability matter as much as correctness.
  • Experience with workflow orchestration and distributed coordination, through orchestration frameworks such as Temporal or Airflow, choreography-based event systems, or hybrid approaches, and understanding of tradeoffs in long-running, stateful enforcement workflows.
  • Experience with relational and non-relational storage systems and data modeling for auditability, immutability, and efficient querying at scale.
  • Understanding of platform engineering patterns, including multi-tenant APIs, configurable rule engines, policy-driven actioning systems, and designing for multiple teams.
  • Familiarity with observability and operational excellence, distributed tracing, structured logging, alerting, and tools for debugging and auditing enforcement systems in production.
  • Experience in regulated or compliance-adjacent environments and understanding of the legal and audit consequences of infrastructure design decisions, log retention, schema choices, and data lineage.
  • Comfort working in polyglot environments and thoughtfully navigating existing systems rather than defaulting to greenfield rewrites.

Responsibilities

  • Define the technical direction for policy enforcement infrastructure.
  • Architect enforcement capabilities as a shared platform for consumption by multiple product teams.
  • Design and evolve multi-signal orchestration systems that enable configurable, auditable policy enforcement at scale across content types and product surfaces.
  • Build the data foundation that makes enforcement decisions durable and reusable.
  • Own API and contract decisions, including schema design, versioning strategy, and how enforcement interfaces evolve without breaking dependent teams.
  • Establish integration standards for teams onboarding onto shared enforcement infrastructure and work directly with consuming teams to execute migrations with clean cutoffs and clear end states.
  • Influence architecture across detection, signal processing, and enforcement workflows so that underlying primitives remain coherent as the platform scales.
  • Mentor engineers and set standards for reasoning about API design, data modeling, and downstream compliance consequences of infrastructure choices.

About the Company

Spotify

Streams music, podcasts and audiobooks

Spotify runs an audio streaming service where listeners find music, podcasts, and audiobooks through one account on phones, computers, and connected devices. Its Discover Weekly playlist recommends songs based on listening habits, alongside playlists made by editors and artists. Listeners stream on demand, save favorites, share playlists, and download eligible content for offline listening through paid plans. The business earns subscription fees from Premium members and advertising revenue from its free service, while separate creator tools support publishing, audience measurement, and promotion. Spotify was founded in 2006 and is headquartered in Stockholm, Sweden.

Company size
5,001-10,000
Company stage
IPO
Headquarters
Stockholms kommun, Sweden
Founded
2006

Recently Posted Jobs

Explore more opportunities at Spotify

See more jobs