←back to thread

Google has eliminated 35% of managers overseeing small teams in past year

(www.cnbc.com)
574 points frays | 1 comments | 27 Aug 25 21:16 UTC | HN request time: 0.331s | source
Show context
AnotherGoodName ◴[27 Aug 25 22:01 UTC] No.45045883[source]▶
This was called the TLM role at google. Technical Lead/Manager. You were expected to code and manage a couple of more junior engineers.

It’s part of an effort to have dedicated managers and dedicated engineers instead of hybrid roles.

This is being sold as an efficiency win for the sake of the stock price but it’s really just moved a few people around with the TLMs now 100% focused on programming.

replies(15): >>45045891 #>>45046165 #>>45046216 #>>45046446 #>>45046469 #>>45046545 #>>45046627 #>>45046811 #>>45047198 #>>45047268 #>>45048052 #>>45048255 #>>45048293 #>>45048558 #>>45049014 #
corytheboyd ◴[27 Aug 25 23:13 UTC] No.45046446[source]▶
TLM role has always sounded like a trap to me, I would never say yes to it personally. I’m sure it’s sold as an expected 50% code, 50% management but everyone I’ve talked to who has been near it says the expectation is more like 80% code 80% management.
replies(5): >>45046592 #>>45046770 #>>45046997 #>>45047867 #>>45048059 #
xenotux ◴[27 Aug 25 23:34 UTC] No.45046592[source]▶
TLM roles are a trap, but not in that sense. There's no expectation that you do two jobs at once.

It's just a way to ease unsuspecting engineers into management. If you don't suck at management, your team inevitably grows (or you're handed over other teams), and before long, you're managing full-time.

Which means that there are three type of people who remain TLMs in the long haul: those who suck at management; those managing dead-end projects on dead-end teams; or those who desperately cling on to the engineering past and actively refuse to take on more people. From a corporate point of view, none of these situations are great, hence the recent pushback against TLM roles in the industry.

replies(4): >>45046606 #>>45047808 #>>45048629 #>>45049028 #
kelnos ◴[28 Aug 25 06:19 UTC] No.45049028[source]▶
> There's no expectation that you do two jobs at once.

I laughed out loud when I read this. I've never seen anyone at any company in a hybrid tech/manager role that wasn't expected to do two jobs at once. Or at least they felt like they were, which is still the same problem.

80% coding & 80% management for that role sounds about right.

replies(6): >>45049304 #>>45049314 #>>45050846 #>>45051406 #>>45052472 #>>45056533 #
1. jll29 ◴[28 Aug 25 12:37 UTC] No.45051406[source]▶
Management requires a birds-eye view of the project in all its breadth, and quickly responding to issues, as well as reporting up (proactive stakeholder management). The job of the manager is to keep the CXOs happy (inform/manage expectations) whilst protecting their own team so they can focus on getting their work done with minimal disruption (isolate).

Coding requires the opposite, zooming deeply into the code and retaining focus. The job of the IC coder is to deliver (design and implement) beautiful and pragmatic architectures that do what is expected.

I recommend anyone to reject to fill roles where these two are combined into one. Note that this is not a comment about workload, but about irreconcileable differences. (The perfect candidates for each even match different personality profiles...)