Live data from Hacker News

Google Cuts Jobs in Engineering and Other Divisions

nytimes.com

571–580 of 1001 posts

Re: Google Cuts Jobs in Engineering and Other Divisions

#571
> The Silicon Valley company laid off employees in its core engineering division, as well as those working on the Google Assistant, a voice-operated virtual assistant, and in the hardware division that makes the Pixel phone, Fitbit watches and Nest thermostat, three people with knowledge of the cuts said.

Why would this hit core engineering if the company needs to focus on AI ? I'd imagine these people would be ever more valuable

Re: Google Cuts Jobs in Engineering and Other Divisions

#572
post #49

Earlier quoted context omitted.

And you know what happens with the money that you take, save and invest? They go in to public companies, they hire MBA's, and they try to improve profitability of company by letting engineers go. Your money have come a full cycle :)

TINA when CPI inflation (in the UK) is has been 18% in just 2 years.

TINA stands for There Is No Alternative? That's a new one for me.

Re: Google Cuts Jobs in Engineering and Other Divisions

#573

Earlier quoted context omitted.

I work remotely for a big US company and I have heard talk of similar plans within the company, offshoring entire products' engineering work to India. Luckily my work is very niche (vuln research). I can only imagine the subpar and vulnerability ridden code we'll be seeing over the next few years from all the offshoring + irresponsible overusage of AI tools.

Why would the code be subpar? Is a google employee in US somehow more competent than the one in India? What you are thinking about was outsourcing which is very different than Google hiring in India. Just because you are paid more you are not a ‘better’ programmer

Quality from India is awful. Both from functionality and just… caring. They don’t really care as much it’s always just good enough. They are generally very difficult to work with.

Re: Google Cuts Jobs in Engineering and Other Divisions

#574
post #347

Google is overrated. It's been obvious for over a decade after they built an interview process that is heavily biased towards those who recently took an algorithms class. You had talking heads yammering about how hard it was to get into Google, which to be honest, made the company even less appealing. Is this a software engineering company or some kind of hyped up nightclub? Yeah, maybe it's a hard interview if you'v…

I did over 400 interviews working there, and many hundreds more serving on hiring committees. I never gave a leetcode interview, and saw only a modest amount of them in committee.

“It’s all leetcode BS” makes a great offhand d complaint but was not the actual truth.

Re: Google Cuts Jobs in Engineering and Other Divisions

#576
post #347

Google is overrated. It's been obvious for over a decade after they built an interview process that is heavily biased towards those who recently took an algorithms class. You had talking heads yammering about how hard it was to get into Google, which to be honest, made the company even less appealing. Is this a software engineering company or some kind of hyped up nightclub? Yeah, maybe it's a hard interview if you'v…

I wouldn't characterize Leetcode interviewing as being biased towards those who recently took an algorithms class - it's biasing in favor of those (of any level of experience) who are willing to spend a few months practicing Leetcode. I thought that Google/etc had at least dialed this back a bit, or maybe just dialed back the "how many gas stations are in the US" type questions, after realizing this wasn't the best p…

Last year I went through a loop and a couple of the questions I got and mentioned to friends who are SWE's at Google thought they were too hard for an interview, especially after checking their proposed solutions in the internal problem bank.

So it's definitely still happening.

No I didn't get the job because they were too hard for me to even get a brute force solution.

Re: Google Cuts Jobs in Engineering and Other Divisions

#577
post #252

Earlier quoted context omitted.

As a European I'm curious which unions and industries are you talking about? I've been working tech or tech-adjacent jobs my entire life here and I've never been in a union nor do I know any friends (developers / designers) that are in a union. And I'm going to conferences and meetups on a regular. I'm not saying unions don't exist (probably more so in certain industries), but for devs to be in a union in Europe? Nev…

"Betriebsrat" sounds German to me, so possibly Germany? And definitely Sweden. Many (most?) of my software engineer colleagues are members of either the engineering-specific "Sveriges Ingenjörer" or generic white-collar "Unionen" union.

