Live data from Hacker News

Google: My interview experience

gilvegliach.it

141–150 of 164 posts

Re: Google: My interview experience

#141
post #50

Earlier quoted context omitted.

I wonder if google had to reinterview their existing employees, in a blind study... How many rounds of interviews before they eliminated most of their staff?

Once upon a time, a hiring committee was presented some feedbacks and had to come to a yes/no decision for some candidates. All them were rejected. It turned out that the feedbacks were of the hiring committee's members, from when they got hired.

Maybe they saw a bunch of people with outdated skills?

Re: Google: My interview experience

#142

Better than my interview experience. Sailed through the phone interview, went in person for the day long interview. Most were no problem except for one that took longer than it should have. And then... Nothing. Radio silence. No emails. No answered emails. I had ceased to exist. After that colossal waste of time, I decided to only work remote.

> Nothing. Radio silence. No emails. No answered emails. I had ceased to exist. Actually, that seems to be the standard behavior for rejected candidates these days, at least in my personal experience. (I've seen some references calling it the "California no", suggesting that the practice is widespread.) It's really kind of annoying.

Interview ghosting ;-)

Re: Google: My interview experience

#143
post #5

As always, remember that even technical interviews like this one have an incredible amount of random chance built into the hiring process. This is especially true at a big company like Google (where I work and do interviews). Do they happen to have positions open right now? Did you happen to get asked questions that clicked with you? Was the hiring committee feeling grouchy that day? Did you get an especially harsh i…

> There's a decent amount that you can do to prepare for one of these things, but there's also an incredible amount you don't have control over. This is where I call bullshit. This person prepared for six months. You can't tell someone to not take something personally if he or she took six months of their life to study up, only to hit a dead end because your company didn't find it within themselves to take control of…

I did the same and failed. I failed in a very specific way which annoyed me a little bit and which left me thinking how superficial this process is.

But 1. i extended my knowledge 2. i came closer to working for google than ever 3. if you really wanna work for google / you will try again and even optimize those superficial 'issues'

Re: Google: My interview experience

#144

Earlier quoted context omitted.

> If you don't get the job, it's not a signal regarding your quality as an engineer and you shouldn't interpret it as such (however tempting it may be to do so). Of course "not getting a job" is a "signal regarding your quality as an engineer". We need to keep this toxic mindset out of tech and silicon valley. The idea that everyone is smart, special, and deserves a job at Google, is completely false. There are peopl…

I was rejected from Google when I first graduated from college. Now I work at NASA and I'm very thankful I didn't get that job. Saying that the hiring process is flawed isn't the same thing as saying everyone is special and deserves a job there. From my anecdotal experience, I felt that they focus too much on algorithms and give the same interview to every candidate regardless of their experience or desired job. I ma…

They are starting to take into account area of expertise, like in the article, they offered 2 Android-specific interviews as a different process. You'd still have some algorithms, but at least the other 2 would be for embedded if that was your area.

Re: Google: My interview experience

#145

What other professions are like this? Do lawyers, accountants, civil engineers, bartenders, etc. take massive time to memorize stuff every time they want or need to go job hunting?

A friend of mine was shocked when I told him how things are looking for a job in the software world. He's a civil engineer. I guess it makes it easier in their world owing to accreditation and certs. He just found it astounding the amount of prep time it takes your average dev to get ready for an interview.

Re: Google: My interview experience

#146

It seems many acknowledge that the Google process (and other similar ones) is very flawed with a high false negative rate, but it's considered ok because there's a flood of talent always applying to Google. Maybe this used to be true, but I don't think it's true anymore. It's very likely still true in the fresh graduate to early 20's age range of candidates. But at this point, senior engineers know what this process…

Of course processes are biased in favour of hiring grads. Graduates are awesome from an employer's POV. They don't know their own worth yet, they don't have families competing for work/life balance, and they're eager to prove themselves. So you can pay them a pittance to burn the midnight oil crunching through the most miserable parts of your workload.

Re: Google: My interview experience

#147
post #74

Earlier quoted context omitted.

You think a company like Google would be able to implement a non-subjective and fair interview. Their current process must cost them a lot of talent

> Their current process must cost them a lot of talent reply They optimize to reduce false positives. They're completely fine with false negatives. They don't have any shortage of talented engineers willing to interview there. That last bit is why I think it's quite silly for smaller/unknown startups to be copying Google's interview process, as seems to be the trend.

[deleted]

Re: Google: My interview experience

#148
post #74

Earlier quoted context omitted.

You think a company like Google would be able to implement a non-subjective and fair interview. Their current process must cost them a lot of talent

> Their current process must cost them a lot of talent reply They optimize to reduce false positives. They're completely fine with false negatives. They don't have any shortage of talented engineers willing to interview there. That last bit is why I think it's quite silly for smaller/unknown startups to be copying Google's interview process, as seems to be the trend.

>>They optimize to reduce false positives. They're completely fine with false negatives.

Getting too many false negatives is a very sure way of getting a lot of false positives.

>>They don't have any shortage of talented engineers willing to interview there.

You might be wrong there. Apart from huge money opportunities, there are little incentives for any body to waste their best years in large company political middle levels.

Re: Google: My interview experience

#149
post #148
post #74

Earlier quoted context omitted.

> Their current process must cost them a lot of talent reply They optimize to reduce false positives. They're completely fine with false negatives. They don't have any shortage of talented engineers willing to interview there. That last bit is why I think it's quite silly for smaller/unknown startups to be copying Google's interview process, as seems to be the trend.

>>They optimize to reduce false positives. They're completely fine with false negatives. Getting too many false negatives is a very sure way of getting a lot of false positives. >>They don't have any shortage of talented engineers willing to interview there. You might be wrong there. Apart from huge money opportunities, there are little incentives for any body to waste their best years in large company political midd…

>>Getting too many false negatives is a very sure way of getting a lot of false positives.

Why ? IMO if you reduce the False Acceptance Rate, you will up the False Reject Rate. Good chart at https://www.tractica.com/biometrics/in-biometrics-which-erro...

Re: Google: My interview experience

#150
post #135
post #58

Earlier quoted context omitted.

I've heard this before, is there a source for this? It has all the hallmarks of an urban legend...

I don't have the source anymore but it was an article where they spoke to someone at Google HR who mentioned that a particular team was difficult to approve anyone or hiring. To prove their point, they anonymized the team's own resume and asked them to rate them.

I saw a lecture (about tech interviews) by a former Google engineer who at the time was working at Etsy. He mentioned that the experiment was performed on him and his team. The hiring committe he was a part of had acquired a reputation of being particularly difficult to please. They ended up rejecting all of their own hiring packets. I was skeptical when I heard the story. Google must do a fantastic job anonymizing the hiring packets that get reviewed, or maybe they had been at Google for a long enough time that they forgot their own process and didn't clue in. However, this engineer did mention it so it doesn't seem to be an urban legend to me. With some clever searching I'm sure you can find the video.
Post reply on HN