The hiring process was fairly straightforward.
I was approached by a recruiter on LinkedIn, who saw that I would be a good fit for a position in several locations.
I had to pass a very brief introductory round of questions by this recruiter, which was painless if you had the experience the job required. They did not ask questions out of the blue, and you were given the opportunity to look over the information before you were asked.
I would take the opportunity to look over the information provided; don't just jump into the interview without reviewing other posts here.
I got past the initial round and then it was onto the technical review by another current Site Reliability Engineer. It is part of their job to consistently get involved in bringing in new talent, and I enjoyed that knowledge.
I feel that the questions were fair and that you had plenty of time to prepare if you had not been on the market for a while, like myself.
I unfortunately did not get asked to attend an in-person interview because I lacked some specific knowledge they were looking for on the inner workings of the Linux operating system.
Understand how process control works in Linux.
Know your signals and how job scheduling is handled in the most recent iterations. Do not be content with older knowledge of how things work.
The following metrics were computed from 71 interview experiences for the Google Site Reliability Engineer role in United States.
Google's interview process for their Site Reliability Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Google's Site Reliability Engineer interview process in United States.