SE 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 3 days. I interviewed at Google in Oct 2016
Interview
The first phase of the interview was over a mobile phone line with a lag measured in seconds, even though I provided my GMail account for a VoIP link.
The Google recruiter was lacking a technical background, but was nice and helpful, until he asked for the emails of 3 of my code monkey buddies so he can fulfil some recruiting quota. I delayed, he cut me off, end of story.
I applied through a recruiter. The process took 1 day. I interviewed at Google (Dublin, Dublin) in Oct 2015
Interview
HR did found a old project of mine I had published in github and found it could be a match to SRE team. So he contacted me by email and then a phone call with basic linux and network questions.
I applied through a recruiter. The process took 3 months. I interviewed at Google (Kirkland, WA) in Mar 2017
Interview
Two phone interviews, one onsite. First recruiter was great, second recruiter always called 5-10 minutes late if they called at all. This drew the process out much longer than necessary. Onsite was scheduled in a phone room (roughly 5x5 with two chairs and a TV) so no whiteboard board until they rolled in a temporary one halfway through the day. Interviewers were great except for one, who did not review my application prior to the interview. That one asked me a question I already had on a phone interview, after letting them know, they asked a question about web development; I am a systems engineer. I was asked to come in for a second round of onsite interviews. I did not accept.
Interview questions [1]
Question 1
Depth fist search, maps, recursion, time complexity.