Plan to throw one away, you will anyhow.
I am doing a startup!
Cross-browser testing from your browser!
I have written my fourth book!
Be faster than Larry Wall in the shell!
You're viewing a comment by Ryan and its responses.
Your interview experience matches what a few other people I know went through when interviewing with Google. They wasted a month of your life and put you through eight interviews and you still didn't get the offer. You are a patient person with a good attitude if you'd consider this a good experience. I'd be very angry and insulted.
Google employees need to get over themselves. The people working there aren't gods. On average, they aren't any smarter than any other large technical organization. I've worked with tons of really smart engineers, and none of them had to put themselves through eight interviews to get their jobs.
Their "interviewing" process pretty much guarantees that only masochists will make it through. Consider yourself lucky.
Mr. Ryan you are not listening to Mr. T.Human who has clearly said that "he had two phone screens and ONE onsite interview with 6 engineers". You are probably a sour grape.
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
The problem is when 6 engineers interview with same level of toughness then same topics are bound to be repeated. 2) finally Google doesn't know the difference between mistake and error. From the post it seems that Google takes errors seriously as well, in this they loose better guys than one who joins them as error is NOT mistake. And if error is so seriously taken then why go upto 8th round
I'm not sure if it's a waste. When you feel prepared for a Google interview, you are going to feel prepared for any software engineering interview. It's good practice - and they pay all of your expenses! I'd say for the purpose of interviewing practice it's an amazing bargain.
(why do I need your e-mail?)
It would be nice if you left your e-mail address. Sometimes I want to send a private message, or just thank for the great comment. Having your e-mail really helps.
I will never ever spam you.
(Your twitter handle, if you have one.)
* use <pre>...</pre> to insert a plain code snippet.
* use <pre lang="lang">...</pre> to insert a syntax highlighted code snippet.
For example, <pre lang="python">...</pre> will insert Python highlighted code.
* use <code>...</code> to highlight a variable or a single shell command.
* use <a href="url" nospam>title</a> to insert links.
<a href="url" nospam>title</a>
* use other HTML tags, such as, <b>, <i>, <blockquote>, <sup>, <sub> for text formatting.
Type the word "lcd_101": (just to make sure you're a human)
Please preview the comment before submitting to make sure it's OK.
Peter Krumins' blog about programming, hacking, software reuse, software ideas, computer security, browserling, google and technology.
Reach me at:
Or meet me on:
Subscribe through an RSS feed:
Subscribe through email:
Enter your email address:
Delivered by FeedBurner
See all top articles
See all downloads
See more detailed list of recent articles
See more detailed category information
See more detailed list of all articles