Member-only story
They Decided to Fire 80% of Their iOS Developers
If AI Handles 80% of the Work, Why Keep a Full iOS Team?
The meeting was supposed to be about the next release. Instead, the engineering director put a different number on the screen: 14.
That was the size of the iOS team. “Do we still need all of them?” he asked, and nobody answered right away.
The team lead had walked in expecting a conversation about the release schedule, a couple of delayed features, and the backlog of technical debt everyone had been quietly ignoring. Instead, the conversation had jumped to something a lot more uncomfortable.
Over the previous few months, the team had leaned hard into AI coding tools — generating SwiftUI screens, writing tests, fixing compiler errors, wiring up networking code, and increasingly handing coding agents larger changes instead of small isolated pieces. Work that used to take several days was landing in one or two. Nobody was putting in fewer hours. They were just getting more out of the hours they already worked, and the director had clearly been tracking it: the backlog was shrinking, releases were easier to plan, and some of the smaller tickets that used to need a junior or mid-level developer were now getting handled by a senior developer working alongside…
