The interviews were with four different Software Engineers. Based on what I gathered online and the feedback I received from friends who are currently Software Engineers at Google, I thought I had decent chances: strong knowledge of at least one current language, some knowledge of algorithms and data structures, as well as Big O notation.
I was surprised to be asked non-software questions, such as the network speed efficiency of various wireless technologies. I was also asked to solve a math brain teaser in a language I specifically said I had not used in years, and was told that the code had to compile and run as is, regardless of potential typos.
It took several weeks for Google to come back to me, but I received a quick offer from a competitor with a more realistic interview process. I'm glad I did not hold my breath. I think I should have left after the second interview; it was pretty obvious the process was a plain waste of time.
Which wireless channel should you choose for your home Wi-Fi, considering there is no interference on any of them?
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.