I applied online for a new grad position in mid-September. I was invited directly onsite and interviewed in Mountain View in mid-October.
Before the onsite, I had a chat with a recruiter and went through a coaching call with a Google engineer in London.
Onsite, I had four technical rounds, separated by lunch with an engineer. About a week and a half after the interview, I was told I would be receiving an offer. After talking to the recruiter and another engineer, I ultimately decided to decline the offer.
Overall, the experience was smooth and well-run, and I enjoyed receiving a Google sweatshirt and water bottle once I received the offer.
I decided against working at Google because I received a more interesting opportunity and wanted to try product development, not just work on tools and infrastructure.
Graph search, dynamic programming, binary search trees, arrays, designing a product release.
The following metrics were computed from 3 interview experiences for the Google Software Engineer, Tools and Infrastructure role in Mountain View, California.
Google's interview process for their Software Engineer, Tools and Infrastructure roles in Mountain View, California is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Google's Software Engineer, Tools and Infrastructure interview process in Mountain View, California.