I received an email response shortly after applying, followed by a phone screen. I was informed that it was possible to skip the online coding interviews, so I bypassed them. After some time, I heard back from the same person, who informed me that the feedback from a potential manager was positive. Consequently, I was assigned a recruiter to manage my candidacy.
I had a 15-minute phone call with the recruiter, who explained the interview format. I was provided with interview preparation materials and spent approximately one month preparing. I also utilized a one-hour online interview coaching session offered by Google.
My preparation included studying college textbooks on data structures, algorithms, discrete mathematics, and probability. Additionally, I used the online version of the "Cracking the Coding Interview" book, which was linked in Google's preparation materials, for practice problems. I also used LeetCode for further practice.
On interview day, I completed five 45-minute coding interviews using a whiteboard. Lunch was scheduled with an employee after the first three interviews.
Less than a week later, I received my results from the recruiter. I was informed of my rejection and given an explanation of the positive and negative aspects of my interview performance. I was also told that I would be eligible to interview again in one year. The recruiter mentioned that my interview performance was strong enough that my application would be reviewed by managers for positions with less of a software engineering focus, such as site reliability engineer.
About a week later, I received an email from my recruiter stating they were not interested but encouraged me to reach out again next year if I wished to reapply.
A few weeks after that, I received an email inviting me to complete a survey about my interview experience. I found the individuals involved in the interview process to be friendly and professional.
One coding question involved threading and concurrency. The other four involved data structures, like graphs, to solve coding problems. All the interviews asked one coding question.
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.