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 11 - 15 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 process took 4 weeks. I interviewed at Google (München, Bavaria) in May 2025
Interview
I was asked two questions, Both the question were of medium complexity. The interviewer was mostly interested in my coding skills, rather than understanding my approach or anything. I tried to explain my approach to the interviewer but he just wanted me finish coding and move on.
Interview questions [1]
Question 1
Code the tail command in linux when you are handling large dataset
During the technical interview process at Google, candidates can expect to encounter coding problems that primarily range from medium to hard difficulty, as categorized on platforms like LeetCode. The majority of these problems emphasize algorithmic thinking and efficient problem-solving techniques. In particular, a strong understanding of graph traversal algorithms, such as Breadth-First Search (BFS) and Depth-First Search (DFS), is crucial. These paradigms are frequently used in interview problems related to trees, graphs, backtracking, shortest path, and connectivity components.
Interview questions [1]
Question 1
Given a file system structure how can you find the size of a folder given each item is either folder with id of the items inside of it, other type is file with name and size
I've applied three months in row, two times with referral. First interview was a simple screening, then three interviews in the same day: two technical and one googliness (conflicts handling, different opinions, ideas and project structuring).
Interview questions [1]
Question 1
Average leetcode problems from all basic categories. Nothing like DP or graphs