gitGood.dev

SRE / DevOps Interview Prep

An interview prep path for SRE and DevOps loops. Heavy on networking, operating systems, and infrastructure-as-code MCQs, paired with the system-design topics interviewers reach for (rate-limiting, queues, load-balancing) and the behavioral themes that screen for incident ownership and judgment under ambiguity.

Site Reliability / DevOps EngineerMid~45h5 sections17 items
Section 1 of 5

Operating systems and networking

SRE loops assume fluency with how Linux schedules, how memory is laid out, and how TCP behaves under load. Anchor these before climbing into orchestration.

  1. 01MCQOperating Systems questions (25 suggested)Multiple choice category
  2. 02MCQNetworking questions (25 suggested)Multiple choice category
Section 2 of 5

DevOps and infrastructure-as-code

The tools the role lives in. Terraform and Kubernetes both surface in senior SRE interviews - know the primitives, the failure modes, and the trade-offs between them.

  1. 01MCQDevOps questions (20 suggested)Multiple choice category
  2. 02MCQKubernetes questions (20 suggested)Multiple choice category
  3. 03MCQTerraform questions (15 suggested)Multiple choice category
Section 3 of 5

Coding: reliability and concurrency

SRE coding rounds are usually pragmatic - rate-limiting, parsing logs, simple concurrency. Practice clean code and explicit error handling, not algorithmic acrobatics.

  1. 01CodeLRU CacheCoding · Hard
  2. 02CodeToken-Bucket Rate LimiterCoding · Hard
  3. 03CodeDesign TwitterCoding · Hard
Section 4 of 5

System design: infrastructure primitives

These are the bounded designs SRE interviewers reach for. Each one is a vehicle for the same conversation: what fails, how you detect it, how you recover.

  1. 01DesignDesign a Rate Limiter (API Throttling)System Design · Medium
  2. 02DesignDesign a Distributed Cache (Memcached / Redis Cluster)System Design · Hard
  3. 03DesignDesign a Notifications / Pub-Sub System (Kafka / SNS / SQS)System Design · Hard
  4. 04DesignDesign a Web CrawlerSystem Design · Hard
Section 5 of 5

Behavioral: incident ownership and ambiguity

SRE behavioral rounds screen hard for incident ownership and judgment under ambiguity. Have one strong story per theme below, with concrete numbers (MTTR, blast radius, customer impact).

  1. 01BehavioralMissed Deadline or Production IncidentBehavioral · General
  2. 02BehavioralOwnership (Amazon Leadership Principle)Behavioral · Amazon LP
  3. 03BehavioralDealing with AmbiguityBehavioral · General
  4. 04BehavioralDive Deep (Amazon Leadership Principle)Behavioral · Amazon LP
  5. 05BehavioralLearning from FailureBehavioral · Microsoft

Browse other learning paths

Three role-targeted paths are live: Backend, SRE / DevOps, and ML Engineer. More are on the way - if you have a role you want covered, let us know.

View all paths →