Skip to content
AssistedVoice
Site reliability engineer interviews

A broken system, one question at a time

SRE and production-engineering loops tend to give each interviewer one topic: practical coding, Linux internals, troubleshooting, design with real numbers, and on-call stories. In spoken rounds on a video call, press the answer shortcut for a first-person reply that works through the evidence in order.

No credit card 30 minutes free Encrypted
Example: asked “The website is down. Figure out why.”, Assisted Voice replies: First I’d pin down the scope: is it down for everyone, and what changed most recently, a deploy or a config push? Then I’d go one layer at a time. Does DNS resolve, and does the load balancer answer? If the backends are failing health checks, I’d log in to one, check the service status and read its error log. If it says no space left on device, I’d run df -h, free up space or fail over to stop the bleeding, then find out what filled the disk.

One interviewer, one topic

Google SREs wrote in 2015 that each onsite interviewer owns a topic such as programming, UNIX internals, networks or troubleshooting. Meta and LinkedIn reports split the loop much the same way. USENIX, 2015 (opens in a new tab); LinkedIn, 2017 (opens in a new tab); Substack, 2025 (opens in a new tab); LeetCode Discuss, 2025 (opens in a new tab)

Google’s own rules: its virtual-interview guide says using AI during an interview means disqualification, and a 2026 SRE/platform posting says interviews are in person in most instances. Don’t use Assisted Voice in Google’s loop. Google Careers, 2026 (opens in a new tab); Google (opens in a new tab)

Google’s column mixes Google SREs’ 2015 article with 2025 candidate reports. LinkedIn’s comes from a 2017 post that has since been taken down. Formats change by team and year.
RoundGoogleSRE: 2015 article, 2025 reportsMetaProduction Engineer, 2025LinkedInSRE, 2017 postAmazonSystem Development Engineer L5, 2025
Coding and scriptingPractical problems, not puzzlesGoogleAt least one interview, in your preferred language. Recruiters call it a practical algorithm or scripting exercise, written in Google Docs. A second-hand account adds converting human-readable file sizes to bytes. USENIX, 2015 (opens in a new tab); r/leetcode, 2025 (opens in a new tab); LinkedIn, 2025 (opens in a new tab)MetaCSV parsing plus an easy string problem in the E4 screen. Another loop combined two CSV files of dinosaur-style data into one result. Substack, 2025 (opens in a new tab); LeetCode Discuss, 2025 (opens in a new tab)LinkedInA phone screen on log parsing or calling a REST API. LinkedIn, 2017 (opens in a new tab)AmazonAn easy problem with a medium follow-up. Blind, 2025 (opens in a new tab)
Linux and OS internalsMemory, processes, signals, filesystemsGoogleRecruiters call it “Simplification”, and a commenter says it goes very deep into OS internals. Prep sites list prompts such as running out of PIDs or inodes, and say software-track candidates have swapped it for coding (prep-site claims). r/leetcode, 2025 (opens in a new tab); r/sre, 2024 (opens in a new tab); Coditioning (opens in a new tab); DataInterview, 2026 (opens in a new tab)MetaMemory management, processes versus threads, the VFS and signals. One E4 candidate counted about 30 questions in 45 minutes (one report). LeetCode Discuss, 2025 (opens in a new tab); r/leetcode, 2025 (opens in a new tab)LinkedInSystems-administration questions in the recruiter screen, then an operations screen on how the Internet works, scaling and monitoring. LinkedIn, 2017 (opens in a new tab)AmazonA Linux troubleshooting round: zombie processes, /proc and sudden network latency. Blind, 2025 (opens in a new tab)
TroubleshootingA failing system, worked from evidenceGoogleNamed in a 2025 recruiter list, and as debugging in a 2025 Bengaluru onsite the candidate called very open-ended. Taro, 2025 (opens in a new tab); r/leetcode, 2025 (opens in a new tab)Meta“A website is down” in the E4 screen. In the E5 loop, OS questions and then troubleshooting in a Linux-like environment. Substack, 2025 (opens in a new tab); LeetCode Discuss, 2025 (opens in a new tab)LinkedInLive troubleshooting on a laptop connected to a running service, with search engines and man pages allowed, plus ranking alerts that fire at once. LinkedIn, 2017 (opens in a new tab)AmazonPart of the Linux troubleshooting round above. Blind, 2025 (opens in a new tab)
Design with numbersReal capacity, not just boxesGoogleNALSD, in at least one interview. A 2025 Bengaluru candidate was asked for a highly available logging system. USENIX, 2015 (opens in a new tab); Taro, 2025 (opens in a new tab)MetaProduction-engineering design at fleet scale. One E4 candidate’s design round was verbal only. LeetCode Discuss, 2025 (opens in a new tab); r/leetcode, 2025 (opens in a new tab)LinkedInA whiteboard architecture discussion in the onsite. LinkedIn, 2017 (opens in a new tab)AmazonA system design round. Blind, 2025 (opens in a new tab)
Behavioural and on-callIncidents, outages, valuesGoogleGoogleyness and Leadership. A second-hand account of a hiring-manager round covered on-call, outages and postmortems. A hiring committee, not the manager, decides. USENIX, 2015 (opens in a new tab); r/leetcode, 2025 (opens in a new tab); LinkedIn, 2025 (opens in a new tab)MetaA behavioural round in both the E4 and E5 loops. Substack, 2025 (opens in a new tab); LeetCode Discuss, 2025 (opens in a new tab)LinkedInA conversation with a manager who asks for war stories. LinkedIn, 2017 (opens in a new tab)AmazonA Bar Raiser, and Leadership Principle questions on operational excellence. Blind, 2025 (opens in a new tab)