> “Betriebsrat" sounds German to me, so possibly Germany?

I am in Germany and I never heard of any union for Devs, not even large firms having any specific ones for Devs. My colleagues frequently discuss about unionizing but there are huge pay disparity hence most often it is hard to get everyone on board sadly.

Most unions are intended for craftsmen, minijobs, public transports and such. There are some small employers covered by famous IG Metall tariff but that is not the norm. I know that likes of Airbus has some kind of union that covers most of the departments and hence pays insane salary but that is something I heard from friends of people who work there, so I can’t assure accuracy.

There might be unions but that is not the norm except some dinosaurs.

Re: Google Cuts Jobs in Engineering and Other Divisions

#578
post #384

Earlier quoted context omitted.

> It's been obvious for over a decade after they built an interview process that is heavily biased towards those who recently took an algorithms class. What would you do instead? Threads about tech interviews are always the same: we all complain about the process with no real alternative when you want to hire at that scale. In particular about: > Just about every other skill that is needed to be a good software engin…

I've been interviewing people for Software Eng jobs for more than 10 years an I haven't used leetcode style problems for like 8 of those years. Leetcode interviewing is lazy interviewing. It's for when you don't want to put an effort in your interviewing process to check if the candidates have the skills you need for the position you are filling. For example. My interview process nowadays is one web API interaction c…

Have you built a $1 Trillion company? No.

Has your company pioneered some great open source software (Kubernetes, Go, React, PyTorch, Cassandra? No.

How do you even know that your method is correct, scalable? Answer is you don't know.

It's mind-boggling that people who hire for software engineers who write CRUD apps used by 20 people, think they know how to hire for firms that serve 4 Billion+ users.

Re: Google Cuts Jobs in Engineering and Other Divisions

#579
post #574
post #347

Google is overrated. It's been obvious for over a decade after they built an interview process that is heavily biased towards those who recently took an algorithms class. You had talking heads yammering about how hard it was to get into Google, which to be honest, made the company even less appealing. Is this a software engineering company or some kind of hyped up nightclub? Yeah, maybe it's a hard interview if you'v…

I did over 400 interviews working there, and many hundreds more serving on hiring committees. I never gave a leetcode interview, and saw only a modest amount of them in committee. “It’s all leetcode BS” makes a great offhand d complaint but was not the actual truth.

[deleted]

Re: Google Cuts Jobs in Engineering and Other Divisions

#580

Earlier quoted context omitted.

I disagree and I am sad that we're teaching each other to be skeptical and cynical. The company is not your friend and not your enemy, I agree. However, people _do_ develop personal relationship with each other. Sometimes even across the different levels in the company hierarchy. Yes, as with any other relationship, circumstances and interests might override this, but relationships still do matter. People have emotio…

I don't think this necessarily holds in the world of remote work. At least for me, relationships are very surface level. Almost no friendly banter, limited 2 second "How was your weekend?" before meetings that no one cares about. Its hard to be friends with little black boxes and white text on a screen. This is compounded when 75% of the team is made up of consultants. I do agree though that its pretty awful but the…

I've said it many times both here and in "real life" - teams filled with any sizable proportion of consults (15-20% and up I would say) are one of the clearest, brightest red flags you could see.

I've seen first-hand organizations shift from 100% employed teams to being majority consultants, and the majority of those consultants on 1-2 year contracts then leaving. Code quality goes to absolute shit. The name of the game is spending the first half of your contract not getting fired and the second half looking for the next contract. Zero documentation. Refusing to do turnover meetings. Not showing up for the last day/week of the contract because their next contract wanted them to start earlier so they didn't care if they got paid for this one or not. Most egregiously someone just brought in their next contract's laptop into our office with over a month left on their contract.

None of this happens with employees. Sure you'll occasionally have someone quit with minimal or no notice but that's the exception. We had to basically assume that any time we got in the last month of the contract was a bonus. Consultants work for their recruiting firm, not for your org, and they behave accordingly.

Post reply on HN