# Read Spotify's AI engineering figures carefully

> Distinguish assisted code contributions from claims that engineers no longer write software.

Source: https://fullbytedeveloper.com/blog/spotify-ai-assisted-engineering
Originally posted: 2026-02-16
Published here: 2026-11-06

Spotify reported at its May 2026 Investor Day that 99% of its engineers used AI weekly and more than 73% of code contributions were AI-assisted. These are company-reported adoption figures. [1]

They do not mean that every contribution was generated entirely by a model or that engineering review disappeared.

## Measure the work you care about

For your own team, choose a repeated task and record the time from request to an accepted, tested change. Include the review and rework. Comparing only the time to produce a first draft misses much of the cost.

Keep the task definition and acceptance checks consistent across the comparison. Track defects found after merge as well as the amount of code produced.

## Keep responsibility visible

Name the person who reviews and accepts each change. An agent can generate an implementation, but someone still needs to decide whether it solves the requested problem.

Use Spotify's figures as evidence of its adoption. Use your own completed changes to decide whether a workflow helps your team.

## Sources

1. [Spotify 2026 Investor Day recap](https://newsroom.spotify.com/2026-05-21/investor-day-recap/)

## Original posts

- [Instagram post](https://www.instagram.com/fullbytedeveloper/p/DU0nes0jDBt/)