Where Assisted Voice helps

Live video-call rounds on Zoom, Google Meet and Microsoft Teams, where the company allows it.

  • Coding and scripting questions shown on screen: capture the problem, and the Code tab gives an approach and working code.
  • Linux, OS and spoken troubleshooting questions: press the answer shortcut for a first-person answer.
  • Design rounds: the Diagram tab draws the components and data flow as the question is asked.
  • Incident and on-call stories: answers draw on your resume and the files you upload, such as notes on incidents you handled.

Where it doesn’t apply

Even on Zoom, Google Meet or Microsoft Teams, it isn’t for these.

The interviewer plays the system. You ask for evidence.

That’s how one prep site sums up the troubleshooting round. From the reports, this is how a round moves, turn by turn. DataInterview, 2026 (opens in a new tab)

  1. Interviewer

    A vague symptom

    “The website is down”, or a service throwing errors and timeouts after a deployment. In one Meta report, the cause turned out to be a full disk.

    Substack, 2025 (opens in a new tab); DataInterview, 2026 (opens in a new tab)

  2. You

    Scope it, and ask what changed

    Who’s affected, and what changed most recently? The Google SRE Book’s troubleshooting chapter asks that second question too.

    SRE Book, 2016 (opens in a new tab)

  3. You

    Ask for evidence, one piece at a time

    Logs, metrics or the output of a command, each as its own request.

    DataInterview, 2026 (opens in a new tab)

  4. Interviewer

    Answers as the system would

    They may also change the conditions as you get closer, so keep checking your assumptions.

    Substack, 2025 (opens in a new tab); DataInterview, 2026 (opens in a new tab)

  5. Interviewer

    Pulls you back to the method

    One Meta interviewer had a candidate start again and go step by step instead of listing ideas.

    r/leetcode, 2025 (opens in a new tab)

  6. You

    Stop the bleeding, then find the cause

    Make the system work as well as it can first. The SRE Book’s order is triage, examine, diagnose, then test and treat.

    SRE Book, 2016 (opens in a new tab)

  7. You

    Close with two fixes

    A short-term fix that restores service, and a longer-term one so it doesn’t happen again.

    DataInterview, 2026 (opens in a new tab)

