Comment Responses

I have to agree with Ryan; I'm afraid this is what happens when you let a bunch of engineers run HR; they consider coding to be some kind of high and pure art form and are incredibly snotty about it to boot. One can only imagine what fun it's like to work there given this filtering process..!

I've been contacted by Google recruiters several times, and turn them down each time because I've heard that the interview process is so tortured. To dispute what T. Human said, this is 8 interviews with 8 different people, the last five of which were at one location campus. That's still 8 interviews, and 8 sets of opinions from 8 interviewers.

Thanks very much Peter for posting this writeup; I hope you achieve your goal of working at Google if that's your aim, and continued success to you.

The interview process is just fine. One or two phone screens, for obvious reasons, to avoid wasting time of 4-5 engineers onsite. Then a day of interviews onsite, which is pretty standard. Generally, they'll make the decision after that, or, in borderline cases, they might ask for another interview. I went through it, and I thought every interviewer was respectful and competent. The whole process may take a few weeks, or months, but if you're patient and not in a hurry, it's a positive experience.

Right. This process is not very different from Microsoft, Amazon, or Facebook - all of which I have been through. The biggest difference is that kind of questions and a certain kind of vibe that I get from Google engineers that somehow feels distinct. It's hard to describe.

This is not 8 different interviews as if you have noticed he wrote that same topics were repeated and the 6th interview was easier than earlier ones. So ideally the interview were of same level and on same different topics with 6 different engineers. diffedifferent people an