←back to thread

1114 points namuorg | 1 comments | | HN request time: 0.318s | source
Show context
abdj8 ◴[] No.43678249[source]
Layoffs are a difficult thing for employees and their managers. I have seen people (one was a VP of Engineering) escorted out of the building, sent in a cab to home along with a security guard (this was in India), not allowed access to computer or talk with other employees. But, recently have had a very different experience. The current company I work for announced 30% layoffs. The list was made public within one hour of announcement. The CEO detailed the process of selecting people. The severance was very generous (3-6 months pay) along with health and other benefits. The impacted employees were allowed to keep the laptop and any other assets they took from the company. They even paid the same severance to contractors.

After the announcement, the laid off employees were given a few days in the company to allow them to say good byes. I love the CEOs comment on this ' I trusted them yesterday, I trust them today'. This was by far the kindest way of laying off employees imo. People were treated with dignity and respect.

replies(20): >>43678291 #>>43678464 #>>43678562 #>>43678693 #>>43678739 #>>43678898 #>>43679191 #>>43679316 #>>43679496 #>>43680833 #>>43680865 #>>43680993 #>>43681111 #>>43681356 #>>43681653 #>>43681730 #>>43681941 #>>43682960 #>>43700522 #>>43705911 #
DannyBee ◴[] No.43680833[source]
Google is just really bad at this, but seems to think it's not bad at this. It's sad since there is no excuse for it - plenty of companies conduct regular layoffs and role eliminations in more compassionate ways, it would not take much to survey and learn from their practices. Hell, IBM was often more compassionate about layoffs than Google.

Some of it they've tried to become more formal about in ways that actually make it worse - so for example, the timing of this (which the person complains about) is because (AFAIK) they now have one day a month where ~all role eliminations that are going to happen that month, happen. Or so i'm told this is the case.

Ostensibly so you don't have random role eliminations every day, which makes some sense, but then you have no way for people on the ground to do anything more compassionate (like move the timing a bit) because they can't get through the bureaucracy.

In the end - it's simple - if you disempower all the people from helping you make it compassionate, it will not be compassionate. The counter argument is usually that those folks don't know how to do it in legally safe/etc ways. But this to me is silly - if you don't trust them to know how to do it, either train them and trust them, or fire them if they simply can't be trusted overall.

replies(4): >>43681799 #>>43682751 #>>43683690 #>>43684992 #
PaulHoule ◴[] No.43681799[source]
Google is bad at a lot of things but has a “we’re number one why try harder?” attitude.

Or rather you can’t benchmark the performance of anyone there against industry peers because they are protected by a two-sided market. Bazel, Kubernetes and other startup killing tools are developed there because with monopoly services they can hire 3x the number of developers at 3x the rate of other firms and shackle them with tools and processes that make them 1/3x as productive and survive. It’s even worse when it comes to evaluating top management, somebody like Marissa Meyer might be average at best but has such a powerful flywheel behind them that they might seem to succeed brilliantly even if they were trying to fail with all their might.

replies(5): >>43682040 #>>43682681 #>>43682692 #>>43682695 #>>43683486 #
1. acoustics ◴[] No.43682695[source]
Bazel is an incredibly productive tool at the right scale. I could not imagine working on a giant monorepo without it.

If a startup is killed by Bazel, it probably wasn't the right tech choice for their scale, and it would be more accurate to say that the startup was killed by bad technical leadership.