Live data from Hacker News

Google: My interview experience

gilvegliach.it

131–140 of 164 posts

Re: Google: My interview experience

#131
post #39

Earlier quoted context omitted.

Hi, I work at Google. I am sorry for this. This should never happen. How long ago was this? I can try to follow up on your behalf.

Nov 13th, 2015. It's a bit of a moot point now, though. I've since switched to remote only, left the bay area, and bought a nice log cabin in the countryside. Horses in the morning and no commute = a very happy me :)

That sounds great!

Re: Google: My interview experience

#132
post #125
post #37

Earlier quoted context omitted.

I had a similar end result from Facebook, I assume I did not pass but never heard back from my recruiter.

Yep, had a video-interview with FB too. Didn't hear from them after that.

My experience is the polar opposite - I've had updates before and after, even just to say sorry it's taking so long (4 days isn't long to me). It must very much depend on who is taking care of you.

Re: Google: My interview experience

#133

Earlier quoted context omitted.

Google NDA covers (non)disclosure of Google confidential info. It has nothing to do with "bad-mouth"ing before or after termination of employment.

Perhaps not, but if you say something negative about Google, and it gets a lot of attention from the public, I think you can agree that you're probably going to get fired. Let's be real here, NDA or no NDA, this is true of working for any company. Which is why the "personal views" of a current company employee of any organization posted publicly is close to useless.

> I think you can agree that you're probably going to get fired.

thesmallestcat claimed "that ex-Googlers cannot bad-mouth the company", and I claimed that no such clause exists in the standard contract of employment.

By the time you are an ex Googler, getting fired is unlikely to be an effective deterrent.

> Which is why the "personal views" of a current company employee of any organization posted publicly is close to useless.

Either you believe that the company is forcing me to write this (instead of just remaining silent), or your argument is not very logical.

Re: Google: My interview experience

#134

Earlier quoted context omitted.

> 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 super important. Don't take it personally at all. They're using the randomness as a flow control. They are always attracting more talent than they actually need purposely to keep the reservoir full and just running the extra through the spill gates. Just taking a rid…

> 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 used to work with someone who now works at Google. He was the sole lead for a project that he absolutely butchered the code before bailing out. I was left to clean up the mess which took many months and then continuing to finish the project to completion to the satisfaction of the end customer. I can certainly say he was not 10x programmer but perhaps he found some niche role there that he can contribute towards.

Re: Google: My interview experience

#135
post #58

Earlier quoted context omitted.

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.

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.

Re: Google: My interview experience

#136
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…

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

You also have to consider the cost of hiring the wrong candidate. That can often dwarf the loss from missing out on a good candidate. The other option is to hire less stringently but use trial periods which have their own problems.

Re: Google: My interview experience

#137
post #89

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.

I once worked for a company that is greatly respected in IT industry. While their engineers were top notch, the non-technical ones were... let's just say not so good. It was common for a recruiter to forget about a candidate (even a good one who passed the interviews!). One guy got positive reply 3 months after his interview. I imagine there may be similar mess at Google too.

Sounds like IBM from 20 years ago... except they would call to just set up a screen interview 4 months after the resume submission for a specific position.

Re: Google: My interview experience

#138

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…

> I made it very clear I wanted to work in embedded systems and write code for microcontrollers and they asked me questions about graph theory. Algorithms are not everything, especially for a company with such diversified technology opportunities. If I'm working on search, then sure. But embedded software? Can't they take the time to focus the interview even the slightest bit?

I'm not a Googler, but from what I hear, moving between teams within Google takes less effort than most places, so that might explain why Google tends to interview for a generic "Google developer" rather than a "Embedded developer" position. Who knows, you might progress from initially working on the Google home firmware, then move on to optimizing the search client code and then possibly the search backend for Home itself.

I'm sure there are a lot of specialists at Google, but I suspect those are fewer than generalists with a solid handle on data structures and algorithms.

Re: Google: My interview experience

#139

Earlier quoted context omitted.

Perhaps not, but if you say something negative about Google, and it gets a lot of attention from the public, I think you can agree that you're probably going to get fired. Let's be real here, NDA or no NDA, this is true of working for any company. Which is why the "personal views" of a current company employee of any organization posted publicly is close to useless.

> I think you can agree that you're probably going to get fired. thesmallestcat claimed "that ex-Googlers cannot bad-mouth the company", and I claimed that no such clause exists in the standard contract of employment. By the time you are an ex Googler, getting fired is unlikely to be an effective deterrent. > Which is why the "personal views" of a current company employee of any organization posted publicly is close…

Ah, I do see thesmallestcat mentioned "ex", but as the topic was you, a current employee, that seems to be an error on their part. (I don't think the topic at that point was applicants, who would not have signed an NDA at that point, and the conversation had since moved to "Googlers defending Google on HN".) Correct me if I read this wrong.

The problem is that there are likely current employees with both positive and negative feedback about the company. However, you will only hear the former, because the latter would get fired for speaking. Therefore, at the very best, we have to assume your view isn't necessarily representative of the whole.

But more than that, I don't feel Google employees have a particularly balanced view about their employer. You can see my thought on the issue here, and Frqy3's response is succinct in the issue: https://news.ycombinator.com/item?id=14159213

But moving all the way back to the top of this chain, I do see a lot of bad interview stories with Google. Whether through malice or not, there is a lot of hoops to jump through, and as thesmallestcat indicated, people who don't have an incredible amount of enthusiasm for Google are unlikely to bother to continue the process. As it stands, each time one of those "horror stories" comes out, a variety of HN members often state that they would not want to work for Google, in part because of that process.

Re: Google: My interview experience

#140
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.

Maybe it's part of the process. It's easier and cheaper to maintain good image to get people interested in working for Google (improving workforce supply) than to optimize the interviewing part.

It's the same with manufacturing. It's better to provide 96% reliability with warranty than to struggle with providing 99.9% reliability.

Post reply on HN