3 ms·
I seem to recall Google saying that they don't hire for a specific position; they hire good developers and then find the right position for them. This idea is d
by RHSeeger 3y ago
I seem to recall Google saying that they don't hire for a specific position; they hire good developers and then find the right position for them. This idea is directly countered by the act of firing developers in a specific position because that position is no longer viable.
- ehsankia 3y agoRight, that doesn't quite make sense. The previous layoff was all across the board and likely trimming lower rated engineers across the whole company. Wiping a specific team, with potentially top tier talent, makes no sense. Are we sure this is actually general engineers? The headline only says "working on". It could be people doing very specific work, like prompt validation, QA, etc.
- sokoloff 3y agoI would wager a fair amount that Google took that lens and very likely "saved" much of the talent that they had previously identified as top tier (in some cases months or quarters before this round of layoffs; in others during the layoff prep).
- Rebelgecko 3y agoI don't think the previous layoffs took perf/grad stack rankings into account
- alphabot314 3y ago> The previous layoff was all across the board and likely trimming lower rated engineers across the whole company. This is simply untrue for the Jan 2023 Alphabet layoffs. Entire orgs (>200 FTE) were let go regardless of individual performance.
- hashtag-til 3y agoThat's mostly to reduce their legal liability, rather than anything else. Poor management, nonetheless.
- LegitShady 3y agoout of good positions
- trashtester 3y agoIf a company wants to fire some people they believe can cause legal trouble if fired individually, somtimes they will spend a year or two reorganizing in a way that incidentally have many of these people all ending up in the same part of the organization. Then they can do layoffs there, seemingly without violating any wrongful termination laws. Somehow the best developers and others who contribute directly to the bottom line tend to be unaffected by such events.
- refulgentis 3y agoI had on very good word that Bard / Assistant was used as a husk for this. New managers managers manager moves in with a good chunk of people to Help With Bard. Then 6 months later you and the older handers are asked to move to an exciting new opportunity in Assistant. of course it's an opportunity, we're investing in it. Bla bla bla. 8 weeks later your roles have been eliminated, you're locked out of everything except the internal jobs listing site for the next 8 weeks. (Note this was happening _before_ tonight's culling) Sundar's really done a great job with culture
- trashtester 3y ago> 8 weeks later This sounds like they've been in a rush. Maybe there are bonus deadlines coming up.
- refulgentis 3y agoThis is an excellent point, Xoogler and been struggling to explain concisely why I've been offended / think all this is fundamentally misleading. And that's it right there. We were all special snowflakes who could always help the mothership. Now we're ballast that Sundar and VPs need to take yearly turns Optimizing.
- bitshiftfaced 3y agoIf we accept the premise, then why wouldn't it make sense to fire developers in specific positions? If a position is no longer viable, it won't matter to you if you fire that person, since presumably any person you choose would also be a "good developer."
- RHSeeger 3y agoI'm making the assumption that they're _also_ still hiring, and that the people that were fired could, instead, be transitioned into other roles. I would be amazingly surprised if they were not still hiring.
- kevingadd 3y agoThat's definitely not how Google does hiring anymore. They don't do true generalist interviews, that's for sure. Every Google interview gauntlet I went through was at least 50% specialists asking me specialist questions, and in the end when I got hired it was when I got interviewed by specialists appropriate for my domain, and I was hired for a specific position.