Google Site Reliability Engineer Interview Guide

The Google site reliability engineer (SRE) interview centers on operational judgment under production load, a different focus than the standard software engineering loop. The site reliability engineer loop leans on a live-outage troubleshooting simulation and Linux questions, like tracing what happens when a URL loads in a browser. Prepare to guide the technical depth yourself during the SRE interview, because interviewers follow wherever your reasoning leads.

This guide breaks down each stage of the Google site reliability engineer interview process, what interviewers look for, and how to prepare with real example questions, actionable tips, and resources.

Google site reliability engineer interview process

The Google site reliability engineer interview runs in two phases: a recruiter and coding screen, then a set of systems-heavy rounds worked mostly through live discussion. Google's SRE process stays team-independent until the final stage, when you enter team matching.

Here's what the interview process can look like:

• Recruiter screen: A 20-25 minute call covering your background, motivation, and interview preferences
• Coding and scripting screen: A 45-minute round on practical coding and scripting built for production scale
• Production troubleshooting: A 45-minute simulated outage worked through in a shared document
• Googleyness: A 45-minute behavioral round on collaboration, leadership, and learning mindset
• Linux or networking: A 45-minute systems round you choose based on your strengths

Recruiter screen

Google's SRE recruiter screen is a 20-25 minute call that confirms your background and maps out how the rest of the loop will run. The recruiter reviews your current role and responsibilities, then asks why you want to move into site reliability engineering at Google.

You'll set your preferences here, including your coding language and your work location. This is also where you choose your track, SWE-SRE or SysEng-SRE, and pick a Linux or networking systems round.

Recruiters look for:

• Motivation for SRE: Why you want site reliability engineering at Google specifically
• Track fit: Whether the SWE-SRE or SysEng-SRE path suits your background
• Role alignment: How your experience maps to the role's scope and level
• Logistics: Your location preferences, notice period, and compensation expectations

Recently asked questions

Here are some recently asked questions reported by candidates:

• Tell me about your current role and core responsibilities.
• Why do you want to move into site reliability engineering at Google?
• Which coding language do you want to use, and do you prefer the Linux or networking round?
• What are your preferred work locations, notice period, and salary expectations?

Coding and scripting screen

The Google SRE coding and scripting screen is a 45-minute round that starts with a simple coding task and builds toward production concerns. Interviewers care less about the base solution and more about whether it holds up at scale.

Expect the interviewer to introduce new constraints midway, then follow up on test cases and difficulty once your first solution works. Scripting is emphasized in this round, since SREs automate a large share of their operational work.

Interviewers look for:

• Production readiness: Whether your code holds up with millions or billions of inputs
• Edge-case handling: How you manage empty, oversized, and malformed inputs
• Debugging mindset: Your approach to test cases, error handling, and logging
• Scripting fluency: How comfortably you automate repetitive operational work
• Reasoning aloud: Whether you talk through your approach before and while you code

Recently asked questions

Here are some recent prompts reported by candidates:

• Read and parse an input file, run a calculation on its contents, and return the result.
• Handle the edge cases for that input: an empty file, files with billions of rows, and malformed or garbage values.
• Make failed parsing visible, so you can tell whether the input was sanitized.
• Extend your solution as new constraints arrive, including real-time processing and data that won't fit in memory.
• Perform basic string operations on parsed input.

Production troubleshooting round

The Google SRE troubleshooting round is a 45-minute simulated production outage that you work through with the interviewer. You'll get a vague starting prompt, often a service returning errors or timing out after a deployment, and drive toward the root cause.

The round runs in a shared document, where you write the commands you'd run and your hypotheses, and the interviewer supplies the expected output at each step.

Expect to explain why you're moving to each next step, since your reasoning matters as much as the fix.

Interviewers look for:

• Structured diagnosis: How you scope the outage before forming hypotheses
• Hypothesis testing: Whether you rule out causes methodically across CPU, memory, and network
• Command fluency: The Linux commands you reach for and how you read their output
• Root-cause reasoning: Whether you can explain why each step moves you closer to the cause
• Fix sequencing: How you separate a short-term fix from a long-term one

Recently asked questions

Here are some recently asked questions reported by candidates:

• A production system returns errors after a recent deployment; find the root cause.
• What clarifying questions would you ask before running anything?
• Which command would you run next, and what do you expect it to show?
• Why are you ruling out that hypothesis and moving to the next one?
• What's your short-term fix to unblock users, and your long-term fix?
• A user can't SSH into a remote machine; walk through how you'd diagnose it.
• A service's latency doubled while CPU sits at 50%; find the cause.

Googleyness round

The Google SRE Googleyness round is a 45-minute behavioral interview built around Google's cultural values. It covers collaboration, leadership, staying positive, and keeping an open learning mindset.

Googleyness is one of four attributes Google scores across its hiring process, alongside general cognitive ability, role-related knowledge, and leadership. Expect questions about how you work with teammates, lead projects, and handle friction.

Interviewers look for:

• Collaboration: How you work with teammates toward a shared outcome
• Handling disagreement: Whether you can hold a position and still move the team forward
• Dealing with difficult colleagues: How you respond when someone is uncooperative
• Learning mindset: Whether you stay open and adaptable under pressure
• Leadership: How you drive projects and support others

Recently asked questions

Here are some recent prompts reported by candidates:

