I was contacted over LinkedIn by a recruiter, which was followed by a technical phone screen.
The phone interview consisted of two coding questions to be programmed on a Google Doc. If you cleared that, you would be scheduled for an onsite.
The phone interview was LeetCode easy/medium (I would say more towards the easier side). I expected something like dynamic programming, but the questions were strings/heap-based and pretty doable. The first one was easy, and the second one was a medium-level difficulty.
The onsite interview had four rounds, all technical and focused on different areas such as graphs, sorting, recursion, and a general array-based topic. I would say all questions were on LeetCode medium level. Some were tricky, in the sense that they required you to remember some algorithm from CLRS and apply it directly.
All questions were new, which I appreciate.
Google really cares if you can write working code in that short time, or at least that is the impression I got from the interviews. I messed up during the interviews and did not write clear code. Also, be well prepared for space-time complexity discussions. Before going onsite, be sure to participate in Google's coaching, as it will help you understand what Google expects onsite.
Overall, the experience was good. The accommodation, flight, and travel were well arranged by Google.
Signed the NDA
The following metrics were computed from 2 interview experiences for the Google Software Engineer, New Grad role in Mountain View, California.
Google's interview process for their Software Engineer, New Grad roles in Mountain View, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Google's Software Engineer, New Grad interview process in Mountain View, California.