AI Changed How Spotify Builds. What We Learned…

On June 24 a batch job competing with new episodes, a recent quality fix that raised per-episode compute, and a scheduling bug cutting throughput about 10% combined to delay episodes normally published within minutes by several hours.

Fix for the June 24 incident: end-to-end monitoring so failures surface before creators notice, a fixed scheduler, batch jobs moved to lower priority, added capacity, and reworked tiering so new uploads take precedence when capacity is constrained.

An automated dependency upgrade passed Fleet Management's safety checks but still broke production. Spotify responded by strengthening rollback capacity and scheduling automated changes during the owning team's working hours, not slowing automation.

Across reviewed production incidents, Spotify did not find AI-authored code to be a material direct contributor, but the increased volume of change outpaced verification controls (review, testing, rollout, observability), which the team is now strengthening.

Merged PRs more than doubled year over year (about 8,100 to 17,000), and quality/optimization work rose from 27% to 31% of that mix, so engineers put over twice the absolute effort into quality; rework rate stayed flat despite a wider industry churn rise.

Intel

AI Changed How Spotify Builds. What We Learned (and Fixed) About Quality at Higher Velocity