Live data from Hacker News

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

cnbc.com

151–160 of 292 posts

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

#151
Good riddance. 7 years too late. I worked as a Google Cloud consultant for a major part of my career. We had this really large client, we were bleeding money because one of our ex-employees promised the client a cost reduction strategy that was impossible and I took over his role - literally a hot seat. We walked into Google's office, it was fantastic, they had something like 12 cuisines in the dining area, multiple game rooms with Table tennis and all. Sleeping rooms, you name it. It was more of a 5 star luxury resort experience than anything.

We walk into the meeting room, past the employee desks, over 50% of it was empty. I asked one of the colleagues showing us around where they all were - "they just work when they like!". Wow, what a dream! Google has/had? this rule where you can take some 20% of your time in a given day for yourself. But, mostly people used something like 40% of it in reality. I thought this was the perfect working culture with great work-life balance. I had very high expectations for the employee quality until I met the TLM and his team we were supposed to meet.

What a bunch of clowns. They suggested we use Cloud Spanner - one of the most expensive offerings at the time and our bottleneck (and bleeding) came from legacy MySql. He didn't even know that Spanner was more expensive than their Cloud SQL offerings, not to mention completely different offerings (it's No-SQL). None of them even knew when to use Spanner for and when to stick with SQL for. It was their own product line-up and we had more knowledge than them! I didn't pass any GCP exams even, at the time. That was the funniest part. We just needed help with some re-architecting of the client's application on a legacy PHP-MySQL combo. They didn't even have suggestions on what stack to migrate to! No idea whatsoever and they tried to talk their way out of it. In the middle of the meeting, my boss leaned over to me and told me "Neya, I think you probably know more than these guys, let's leave" and we wasted no time. To Google's credit, they did offer us some credits to use, but it was far too less than what were bleeding.

I went back to office and out of curiosity searched for how much these guys make - It was easily 120k - 250k (back then) depending on their experience. That's when I literally stopped trusting Google with anything at all. I could never be that laxed when I take that much money from anyone. Later, I learned a lot of these people were just there because depending on the country, you had to maintain a quota (ratio) of certain demographics within Google, most of the TLMs and their teams just conveniently fit into that. Why fix something that's not broke, right?

The Google we knew with the original startup culture was long dead and this story is atleast 7 years old now. For over 5 years since then, they did nothing but make money by simply increasing prices for GCP offerings. I remember our costs rising up suddenly after they just pulled the rug on us with Cloud storage price increase at random. No innovation, nothing. The AI mode they launched now after ChatGPT took the market by storm was what should've been 5 years ago. They are following the pattern exactly as described in the book we learned in our Masters' - "How the mighty fall" (really good book) and well deserved. You reap what you sow.

/endrant (thanks for reading!)

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

#152

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.

I was a TL and then a TLM in my org, and am now an EM. I'm actually pretty happy about it, personally. I am organizing an eng summit tomorrow between my team and a sibling team (which is onsite and visiting from elsewhere) in my org, and I noticed that about 18 months ago, I would have been the person to give 4 out of the 5 main talks at the summit (as the expert / TL on that system). Now it's five different eng. This tells me I've been able to nurture / elevate the other engineers on the team, get them all into technical leadership roles, and then have them reach out and be ready to talk about their work to other teams.

Overall: this is a good thing. By taking up less room on the technical side, I've replaced one of me with four strong engineers. Previously, I was split between TL work and EM work and as a result, did a half job of each, leaving too much un-done.

The other thing I'll note is that engineers are basically the only role with this distinction. Product Managers, Program Managers, Sales, Marketing, all those roles seem to combine management with seniority. Only on the engineering side do we have both a TL and Manager hierarchy (while typically the TLs for a team report to the same manager that the line manager for the team does, they exert authority differently). This works out okay on the eng side when there is a strong alliance between the TLs and the EMs, but that doesn't always happen.

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

#154

Earlier quoted context omitted.

When I started, I was told that one of the easier ways to get promo at L5 was to become a manager. I don't know how true that was at the time, but I think this could be a consequence of that sort of local optimizing. I think now they don't even allow you to be a manager at L5 unless you're grandfathered in?

