This is part 4 in our series about Spotify's journey with background coding agents (internal codename: “Honk”) and the future of large-scale software maintenance. See also , , and .

The Spotify Engineering Blog provides  insights, technical deep dives, and behind-the-scenes stories from the engineering team at Spotify. Covering a wide range of topics, including backend systems, data processing pipelines, and frontend architecture, the blog offers a glimpse into the technology stack and engineering practices used to power one of the world's leading music streaming platforms. Developers can learn about scalable infrastructure solutions, innovative engineering techniques, and best practices for building high-performance software systems. By following the Spotify Engineering Blog, developers can gain inspiration, knowledge, and practical insights to apply to their own projects and endeavors.

Spotify Labs

Part 4 of the series on how background coding agents work at scale. A case study of how a team at spotify used their internal AI coding agent ("honk") alongside backstage and fleet management tools to automate migrations of ~1,800 downstream data pipelines from deprecated datasets to new versions. The effort saved an estimated 10 engineering weeks. Key lessons include the importance of context engineering, standardization across pipeline frameworks (BigQuery Runner, dbt, and the more variable scio), and the need for automated testing to enable agent self-verification. The team successfully rolled out 240 automated migration PRs, with future plans to let the agent gather its own context from jira and documentation.

Background Coding Agents: Supercharging Downstream Consumer Dataset Migrations (Honk, Part 4)

Simplifying fleet migrations with Backstage