The process took 2 days. I interviewed at Google in Sep 2009
Interview
While working at Google may (or may not) be great fun, the interview process there is much less so. After a very technical phone interview, my in person interview was all about tricky logic problems with no focus on the engineering process itself (optimal card shuffling, How many golf balls can fit in a school bus?,etc.)
I applied through a recruiter. The process took 2 weeks. I interviewed at Google (Mountain View, CA) in Jun 2008
Interview
I had two rounds of phone interviews. In the first round the interviewer asked me about my current experience, motivation to work in google etc. I believe this was mostly to get an understanding of who should be interviewing me. In the second round, the interview was mostly technical. I was asked some coding questions, questions about memory management, and data structures.
Interview questions [1]
Question 1
I was asked a question about the following. If a user types in a n digit number on the telephone, how do you write a function to deduce if the number constitutes a valid word. For example, if the user enters 123, then can a valid word be made out of (a/b/c) + (d/e/f) + (g/h/i)
The process took 1 day. I interviewed at Google (Mountain View, CA) in Dec 2009
Interview
The interview was pretty technical and they don't really care about your previous experience. They have a slip that is passing around to interviewers and they put comments on what they already asked just to avoid asking the same question. They tried to cover different technical aspects, but I had 3 interviewers asking me about writing algorithms to solve given problems and all sorts of efficiency big-O discussion.
Interview questions [1]
Question 1
Given a list of iterator, write an wrapper iterator that can iterator thru all the iterators in the list