The Google interview process is very slow. Start it a month before any other company so that your offers come out at the same time.
Google also has a tendency to downlevel candidates, as well as to lowball the first offer. You really need to have competing offers to negotiate them up.
During team matching, recruiters tend to present relatively undesirable teams first. My friends who already work at Google say these teams have had positions open for a long time and are struggling to fill.
Recruiters also don't always have a good handle on what teams are a good fit, slowing down the process. You have to push them to match you with teams that are interesting and suitable.
One coding question was straight from LeetCode.
Two were not found on LeetCode, but were very similar to LeetCode-type questions.
The system design question was also very generic.
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.