I applied online and was contacted within a few days. The typical interview process involved a short phone call with a recruiter, followed by a one-hour technical phone interview with an engineer. This was then succeeded by a six-hour onsite interview.
The questions were not as difficult as I expected, though I may have been lucky and received a sequence of easier questions. The interview is also a test of endurance; by the end, I could barely think straight.
If you want to prepare properly, I would recommend one or two practice sessions where you complete five interview practice questions in a row. If you have a strong understanding of graph algorithms and fundamental data structures, I imagine you will pull through.
Also, make sure you can determine the Big O complexity of whatever code you write, as the engineers will ask for your analysis after you finish each question. I think I answered four out of five questions correctly at the onsite interview, so I did not receive a job offer.
I signed an NDA.
The following metrics were computed from 28 interview experiences for the Google Software Engineer role in Cambridge, Massachusetts.
Google's interview process for their Software Engineer roles in Cambridge, Massachusetts is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Google's Software Engineer interview process in Cambridge, Massachusetts.