How long
30 or 45 minutes by one prep site’s count, and 45 for the systems round in a Meta prep guide. Both are prep-site figures. Coditioning (opens in a new tab); DataInterview, 2026 (opens in a new tab)
The alert-triage variant
LinkedIn’s 2017 post describes ranking a set of alerts that all fire at once, explaining why, then answering troubleshooting questions. It’s modelled on being on call. LinkedIn, 2017 (opens in a new tab)
Spoken or hands-on
When it’s spoken on a video call, the answer shortcut gives a first-person reply that works through the evidence in order. LinkedIn’s laptop on a running service and Meta’s Linux-like environment are hands-on, and Assisted Voice doesn’t apply there. LinkedIn, 2017 (opens in a new tab); LeetCode Discuss, 2025 (opens in a new tab)

Design with numbers, not magic boxes

Google calls its SRE design round non-abstract large system design, or NALSD. Its workbook runs the design in two phases, and every box on the whiteboard has to become a resource estimate. SRE Workbook, 2018 (opens in a new tab)

NALSD is Google’s round, and Google’s virtual-interview guide says using AI during an interview means disqualification. Use this section to prepare, and leave Assisted Voice out of it. In design rounds elsewhere on Zoom, Google Meet or Microsoft Teams, where it’s allowed, the Diagram tab draws the components and data flow as the question is asked. Google (opens in a new tab)

  1. Phase 1

    Basic design

    1. Is it possible?
    2. Can we do better?
  2. Phase 2

    Scale it up

    1. Is it feasible?
    2. Is it resilient?
    3. Can we do better?

A box on the whiteboard labelled “storage”

has to become

How many machines and disks, at what throughput and latency

Naming a well-known technology isn’t enough. Google expects realistic throughput and storage estimates. USENIX, 2015 (opens in a new tab); SRE Workbook, 2018 (opens in a new tab)

Design prompts candidates got

Watch for

Where incidents, on-call and SLOs come up

In these reports, incident and on-call questions turn up inside other rounds: a manager conversation, a technical stage, or Leadership Principle questions. LinkedIn, 2017 (opens in a new tab); Blind, 2025 (opens in a new tab); GitLab, 2026 (opens in a new tab)

  • War stories and alert triage

    LinkedIn’s 2017 post says managers ask for war stories, and its alert-triage exercise is modelled on being on call.

    LinkedIn, 2017 (opens in a new tab)

  • Incident review as a stage

    GitLab’s 2026 SRE posting puts incident review in the core technical stage, and its handbook lists on-call and incident management among the experience it looks for.

    GitLab, 2026 (opens in a new tab); GitLab Handbook (opens in a new tab)

  • Operational excellence at Amazon

    System Development Engineer L5 loops include Leadership Principle questions on operational excellence, automation and reliability.

    Blind, 2025 (opens in a new tab)

  • SLOs inside design and behavioural rounds

    A prep site says SLO and error-budget questions tend to sit inside design and behavioural rounds rather than a round of their own. That’s a prep-site claim, based on one 2025 report.

    DataInterview, 2026 (opens in a new tab)

Other SRE loops, as reported

Media.net’s 2026 loop opens with an online Linux test and machine coding, both outside what Assisted Voice does. LeetCode Discuss, 2026 (opens in a new tab)

Individual candidate reports and published process pages, not official policy. Formats change by team and year.
CompanyFormat reportedSource
GitLabSRE, Intermediate to Senior Staff, 2026A recruiter call, a core technical stage on architecture and incident review, a hiring manager, a team-specific peer technical interview and a skip-level interview.GitLab, 2026 (opens in a new tab)
AtlassianSRE, Bengaluru and US, 2022–2025A Bengaluru review lists five rounds: screen and coding, coding, design, craft and values. A 2025 US review describes a technical and a design interview on one day, and a 2024 reviewer called the coding “gotcha”.Glassdoor, 2025 (opens in a new tab)
Media.netSRE, Bangalore, 2026A Linux OA of 15 scenario questions, then machine coding in C++ sockets: a TCP key-value server, extended to a proxy and then a load balancer. Then a discussion of load-balancing algorithms, consistent hashing and CAP, a second technical round, managerial and HR.LeetCode Discuss, 2026 (opens in a new tab)
PhonePeSRE Engineer, campus, 2023Rounds on networking theory, shell-scripting basics and HR.Glassdoor, 2023 (opens in a new tab)
MetaProduction Engineer, prep-site summaryFive 45-minute rounds (PE basics, PE coding, systems, SWE coding and behavioural) on CoderPad, according to a prep site, not Meta. Meta’s hiring FAQ says outside AI tools aren’t allowed; only the tools inside its interview environment may be used.Coditioning (opens in a new tab); Meta Careers (opens in a new tab)
FAQ

