I applied through a recruiter. The process took 4 weeks. I interviewed at Google (Mountain View, CA) in Oct 2012
Interview
Google seems to be improving - they finally realize that they need to be slightly more open-minded in terms of candidate selection than before to avoid missing some real talent which becomes more rare than before.
They hand you over from one recruiter to another, one does the initial talking, then another one talks more specifically about position and location, then another one takes care of the interview.
They do interview on-side in Mountain View, California. The place is nice to visit, although I would not personally move there.
I find Google interview quite different from others and it clearly demonstrate the goals and priorities of the company. I am not judging if they are right or wrong but it is different. Most of the technology companies want good engineers who know how to use their brains to solve the problems and the tools and technologies to implement these solutions. Google is mostly (and solely - during the interview) concentrating on the first point. They do not seem to care if you have many years of proven experience in relevant domains. You will be asked to solve some problems that require the CS knowledge at the university level at least.
Personally I find this practice questionable. While it is good for pure research engineers, it gives somewhat partial view on some candidates. But looks like Google is trying to stick to their method of selecting the candidates.
Interview questions [1]
Question 1
The most difficult questions are about some particular algorithms or mathematical problems that interviewer is very familiar with but the candidate has never heard of. Not only it may create a stressful situation (candidate thinks that it is something he/she is supposed to know), it is not how the people solve new problems in IT. Many people may not be able to fully understand a particular mathematical (e.g. theoretical) theorem in a matter of 10-15 minutes and without good understanding of that particular theorem it may be hard to apply it to the real-life problem presented by the interviewer.
For example, the question about finding the majority number in a large input sequence.
After clearing all the interviews in 2 months, here comes the team match. Where no one ever knows when they gonna get a team match call. Even if you get the TM call next comes the HC again no one knows why they reject.
Interview questions [1]
Question 1
Coding questions from Leetcode google tagged but deep dived into it based on the level.
The interview lasted about a day, with 5 different interviewers. For each section, the technical questions took most of the part. They also showed me their office in Toronto, which was nice
Interview questions [1]
Question 1
What was the most difficult problem you solved during your last job?
it was difficult. lengthy dsa questions. design was ok. needs nice preperation. googlyness also needs preperation. it was difficult. lengthy dsa questions. design was ok. needs nice preperation. googlyness also needs preperation.