The Middle-Management Purge: How Silicon Valley is Flattening the Corporate Hierarchy

Over the past two years, a particular type of meeting has been taking place inside big tech companies; it usually takes place on a Tuesday or Wednesday morning, frequently via video call, and occasionally with HR on the line. A manager with six direct reports, ten years of experience, and a strong performance record is informed that the company is “streamlining its organizational structure.” What that means, in practice, is that they are being asked to either absorb someone else’s team or accept a role that involves no management responsibilities at all. Just execution. Hands on the keyboard, no one to report to, just code, content, or data.

Silicon Valley has been moving to flatten its corporate hierarchies for years, but something shifted around 2023, and it hasn’t slowed down since. First, the language was altered. In a public statement, Mark Zuckerberg expressed his disapproval of “managers managing managers, managing managers, managing the people who are doing the work.” Andy Jassy at Amazon ordered a 15% increase in the ratio of individual contributors to managers. Google’s Sundar Pichai announced a 10% cut in vice president and manager roles as part of what the company called an efficiency push. Intel’s new CEO, Lip-Bu Tan, put it more bluntly in a memo to staff: “The best leaders get the most done with the fewest people.”

The logic, stripped of its corporate language, is straightforward enough. Hierarchies slow things down. Every decision that has to travel up three layers of management before it comes back down costs time, and in industries where competitive windows close in months rather than years, that cost is real. Deborah Ancona, a management professor at MIT, described it as an organization problem that’s always existed but now has new urgency: companies exist in an exponentially changing environment, she said, and traditional hierarchies were built for a world that moved more slowly. You can’t move fast if every call requires consensus from a chain of people who weren’t in the room when the problem was identified.

It’s hard not to notice, though, that “efficiency” and “cost-cutting” are doing a lot of work in the same sentence, and that the distinction between them has gotten blurry. Middle managers accounted for nearly 29% of layoffs in 2024 — a number that’s risen sharply from 19.7% in 2018. Meta’s much-praised “year of efficiency” involved laying off roughly 21,000 people across two rounds. It was richly rewarded by the stock market. Meta’s market capitalization surpassed $1 trillion. At least Wall Street appeared to accept the reasoning.

Key Reference Data: The Middle-Management Flattening Trend

A more nuanced account is provided by those who are actually going through the transition. Yvonne Lee-Hawkins, a former Amazon HR manager, found herself assigned 21 direct reports after a round of organizational changes. She’d done 11 before. The weekly one-on-ones that she’d used to track performance, surface problems, and provide mentorship became logistically impossible — she cut them in half, then struggled to make even that work. An AWS manager who spoke to Business Insider described something similar: flatter structure, more reporting burden on individual employees, more time in meetings as she tried to stay across a more diverse group of direct reports. These are not impersonal issues. They occur when a layer of management is removed without completely redistributing the tasks that layer was carrying out.

Jensen Huang of Nvidia is well-known for overseeing sixty direct reports. That figure, which is alternately regarded as proof of concept and proof of an almost superhuman operating capacity, is circulated in tech circles with a sort of reverent disbelief. A goal of 15 to 20 reports per manager has been set by Dell. According to an internal document from Amazon Web Services, each manager was required to have at least eight, up from six. The quality of a manager matters far more than the number of people they oversee, according to Gallup’s research, which raises the unsettling possibility that the concept of “optimal span of control” as a whole is flawed. A mediocre manager with six reports might perform worse than a great manager with fifteen.

However, this does not imply that providing 15 reports to every employee results in excellent management.
The career pipeline issue is one aspect of this that the efficiency narrative frequently ignores. Despite its organizational shortcomings, middle management has traditionally been where junior staff members learned how to lead. An engineer or analyst with potential could take on a small team, make some mistakes at a manageable scale, and develop the judgment that senior leadership demands. When you remove that layer, decision-making at the top is accelerated and the training ground for future decision-makers is subtly eliminated. According to Jane Edison Stevenson of Korn Ferry, flat organizations may elevate high performers, but they frequently fall short in producing leaders capable of coordinating across an entire organization rather than just performing exceptionally well within a single vertical.

Observing this trend in Google’s product management layers, Amazon’s operations teams, and Microsoft’s engineering ranks gives the impression that it’s partially structural correction and partially something less deliberate. According to several accounts, Microsoft had built up layers of management over the years by pushing talented engineers into positions for which they weren’t especially qualified. It makes perfect sense to fix that. Efficiency memos don’t address the questions raised by the larger industry rush to flatten, which is occurring concurrently at twelve major companies and is frequently motivated more by investor pressure and earnings optics than by a true organizational diagnosis.

Bayer CEO Bill Anderson, who implemented what he calls a “dynamic shared ownership” model after taking over in 2023 — cutting thousands of managers and having employees work in 90-day project networks — framed it as a response to a fundamental absurdity: hiring highly educated, trained people and then surrounding them with eight layers of hierarchy and wondering why big companies feel so slow. It’s a valid criticism. However, it’s also possible that the remedy being used now, widely and swiftly throughout a large portion of the tech sector, is quicker than the reasoning behind it.
Those in those Tuesday morning meetings most likely have an opinion on that. Simply put, no one is currently in charge of enough employees to ask them.