SRE applicants have rated the interview process at Google with 4 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 66.4% positive. This is according to Glassdoor user ratings.
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 2 weeks. I interviewed at Google (Bengaluru) in Jun 2015
Interview
A technical recruiter did a small screening to know my strengths and weakness and scheduled a telephonic round. I asked for a weeks time.
One telephonic round, call was from Australia. Site Reliability Engineer Role.
Interview questions [1]
Question 1
A jigsaw puzzle with peices protrduing out or in. Can you quickly say, given the size of puzzle and pieces whether it is solvabale or not
I applied online. The process took 3 weeks. I interviewed at Google (New York, NY) in Apr 2012
Interview
Phone screen followed by onsite interview. I was asked "what is an RPC" call, I sited a form of IPC followed by a number of examples. I thought I answered was sufficient, they were looking for something outside of the client/server model specific to Java RPC stub calls and such. I thought this was odd given that Java development wasn't my forte.
Interview questions [1]
Question 1
There wasn't any question that was overly difficult, they were looking for a developer mostly and I just wasn't at that level, it's not clear how they separate SRE from DevOps to Developer.
I applied through an employee referral. The process took 2 weeks. I interviewed at Google (Los Angeles, CA) in Feb 2014
Interview
Was contacted by one recruiter to get information from me which they then sent to another recruiter in my area. Did a little back and forth with that recruiter, then scheduled the phone screen interview. Recruiter was helpful and answered any questions I had. They provided many links of topics I should know for the phone screen. Phone screen was on time, however it was quite obvious that they matched a phone screen interviewer who did not use the language I used (or did a hell of a job pretending they had no idea what pointers were), which was disappointing. If you make it past this round, you will have an on site interview. However, I was not lucky enough to have this opportunity.
Interview questions [1]
Question 1
Non-disclosure agreement. That being said, for an unexpected question, I was asked about a specific part of the language I was interviewing with that had no connection with any part of a normal CS interview I have ever had.