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 31 - 35 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 -
Two phone screens, one on-site. Wasn't easy and I didn't pass in the end, but I enjoyed the experience. I might try again in the future, as they will contact you again after a year or so.
Interview questions [1]
Question 1
What is the function of inodes in a Linux filesystem?
15 minute phone screen, 1 hour phone interview / google doc whiteboard, then virtual onsite with 7 leetcode-style problems back-to-back. exhausting and poorly paced. hiring committee ghosted me with no feedback or reason given.
Interview questions [1]
Question 1
data structures and algorithms, optimizating your solution (n2 -> n log n -> n), 5-6 leetcode medium / 1-2 hard. be prepared for non-stop 45 minutes of coding, barely any time for you to ask questions that aren't about the problem
First I got an online coding assessment. That was followed by a phone screening that went through a coding problem. Then, an on-site that consisted of 4 interviews, each technical with limited discussion of anything else.
Interview questions [1]
Question 1
General algorithm questions. Nothing too complicated, but in person interview was all day and the pressure is high.