AI Changed How Spotify Builds. What We Learned (and Fixed) About Quality at Higher Velocity · Tyson Singer, Head of Technology and Platforms, SVP, Spotify · Spotify Engineering, September 16, 2026
Spotify looked for an AI quality signature in its own incidents and did not find one
Spotify says it added two questions to its monthly major-incident retrospective during its AI ramp-up: whether AI-authored code contributed directly, and whether the increased volume of change pressured review, testing, rollout or observability. Across the incidents reviewed it reports no AI-authored code as a material direct contributor. The second effect it does report: the volume of change increased faster than some of its verification controls could adapt. Merged changes more than doubled year over year in August, from roughly 8,100 to 17,000, with quality and optimization work rising from 27 percent of that mix to 31 percent and maintenance and configuration falling from 31 percent to 25 percent. Singer's summary of the whole exercise: "AI increased the capacity to produce change. The next constraint became our ability to verify it."
Two things sit behind that headline. Spotify rebuilt its rework rate metric to weigh the age of the code being changed, and sets its own flat result against the industry-wide rise in code churn reported by FAROS. That comparison is Spotify measuring against a metric it redefined and has not published the definition of, so it is not like for like. Separately, code complexity and pull request size are both creeping up, and Spotify declines to move the thresholds, writing that "we are deliberately not rewriting the thresholds to make ourselves feel better." The concrete failure it does name is an automated dependency upgrade that passed every safety check and still broke production, after which it expanded rollback capacity and began scheduling automated changes inside the owning team's working hours.
Why it matters: If code churn is the number you watch for AI-induced quality debt, Spotify is arguing that churn and rework answer different questions and that the age-weighted one is the better proxy. The thresholds point is the more transferable half. Complexity and diff-size limits were calibrated for what one person could hold in their head, and a team that quietly raises them because agents now produce larger units of work has removed a signal rather than fixed one.