4 ms·
Haha what a colossal fuck up from the HR or whatever clown. Imagine losing a top engineer over a bureaucratic error. Well, a win for Figma at least.
by renewiltord 5y ago
Haha what a colossal fuck up from the HR or whatever clown. Imagine losing a top engineer over a bureaucratic error.
Well, a win for Figma at least.
- otabdeveloper4 5y ago> over a bureaucratic error Doesn't sound like an error to me. Getting rid of "legacy employees" is always a huge pain in the ass, sounds like his management found a solution. (Even though, frankly, a cowardly one.)
- katbyte 5y agoGuess that all depends on your view of legacy employees who took a company to where it is today
- higeorge13 5y agoAt this scale i think nobody cares, and eventually google will continue existing without them.
- renewiltord 5y agoHonestly, didn’t really consider this, but based on what I know, Google isn’t one to stop people from resting and vesting so it’s a bit strange to interpret this as an attempt from them to offload someone. They don’t usually care. I know a couple of people who do very little every day.
- finjo 5y ago"Legacy employees" sounds like code for "employees we could replace with cheaper new grads".
- otabdeveloper4 5y agoSometimes, yes. But really there's all kinds, from "we don't want this guy who insists on keeping the old C++ codebase alive" to straight-up people who engage in fraud because they think the company owes them. That said, my personal view is that you should keep "legacy employees" unless they explicitly refuse to work.
- Cthulhu_ 5y agoYup, even if they're no longer productive in terms of code output, it's worthwhile keeping them around for their knowledge of the systems - you cannot replace that, and if you try, you end up having to either 'archive' their work with a big "we don't know how this works, but it does so do not touch", or re-engineer it from scratch which is very expensive.
- thrdbndndn 5y agoI honestly don't understand what "bureaucratic error" means in this context. Does it imply office politics? Surely even Google won't let a top engineer leave due to purely administrative issues.
- girvo 5y ago> Surely even Google I think it's _more_ likely to happen at a company the scale of Google, frankly.
- thrdbndndn 5y agoThat's what I meant? "Even XX won't" means while XX is more likely to do YY, it shouldn't get to this degree.
- girvo 5y agoI must be misunderstanding I'm afraid. From my perspective, it's incredibly unsurprising that a company as large as Google and run the way Google is would let a top engineer leave due to administrative issues
- high_derivative 5y agoAs a FAANG employee, the way this typically happens is this: There is some sort of team reshuffle, someone moving to a new project and so on. Another team agrees to take on a high level IC (I assume this guy was at least L8-9). At that level, this move is approved by a VP. Person moves, headcount is filled/removed at his old team. Then new VP decides he is not ok with some part of the working arrangement (e.g. remote, scope). Person is now given a few weeks to find a few project/team, but most teams cannot accommodate senior ICs at that level easily. Boom, out of a job. Basically VP backroom dealings. It's just 'bureaucracy', and seniority almost does not matter. The only way to stop it at that point would be calling other VPs or SVPs for favours. In fact, seniority works against you here, because it becomes more political, while nobody cares about a low level IC switching around, and almost any org can absorb a solid L5 contributor.