• Walk me through your experience, including how you collaborate and lead projects.
• Tell me about a time you held an opinion your team didn't accept, and how you handled it.
• Describe a situation with a difficult or uncooperative colleague, and what you did.
• Tell me about a time you stayed positive and kept learning under pressure.
• Tell me about a time you failed, and what you learned.
• Describe a mistake you made and how you corrected it.

Linux and systems round

Google's SRE Linux and systems round is a 45-minute interview that measures how deep your operating system and networking knowledge goes. Open-ended prompts let you demonstrate range across the operating system and networking stack.

Expect a broad tracing prompt you take end to end, then a second systems segment built around a scripting task that escalates over three iterations, plus questions on signals, processes, and links.

Interviewers look for:

• Depth on demand: How far you can go into each layer as the interviewer follows your reasoning
• End-to-end systems knowledge: Whether you can trace a request through DNS, sockets, and the kernel
• Operating system fundamentals: Your grasp of processes, signals, and links
• Networking knowledge: Your understanding of protocols such as QUIC
• Scripting under changing requirements: How you extend a script as constraints escalate

Recently asked questions

Here are some recently asked questions reported by candidates:

• Walk through what happens end to end when you type a URL into a browser.
• Explain the QUIC protocol and the advantages it introduced.
• Describe how interrupts and signal handlers work, including signal masking.
• Write a script that pings hosts, finds the slow ones, and loops through them to print specific data, escalating across iterations.
• Compare background and foreground processes, and hard links against soft links.
• How would you find and clean up zombie processes?
• Explain inodes, and the difference between SIGTERM and SIGKILL.

How to prepare for the Google site reliability engineer interview

1. Practice a repeatable diagnosis structure: Work through outages in a fixed order: scope, hypothesize, test, root cause, then fix. A consistent structure keeps you clear under pressure in the troubleshooting round.
2. Ground your answers in fundamentals: Google tests why a system behaves the way it does, so be ready to explain the mechanics behind each command and tool.
3. Trace systems end to end: Practice explaining flows like what happens when a URL loads, from DNS resolution through sockets, interrupts, and process creation.
4. Prioritize practical coding and debugging: Focus on parsing messy input, handling edge cases, and writing test cases. The coding screen centers on production concerns more than algorithm puzzles.
5. Build a study-note question set: Compile the topics and questions you expect, then write concise notes for each. This mirrors how strong SRE candidates organize their preparation.
6. Practice with mock interviews: Run AI and peer mock interviews to work through troubleshooting and systems questions out loud, since clear reasoning carries these rounds. Book expert coaching for feedback on how you explain your thinking.

About the Google site reliability engineer role

Google site reliability engineers keep large-scale production systems reliable, blending software engineering with systems operations. Google caps operational work, known as toil, at half of an SRE's time, reserving the rest for the engineering and automation that keep services stable as they scale.

Google SREs typically focus on:

• Keeping services reliable at the scale of billions of requests
• Diagnosing and resolving production incidents
• Building tooling and scripts that reduce repetitive manual work

Additional resources

• Software Engineering Interview course
• System Design Interview course
• Security Engineer Interview course
• Behavioral Interviews for Engineers course
• Google SWE interview guide
• Google SWE interview questions
• Google interview experiences

FAQs about the Google site reliability engineer interview

What does the Google site reliability engineer interview process look like?

The Google SRE interview starts with a recruiter screen, moves to a coding and scripting screen, and finishes with a set of 45-minute rounds covering production troubleshooting, Googleyness, and a systems round in Linux or networking. After the loop, you enter team matching before an offer is finalized.

How is the Google SRE interview different from the Google SWE interview?

The Google SRE interview centers on production operations and systems knowledge, while the Google SWE interview leans more on algorithmic coding. SRE candidates face a live troubleshooting simulation, Linux internals questions, and scripting at scale, alongside the shared Googleyness behavioral round.

How many rounds are in the Google SRE interview?

The Google SRE loop in this guide runs five rounds: a recruiter screen, a coding and scripting screen, and three 45-minute onsite interviews. The count varies by track and level, and some candidates report additional coding rounds and a separate system design (NALSD) interview, so plan for a loop of five or six rounds.

What happens after you pass the Google SRE interview?

After you pass the Google SRE interview, a hiring committee of Googlers who didn't interview you reviews your packet before you enter team matching. Matching often takes a few weeks to a few months, though it can stretch toward a year in a tight-headcount market, so keep other options open while you wait.

Can you choose your programming language in the Google SRE interview?

You can use your preferred programming language in the Google SRE coding and scripting screen, and the recruiter confirms your choice during the initial call. Prepare to write production-ready, well-tested code in that language, since the screen emphasizes scale and edge cases.

Can you use AI tools in the Google SRE interview?

Google began piloting AI-assisted interview rounds in 2026, where candidates use an approved assistant on a code-comprehension task while interviewers assess how well they prompt and validate its output. The pilot started with software engineering roles and its rollout to SRE loops isn't confirmed, so check the rules for your specific loop with your recruiter.

How much does a Google site reliability engineer make?

Here are the reported compensation ranges by level for Google site reliability engineers, according to Levels.fyi:

• L3 (Software Engineer II): ~$197K
• L4 (Software Engineer III): ~$286K
• L5 (Senior Software Engineer): ~$423K
• L6 (Staff Software Engineer): ~$555K

These figures combine base salary, equity (Google Stock Units), and an annual bonus, with equity vesting over four years. Reported EMEA compensation runs lower; in Dublin, ranges run from roughly €108K to €434K by level.