Questions, answered

Contact us
  • Usually a recruiter screen, one or two technical screens, then four or five interviews that each cover one topic: coding or scripting, Linux and OS internals, troubleshooting, design with real numbers, and a behavioural or hiring-manager round about incidents and on-call. That’s the shape Google SREs described in 2015, and Meta and LinkedIn reports split the loop in a similar way.

Sources

Last reviewed . Candidate reports are paraphrased, and formats vary by team, location and year.

  1. Hiring Site Reliability Engineers, written by Google SREs (;login: magazine)USENIX, 2015 (opens in a new tab)
  2. Non-abstract large system design (Google SRE Workbook, chapter 12)SRE Workbook, 2018 (opens in a new tab)
  3. SRE principles and flashcards to design NALSDGoogle Cloud Blog, 2020 (opens in a new tab)
  4. Effective troubleshooting (Google SRE Book)SRE Book, 2016 (opens in a new tab)
  5. Senior Infrastructure Software Engineer (SRE/Platform) job postingGoogle Careers, 2026 (opens in a new tab)
  6. Guidelines for virtual interviews at Google (candidate guide)Google (opens in a new tab)
  7. Hiring SREs at LinkedIn (page since taken down)LinkedIn, 2017 (opens in a new tab)
  8. Google SE SRE interview, BengaluruTaro, 2025 (opens in a new tab)
  9. Google Systems Engineer, SRE interviewr/leetcode, 2025 (opens in a new tab)
  10. SE SRE interview at Googler/sre, 2024 (opens in a new tab)
  11. Expected an NALSD interview, got abstract system designBlind, 2025 (opens in a new tab)
  12. Meta E4 Production Engineer interview experienceSubstack, 2025 (opens in a new tab)
  13. Meta E5 Production Engineer phone screen and full loop, London (passed)LeetCode Discuss, 2025 (opens in a new tab)
  14. Meta Production Engineer E4 interview experiencer/leetcode, 2025 (opens in a new tab)
  15. Meta Production Engineer interview guide (prep site)Coditioning (opens in a new tab)
  16. Google SRE interview questions (prep site)Coditioning (opens in a new tab)
  17. SRE course: the troubleshooting round (prep site)DataInterview, 2026 (opens in a new tab)
  18. Google Site Reliability Engineer interview guide (prep site)DataInterview, 2026 (opens in a new tab)
  19. SRE roles and interview loops (prep site)DataInterview, 2026 (opens in a new tab)
  20. Media.net SRE interview experience, BangaloreLeetCode Discuss, 2026 (opens in a new tab)
  21. PhonePe SRE Engineer interview questionsGlassdoor, 2023 (opens in a new tab)
  22. Atlassian Site Reliability Engineer interview questions (India)Glassdoor, 2025 (opens in a new tab)
  23. Amazon System vs Software Development Engineer interview processBlind, 2025 (opens in a new tab)
  24. Site Reliability Engineer job postingGitLab, 2026 (opens in a new tab)
  25. Interviewing at GitLab: InfrastructureGitLab Handbook (opens in a new tab)
  26. Google SRE interview experience, as told by a friendLinkedIn, 2025 (opens in a new tab)
  27. Hiring process FAQMeta Careers (opens in a new tab)

Work the problem one step at a time

Your first 30 minutes are free. After that it’s $5 an hour, pay as you go, with no subscription.

Start free — 30 minutes, no card
No credit card 30 minutes free Encrypted