Firstly, I was given a link for two programming questions. These were medium-difficulty questions to be solved in 90 minutes, which was ample time.
Then, I was contacted by a recruiter and scheduled a phone call interview. This was a 45-minute call that included an easy programming question based on strings, presented in Google Docs.
Finally, I was invited for an on-site interview at their office in Mountain View. The interview consisted of four rounds.
Each round involved whiteboard programming, featuring either one large question or two to three smaller ones. Again, the questions were solvable.
Lots of practice in LeetCode and the "Cracking the Coding Interview" book should be enough for cracking those questions.
Strong fluency in Data Structures & Algorithms, and of course, strong programming intuition and logical thinking skills, which goes without saying, are needed to crack them.
The following metrics were computed from 25 interview experiences for the Google Site Reliability Engineer role in Mountain View, California.
Google's interview process for their Site Reliability Engineer roles in Mountain View, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Google's Site Reliability Engineer interview process in Mountain View, California.