Google tried removing all managers in 2002. It lasted two months.
The Engineering Manager's role is under attack (again)
Engineering managers are being cut again as companies chase flatter orgs and wider spans of control, with Meta targeting a 1-to-50 ratio. Suzan Bond, who was laid off six times before becoming a COO, explains the erosion cycle: fewer managers means less people work, which makes managers look less valuable, which justifies cutting more. Google and Microsoft have run this experiment before and quietly rebuilt the layers. The fix starts with EMs translating team problems into obstacles to business goals.
They relented when too many people went directly to Page with questions about expense reports, interpersonal conflicts, and other nitty-gritty issues.
- scott_w
Reading Meta wants a 1:50 ratio is wild. Let’s put some simple numbers down.
I like a 30 minute 1-on-1 per engineer per week. At 1:50, 25 hours out of my 40 are now 1-on-1s.
Assume a usual team is 5 engineers, so I’m covering 10 teams, effectively.
So I have 15 hours to keep context of 10 teams. Am I expected to contribute as an IC, too? Usually when I’m directly leading a team, putting code into prod is how I feel the pain.
Finally: am I getting 10x the salary for doing the job of 10 EMs?
I’m all for cutting bureaucracy but is AI really this magical?
- arnvald
I used to work in an organization where a senior director had 2 direct reports, one of them being a director who had 2-3 direct reports (senior managers), and these senior managers had maybe 3-4 managers each.
Getting anything done was a nightmare because everyone up to the senior director level wanted to have an impact on the decision, so the approval process took ages.
When done right, the flattening is good (and I say it as a middle manager) - it should remove layers that don’t add value, and empower people at lower levels. In this case removing the senior director or director wouldn’t hurt the organization.
Unfortunately what I often see is that an organization will reduce number of people in one layer from 3 to 2, increasing the number of direct reports, but keeping the same number of layers leading to no improvements (besides cutting costs)
- okaleniuk
Maybe it should be under attack. I've been promoted to engineering management position two years ago and, as soon as I got rid of all the bullshit activities, the role itself dissolved.
Now I spend about two hours a week on regular syncs, an maybe another hour on average putting fires down. The rest of the time I do engineering along with my teammates. Needless to say, we are super productive in this setup.
- praptak
From my experience as a software engineer there is not enough management being done.
I'm talking situations like broken processes that everyone complains about but nobody has the power to change. Planning cycles that stack delays. Unclear ownership where anyone can block your request but no one can approve it.
I'm not saying this simply translates to "more managers". There obviously can be too many cooks. But I think currently we have too little and 50:1 is crazy, simply because 50 people cannot work as a single homogeneous group and you end up with TLs pretending they are not managers.
- maxipavlovic
It's the best time to be alive as an EM today. You at least have a chance to lead a team and do cool engineering without a complete burnout.
The ones who are attacked are most probably the enterprise-like comfort layers that uses Copilot instead of Claude Code (replace with a good tool that you like). And if I am wrong and our job is forced to do engineering again, I don't see that as a loss, sincerely.