Summary: Spotify’s Q4 2025 earnings call took place on February 10, and the headline numbers were pleasant enough: monthly active users hit a record high. Any team in the middle of rolling out coding agents has just been handed a specimen, and it deserves a proper dissection. The picture Söderström sketched on the call: an engineer on the morning commute opens Slack on a phone and describes a bug to Claude, or lays out an iOS feature request.
Spotify’s Q4 2025 earnings call took place on February 10, and the headline numbers were pleasant enough: monthly active users hit a record high. The remark that set the developer internet on fire, though, came from co-CEO Gustav Söderström, who said the company’s best developers “have not written a single line of code since December.” TechCrunch published its story on February 12, the quote traveled fast, and Business Insider, NDTV, and other outlets picked it up within days.
Nobody was being warmed up for layoffs. What Söderström described was a workflow already running in production: an internal system named Honk, paired with Anthropic’s Claude Code, replaces the old arrangement — engineers writing the code themselves — with a new one in which engineers direct the AI and sign off on what it produces. Any team in the middle of rolling out coding agents has just been handed a specimen, and it deserves a proper dissection.
Honk: Direct Claude From Your Phone, Ship Before You Reach the Office
The picture Söderström sketched on the call: an engineer on the morning commute opens Slack on a phone and describes a bug to Claude, or lays out an iOS feature request. Once Claude finishes, the fresh build comes back through Slack, and the engineer reviews, merges, and pushes toward production — all before the commute ends. Honk is Spotify’s internal layer that connects generative AI (Claude Code underneath) to remote, real-time code deployment, and the company says it has sped up coding and shipping “tremendously.” Claude Code, for context, is Anthropic’s flagship command-line coding agent — and on the day this article was published, Anthropic set Claude Sonnet 4.6 as the default model for free and Pro users. Put the two stories side by side and one conclusion is hard to escape: agent workflows have moved out of the experiment phase and into earnings-call numbers.
What the Best Engineers Do Now: Supervising AI
Söderström did not present the system as sorcery. The AI, he stressed, “still makes a lot of errors,” and that is precisely why developer supervision stays in the loop — the top developers now watch over AI output rather than type it themselves. An engineer’s value is migrating accordingly, away from typing speed and toward problem definition, review, and acceptance. He put his conclusion in blunt terms: “We foresee this not being the end of the line in terms of AI development, just the beginning.”
More Than 50 Features Shipped in a Year
The numbers back the story. Through this pipeline, Spotify said, it delivered more than 50 new features and changes to the streaming app over the course of 2025. AI-powered launches from recent weeks include Prompted Playlists, Page Match for audiobooks, and About This Song. The message from the call was consistent on this point: AI is not merely changing the recommendation system — it is changing the cadence of software delivery itself.
The Moat Question: Music Taste Has No Single Right Answer
Pressed on the threat from AI giants, Söderström gave an answer that rewards a slow read: music preference has no single correct answer. The same workout-playlist request surfaces hip-hop for many Americans and death metal for some of them, EDM across much of Europe, and heavy metal for plenty of Scandinavians. Data of that kind cannot be commoditized the way encyclopedic facts can — hence his claim: “This is a dataset that we are building right now that no one else is really building.” On AI-generated music, artists and labels can flag in track metadata how a song was made, while the platform keeps policing itself for spam.
Sober Read: Marketing Narrative or Genuine Workflow Shift?
Not everyone bought it. Over on Reddit’s r/programming, engineers found the “best developers haven’t written code” framing funny, and some half-joked that this was really CEOs playing the stock market. Two readings hold up better than the mockery. First, even granting that the narrative is polished, the direction tracks the capability curve of tools like Claude Code — the open question is pace, not destination. Second, the moment merges can happen from a phone, the review process, deployment permissions, and audit trails stop being back-office concerns and move to the core of the product. Spotify can only operate this way because Honk already builds those guardrails into the pipeline. For most teams, that — not the headline quote — is the part genuinely worth copying.