Google Site Reliability Engineer interview questions
based on 135 ratings - Updated Apr 11, 2026
Averageinterview difficulty
Very positiveinterview experience
How others got an interview
58%
Recruiter
Recruiter
26%
Applied online
Applied online
7%
Employee Referral
Employee Referral
5%
Other
Other
3%
Campus Recruiting
Campus Recruiting
2%
In Person
In Person
Interview search
135 interviews
Viewing 26 - 30 of 135 Interviews
Google interviews FAQs
Site Reliability Engineer applicants have rated the interview process at Google with 3 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 71.6% positive. This is according to Glassdoor user ratings.
Candidates applying for Site Reliability Engineer roles take an average of 14 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at Google overall takes an average of 43 days.
Common stages of the interview process at Google as a Site Reliability Engineer according to 1 Glassdoor interviews include:
Phone interview: 100%
Here are the most commonly searched roles for interview reports -
The interview process wasn't trickery-based. It was starting with a small problem, explaining your thinking, and they expand it with more complexity and constraints. It's nothing like you're used to but fairer based on software engineering philosophy rather than trivia.
Skipped phone screen due to having a referral. Final round was 5 rounds of 45 minute interviews. 4 rounds technical, 1 behavioral/googliness interview. Spread across 2 consecutive days remotely over Google Meet.
Interview questions [1]
Question 1
Design a data structure to read a stream of temperatures and find the max within the past 24 hours
I applied through a recruiter. The process took 3 weeks. I interviewed at Google (San Diego, CA) in Sep 2017
Interview
Speak out & you will get help.
Feel Free to ask for as much information as possible. Some questions require you to ask more or state assumptions. Again, speaking out is your best friend here
Interview questions [1]
Question 1
Linux Kernel Internals, Networking, Programming, etc