If you weren't one of the 700, Brian Armstrong's restructure just changed your job description whether you agreed to it or not.
Armstrong's memo is explicit. Coinbase is eliminating pure management roles entirely. Every leader going forward is an "active individual contributor" and a "player-coach." The org caps at five layers. AI handles the coordination work that used to require a layer of people between you and the business.
Those left are no longer cushioned by a communication layer between them and management. Decision-making is more direct. Value-sharing vital.
Et Tu Coinbase?
In September 2024, Amazon CEO Andy Jassy wrote directly to staff instructing every S-team organisation to increase the ratio of individual contributors to managers by at least 15% by the end of Q1 2025. His reasoning was structural: fewer managers, faster decisions, ownership pushed deeper into the SWE role.
(Source: Message from CEO Andy Jassy: Strengthening our culture — aboutamazon.com, September 2024)
Meta went further. Its new applied AI engineering division (handling its superintelligence efforts) runs at a 50-to-1 employee-to-manager ratio, double the 25-to-1 figure widely regarded as the outer limit of managerial control.
(Source: Meta's new AI team has 50 engineers per boss — Fortune, March 2026, citing Wall Street Journal)
Now Coinbase. It's becoming a familiar pattern: flatten the structure, cut the coordination layer, trust the engineers left to take full ownership.
What has Disappeared?
For most of history, there has been a 'chain of command', an organisational hierarchy. Whatever one wants to call it, it showed up in software teams in an important way. There was always someone to translate the technical realm of engineering and code to the 'powers that be.' These managers ran the stakeholder meetings. They translated your technical decisions into language the business understood. They explained value upward while you were busy raising PRs and tuning performance.
That person is gone now. The most important gap to close is the communication one.
The VP needs to understand the cause for delays. The board still needs full confidence in the army of agents engineers are expected to control (a whole issue unto itself!). The shrinking pool of juniors still need context. Those conversations aren't going away, however much we might prefer it. Instead they are the new job description for 'Software Engineer.'
An Accelerating Trend?
The ability to communicate, facilitate, persuade, and influence was always part of the job. There were people doing exclusively this. But the best performing engineers were never just technical wizards, they were the people who could convince the organisation of their expertise and vision---those capable of executing it through their team.
Now the cover is gone and the requirement is only accelerating.
The engineers who thrive in this structure won't simply be the most technically skilled in the room. They'll be the ones who can hold a stakeholder relationship, make technical complexity legible to people who don't share their context, and advocate for their work without someone else doing it for them.
It just so happens that AI means the last excuse to ignore communication is gone. We have left the territory of 'soft skills' training. It's what we are hired to do.
Top comments (0)