Live data from Hacker News

Google: My interview experience

gilvegliach.it

41–50 of 164 posts

Re: Google: My interview experience

#41

At google, I was given some code that manipulated some bits and the interviewer, in inexplicably terrible English, kept asking me what the purpose of this code was for. He has a very thick Eastern European accent which was not understandable and I don't know how he was able to get into interviews. I could tell it was doing some sort of overflow detection but other than that I had no idea. I hadn't done anything with…

[deleted]

Re: Google: My interview experience

#42
> The recruiter also said I was borderline, which might be just a nice empty word from her, but made me feel better.

I don't think this is just her being nice; I was also told I was borderline and they actually ended up letting me interview again for a different position (SETI instead of SWE). Alas I got rejected again, but the year after they called me back because I was borderline, or so they told me, and I am working there now.

As others have said, there is some element of chance, both on their part and also likely on yours. Hopefully you'll apply again as it seems like you have a good chance.

Re: Google: My interview experience

#43

I'm becoming convinced that the only way to get into Google is to get in as an intern or new grad if OP studied for 6 months and still didn't get an offer. It doesn't seem that way at other top companies like FB, Amazon and MS from the people I've talked to.

I got hired by Google, but didn't get an offer from Facebook. There are some differences in the process that could lead to a different outcome sometimes.

However, I think they have more in common than differences and luck is a big factor.

Re: Google: My interview experience

#44
post #30
post #4

At least they give you some feedback in the end. I had the experience to be rejected after an onsite interview at Amazon, and they did not take the time to give a word of feedback, after I even asked for it. I see the past interviews were of great help to you to finally get the position at Amazon. I am looking forward to read your third post. Complimenti collega!

I never got any feedback from a Google onsite, is that new?

This should never ever happen. How long ago was this? I work at Google. I can try to follow up for you.

Re: Google: My interview experience

#45
post #21

Earlier quoted context omitted.

Right, with 4 being basically impossible to get, and scores being normalized wrt the history of the interviewer.

I haven't worked at Google, but I have interviewed with and reviewed feedback from Xooglers, and 4's are not impossible -- but they are rare and you have to essentially be smarter than your interviewer about the particular problem to get one. This can be pretty hard, since many interviewers pick problems that they are extremely familiar with.

On my Google onsite (in Zürich as well), one of the interviewers told me that if he gave me a 4.0, he'd have to argue on my behalf if the hiring committee wasn't sure of hiring me.

Re: Google: My interview experience

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

One of the most frustrating things I've seen is that interviewers/recruiters themselves couldn't stand up to the same rigor of questions which they expect from applicants. In one such company, I asked a question on "algorithmic fairness, accountability and transparency" about core algorithms they used for their business. First, it came across as a bit of a rude shock to them - they hadn't heard about it. Second, they parroted a line which was along the lines of "our legal team looks into it and makes sure it is legal". Third, when pushed about the fact that my question was not on legality - they refused to accept that they may have overlooked this part or were not aware of it. Rather than engage in a discussion, when the boot was on the other foot - they wanted to weasel their way out of it.

Re: Google: My interview experience

#47
I'm curious if the people giving the interviews have an incentive to be conservative with scoring. Maybe it looks bad when your score is the highest? As if you're lowering the bar? If true, I could see that contributing to how these interview stories play out (candidates thinking they did better than their no-hire outcome).

Re: Google: My interview experience

#48
post #40

At google, I was given some code that manipulated some bits and the interviewer, in inexplicably terrible English, kept asking me what the purpose of this code was for. He has a very thick Eastern European accent which was not understandable and I don't know how he was able to get into interviews. I could tell it was doing some sort of overflow detection but other than that I had no idea. I hadn't done anything with…

> I hadn't done anything with bits since college. No offense, but then the job probably was not right for you (which does not mean that you would not excel at other roles, of course). It then seems that the interview might have served is purpose just fine and saved both you and Google from being cast into an unfitting position.

I really wouldn't make that conclusion until you knew what job he was interviewing for. Firmware development? Sure, you might be right. iOS developer? Unlikely that low level bit manipulation is going to be a good indicator of his ability to succeed in that role. That's not to say its irrelevant, but, just not a quality indicator for that role in my opinion.

Re: Google: My interview experience

#49
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 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 ride over the chute is proof positive that you've got marketable talent.

Re: Google: My interview experience

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

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?

Post reply on HN