Database › Spotify
Spotify
Spotify publishes engineering posts about its background coding agent (Honk). No mandate has been reported.[1]
Tools
- Honk (internal background coding agent)[1][2]
- Fleet Management / Fleetshift (internal)[1][2]
- Backstage[2]
Metrics tracked
- Spotify counts merged agent-generated PRs and estimates the engineering weeks saved on migrations.[1][2]
Guardrails
- Agent changes go through verification loops before PRs are opened, including an LLM-as-judge check on diffs.[1]
- Downstream owning teams still did their own manual testing before merging the automated migration PRs.[2]
Hiring, reviews & process changes
Nothing verified from a public source yet. Know a source?
Reported results
- Spotify says the background agent has merged 1,500+ PRs, and that Fleet Management has automated roughly half of its PRs since mid-2024.[1]
- Spotify rolled out 240 automated dataset-migration PRs, saving an estimated 10 engineering weeks.[2]
Metric tags: PR throughput, Time saved
Editor's note: Dates are month-level, taken from the URL paths. The day was not found on the pages.
Sources
- Spotify Engineering: Spotify's background coding agent (Part 1) · 2025-11 · company source
- Spotify Engineering: Background coding agents and dataset migrations (Honk, Part 4) · 2026-04 · company source
Last verified 2026-10-25. Industry and size are editorial bands; see methodology. Spot an error? Submit a correction.