Live data from Hacker News

Ask HN: 20% of LinkedIn's recent layoffs were managers

news.ycombinator.com

191–200 of 289 posts

Re: Ask HN: 20% of LinkedIn's recent layoffs were managers

#191
post #31

Earlier quoted context omitted.

>LI has a distinctive lack of chill right now contrary to the company image I don't get it. Did linkedin have an image of being a chill place to work?

Yes, absolutely. I worked there about 7-8 years ago and at the time it was considered a "retirement home" in Silicon Valley.

.

Re: Ask HN: 20% of LinkedIn's recent layoffs were managers

#192

Earlier quoted context omitted.

Surely this is because Elon is there picking up the slack for the missing 80%.

Or, you know, the people dealing with the advertisers ("partners") are gone and no money is coming in. But sure the servers are still running ;)

no idea why you need a dedicated person for dealing with the advertisers. it seemed to be just pressure from adl to scare the advertisers away, or otherwise adl will generate controversy

a very slimy and backwards model

Re: Ask HN: 20% of LinkedIn's recent layoffs were managers

#193

Earlier quoted context omitted.

I used to work for Large Tech Company and I would pretty frequently fly out to San Francisco Suburb for work. One of the more interesting time periods of that phase was when the office building I worked at for Large Tech Company was across the parking lot from LinkedIn in San Francisco Suburb . We frequently played a largesse game of hangman with the LinkedIn employees drawn on the windows across our parking lot. Lin…

That sounds suspiciously like the office location where you‘d see big cargo planes fly overhead once in a while.

In the 90's, the shadows of the P-3 Orions regularly flying out of Moffett Field to hunt for submarines would pass over my house and briefly darken my living room many times a day in Mountain View.

Re: Ask HN: 20% of LinkedIn's recent layoffs were managers

#194
post #107

Earlier quoted context omitted.

Having 17 direct reports is too much. Managers are not just a link in the chain of command. They also do stuff that needs to be taken care of. All kinds of unusal things happen and not all are suitable for delegation. 17 direct reports is not only a measure of how many colleagues they need to manage. It is also a measure of the large the weird-things-that-needs-taking-of-scope is.

Seriously. The most effective teams I've ever worked in, had 3-5 people under a manager. The manager occasionally got their hands dirty when they could spare the time, but in general, "getting every roadblock out of 5 people's way" is a lot of work, and combined with all the non-delegatable stuff, would keep them pretty busy. When a team grows much beyond that, the manager is no longer removing all the roadblocks. Th…

Was thinking about this in mathematical terms recently, in terms of what's efficient vs. what can scale. In general, managers can't do things for reports that don't scale fairly across their whole team, because otherwise it'll give the appearance of favoritism for those reports who get favors and demotivate the rest. So to a first approximation, a manager with N reports can devote at most 1/N of their time to making a report's job easier. (To a second approximation, it's more like 1/2N because the manager also has overhead tasks like 1:1s and performance reviews that scale with the number of reports. To a third approximation the denominator scales supra-linearly after about 10 reports because you start taking up all your time with management tasks and have literally zero time for project work.)

Their goal is to keep their report's time fully utilized, so it is logical for a manager to take on a task if it saves their report 2N as much time in IC work. For example, a manager with 4 reports can devote up to 10 hours/week fairly to each one; taking the second approximation, that's 5 hours of overhead and 5 hours of project work. The report has 40 hours/week of time. Therefore, it makes sense for the manager to do a one-hour task (say, design work) if it saves the report at least 8 hours of work. A manager with 10 reports can devote only 4 hours/week to each, so with 2 hours of overhead and 2 hours of project work, it makes sense to take on a one-hour task only if it saves the report 20 hours of work. Taking the third approximation and assuming overhead is a constant 2 hours/week/report, the first case becomes 8 hours of project work, and so a task makes sense if it saves the report 5 hours of work.

