On site, there were six 45-50m interview slots. One was held over lunch to answer my questions.
Three of the interviews focused on algorithms and coding, one was about previous experiences, and one was a high-level system design.
Coding problems were not traps but required thought and care. Two of my problems involved brute-force traversal, and one was a more complicated problem requiring dynamic programming (which I do not think I got fully right).
During an interview, the requirements of each question would evolve, adding extra constraints or demanding increased complexity. Depending on the interviewer, they would only move on after you had your code in. Therefore, if you can put the algorithm into code form faster, you might be able to better show your prowess, as you would get to the harder items.
It is a marathon, and that makes it harder. The questions would have been much easier if they were done in isolation. I guess it also tests your ability to cope with pressure.
Overall, it was a very interesting experience. I have not heard whether or not I will have an offer.
Signed an NDA about details.
The following metrics were computed from 748 interview experiences for the Google Software Engineer role in Mountain View, California.
Google's interview process for their Software Engineer roles in Mountain View, California is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Google's Software Engineer interview process in Mountain View, California.