The process was straightforward. It began with a recruiter phone call to assess background and skills, providing details about the role and expectations. I was told to practice coding as much as I could.
Next was a 60-minute coding round, focusing on LeetCode Easy to Medium problems. The onsite stage consisted of 4 rounds with various focus areas:
Be hands-on with arrays, linked lists, heaps, stacks, queues, hash tables, graphs (BFS/DFS), recursion, dynamic programming (memoization, tabulation), sorting, and searching, along with proper system design concepts.
I'd suggest practicing on Codewars, LeetCode, and Topcoder.
To really understand Googleyness, technical breadth, behavioral aspects, and team expectations, practice mock interviews with a Google coach on Prepfully. This is really helpful to supplement your technical practice. Additionally, Glassdoor questions are very useful.
Write code to construct a binary tree that is a mirror of the given binary tree.
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.