You can see how a manager very rapidly approaches the "Do nothing other than bare minimum performance reviews, 1:1s, and save the report from blatant stupidity" line as their reporting load increases. This is why so much moderate stupidity and waste persists in big companies: the manager is not incentivized to remove it (and doesn't have time to anyway), but the report does not have the organizational power to change it. And ironically flatter hierarchies tend to be worse at this, unless they have ICs step up and do the "improve efficiency for everyone" role, but then they're usually either promoted into management or they leave.

This is also why managers look chronically dumb and entitled to ICs. The IC can see plenty of opportunities where "If you just did X, which takes 15 minutes of your time, it would save me 2 hours of my time." They don't realize that their manager has 10 other reports, so a.) their manager does not have 15 minutes of time to spare and b.) their manager is only going to spend it if saves at least a day. Otherwise it makes more sense for the employee to do it themselves, simply from a scalability perspective.

Re: Ask HN: 20% of LinkedIn's recent layoffs were managers

#195

Earlier quoted context omitted.

> Typical ratio of people to managers in a company is about 1:4, so that tracks. Over the last 10 years, we have improved productivity tools, and for every other role the expectations are higher. I find it funny that the ratio of ICs:Managers has not gone up and the industry doesn't discuss that it should go up or what tools we need to help make it grow.

Productivity tools don't help you when dealing with people problems. You can't throw a TODO app or some other bullshit on someone who is underperforming or to coach someone for a promotion.

Is it a hard problem? Sure.

Isn't increasing productivity by solving hard problems why we get paid? My biggest question is, why isn't it even talked about and/or have aspirational goals set up?

Re: Ask HN: 20% of LinkedIn's recent layoffs were managers

#197

Earlier quoted context omitted.

Yeah I report to a director and make more than them at senior staff level

Teach me this!

1.) Be good at what you do.

2.) Be even better at leetcode.

3.) Interview during a downturn, when everybody's stock is in the toilet and all the companies that are about to go bankrupt aren't hiring.

4.) Get multiple competing offers.

5.) Play them off against each other. Turn them down if you have to.

6.) Get as much stock as you can in the counteroffer.

7.) Wait for the upturn, where the company's stock goes parabolic.

8.) Profit.

#3 and #7 are the most important. Timing and luck are better than skill. But you usually need #1 and #2 to accomplish #4 during #3, and you need #4/5 to get #6, which is what really makes you the big bucks in #7.

Re: Ask HN: 20% of LinkedIn's recent layoffs were managers

#198
post #192

Earlier quoted context omitted.

Or, you know, the people dealing with the advertisers ("partners") are gone and no money is coming in. But sure the servers are still running ;)

no idea why you need a dedicated person for dealing with the advertisers. it seemed to be just pressure from adl to scare the advertisers away, or otherwise adl will generate controversy a very slimy and backwards model

Without internal Twitter context, but having seen companies with marketing teams... there's a lot of people involved in doing close work with partners, whether advertisement ones or others. On the tech side it's kind of like AWS support - sure, everyone had access to the support portal, but once you start spending $$$, you'll get dedicated people sitting in your company's slack channel, providing support, advice and planning if you need it. (Sure, it doesn't always work great, but the idea holds) I'm sure that whoever was the big ad spender with Twitter has a dedicated contact reachable more directly. (And possibly negotiating better deals than advertised to everyone)

Re: Ask HN: 20% of LinkedIn's recent layoffs were managers

#199

Earlier quoted context omitted.

That sounds suspiciously like the office location where you‘d see big cargo planes fly overhead once in a while.

Like the unmarked ones going to area 51 filled with engineers on their way to work?

An expensive distraction. The real interesting stuff is on Area 72.

Re: Ask HN: 20% of LinkedIn's recent layoffs were managers

#200
I see this discussion has gone deep into so called technical managers and their effectiveness, even their necessity. I feel there is no clear answer possible. We are trying to objectively analyse what is not objective in the first place. Before we discuss necessity of some role we need to define it. Who is a good technical manager? What do they bring to the table? Definitions anyone? I can try but it will be subjective. I am sure there are different sets of opinions around what %mentoring and IC they should do. In fact, can we even define software engineering role and standards? Someone who writes code to solve a problem? To me a good one will write concise code thats easy to change making good use of available tools and paradigms. I have already used several vague terms. My point being, we are in a profession where entry barriers are low. Role responsibilities and standard of good work are contextual and opinionated. That has a direct impact on your experience with peers and managers. You are not always going to approve of the number of managers, their level of tech involvement etc. Have clarity on what you can tolerate and what you cannot compromise on.
Post reply on HN