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.
Table of contents
Dataset migrations can be painfulSimplifying fleet migrations with BackstageWith Honk, context is keyWhat did we learn for the futureSort: