A recruiter reached out by email.
The first call with the recruiter included an initial screening with basic Linux and algorithmic questions.
Next was a telephonic coding interview. The question was straightforward, and I came up with a multi-threaded solution for efficiency reasons.
I was invited for an onsite interview.
The preparation materials provided for the interview process were amazing.
This was my first time interviewing for Google, so although I prepared, I felt I needed to prepare in a different manner. I didn't know any Google employees personally either, so honestly, I didn't know what to expect.
The interviews included:
The Linux session went well.
The system design session was okay; I should have provided more hard numbers.
Programming was a different story. At least in one of the sessions, I was caught by surprise by the simplicity of the problem. Nevertheless, I definitely could have done better.
I figured it would be a failure midway through the day itself, and that probably affected the interviews in the second half of the day.
See above
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.