Search and ads, at least, had the L6 requirement for manager going back as long as I’m aware. I was under the impression that the requirement was relaxed at some point in some of the less revenue critical orgs, but that the L6 restriction actually goes back a long way.

FWIW I was L5 manager (on the SWE ladder) in two PAs. The L6 requirement did exist but in my experience was quite soft. All that my management had to do was justify to the VP that I was capable of doing the job and would soon be ready for promo to L6 (though the first org got nuked and the promo took a long time).

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

#155
post #139

Earlier quoted context omitted.

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.

A few thoughts: (1) As an engineer, I prefer to be managed and guided by someone who actually knows what I work on, preferably better than I know it. (2) A manager who actually understands the tech is often better at unblocking the team. (3) Since senior IC openings tend to grow very thin as you become older, TLM path might be a viable career path for at least some. Can this role work if we don't expect IC output fro…

When you become a good enough IC, “ As an engineer, I prefer to be managed and guided by someone who actually knows what I work on, preferably better than I know it.” is no longer reasonable. Then your managers role is to maximize your ability to make an impact by putting you in the right place/project.

As a manager of people who know far more about the things they do than I do, my goal is to assist and ensure in the right place (for them and the org). It’d be foolish for me to hire peons who know less than me.

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

#157
post #95

So what does it mean exactly, they merged a bunch of teams?

Managers with fewer than three direct reports were either let go or forced to find new roles (typically as individual contributors, given the overall push to have fewer layers of management).

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

#158

Earlier quoted context omitted.

If you don't mind me asking, why did your team get bigger? Did your scope increase?

I assume you're referring to my other comment, since I didn't mention my team size in this one. I'd love to say that the answer is "because I'm a good manager", but I think that the real answer is "because there was money=headcount available, the layers of management above me successfully presented our value and inflated our needs enough to convince a VP to give it to us, and my own manager physically did not have en…

I passed on a similar opportunity, kept the team small. This was back in the pandemic when headcount flowed freely. What you describe sounds about right. My experience is that having a capable team goes a long way creating those expansion opportunities.

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

#159
post #144

Earlier quoted context omitted.

> But the huge perk of management is leverage. If you're technically competent and credible, and want something to happen, your team will see it your way. If you're a random "ideas guy" in an IC role, that's not a given. There are three levers of power in an organization - relationship, expertise and role. Role power is by far the least effective. If you can’t get team buy in for your ideas or they believe you’re an…

> Role power is by far the least effective. Eh, maybe at faangs or at the executive level but at non faangs you might not notice a role having power because most roles with the Manager title are no longer actual managers but supervisors. I had more agency over where capital was deployed as a teenager deciding how many people were going to be on the shift for closing, then I have making over 200k/yr as a Senior Manage…

The article is mostly about first level managers. I’ve never had any “manager” that really has any power over raises more than 3-4% or any real control over budgets.

When I was being hired as a strategic hire for startups - and was being interviewed by the director or CTO - I specifically asked would I be reporting directly to them or another manager. I actually refused one job because I saw that the expectations they had from me and how far I was down in reporting structure was incongruous.

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

#160
First they laid off the non-technical employees. As a big tech company, Google needs to focus on coding. But that wasn't enough, so they laid off the middle managers in charge of coders. As a big tech company, Google needs to focus on coding. But that wasn't enough, so they laid off the low-level managers who were the domain experts on each product. As a big tech company, Google needs to focus on pure coding, and anyone who isn't doing 100% coding is extraneous. But, that won't be good enough, so next they'll lay off the senior engineers. As a big tech company, Google needs to focus on coding, and senior engineers spend too much time doing "architecture" (whatever that means). But that won't be enough, either. So they'll lay off the regular engineers, too. As a big tech company, Google needs to focus on only the purest coders, meaning junior engineers who don't actually understand the product (understanding the product considered harmful). But that won't be enough. So they'll lay off all of the juniors and only keep one guy named Greg who will adopt the title "webmaster of google dot com" and rewrite the whole thing in PHP. Then this big tech company can really prosper!
Post reply on HN