DevOps Engineer → Site Reliability Engineer

A realistic transition from DevOps Engineer to Site Reliability Engineer: transferable skills, the gaps to close, a step-by-step learning plan and alternative routes. Estimated skill overlap 50%. Difficulty: Medium.

Difficulty: Medium7 stepsDuration: 9 to 13 monthsOverlap: 50%

Transition from DevOps Engineer to Site Reliability Engineer.

Transferable skills

  • Kubernetes
  • Programming (Go/Python)
  • Linux internals
  • Terraform

Skills to learn

  • SLO & error budgets
  • Performance engineering
  • Distributed systems
  • Incident command

Prerequisites

  • Solid DevOps experience: CI/CD, infrastructure as code, containers and a cloud provider.
  • A programming language (Python or Go) used for real automation, not just scripts.
  • Linux internals and performance troubleshooting at the process level.
  • Exposure to incident response and on-call rotations.

Step-by-step learning plan

  1. 1. Build on your DevOps Engineer experience

    2–4 weeks

    Leverage

    • Kubernetes
    • Programming (Go/Python)
    • Linux internals
    • Terraform

    Map transferable skills — Kubernetes, Programming (Go/Python), Linux internals — against what a Site Reliability Engineer needs.

  2. 2. Close the partial gaps toward Site Reliability Engineer

    3–6 weeks

    Improve

    • Observability & tracing

    Raise Observability & tracing to the level a Site Reliability Engineer relies on.

  3. 3. Learn the core of the Site Reliability Engineer role

    6–10 weeks

    Learn

    • SLO & error budgets
    • Incident command

    Technologies

    GoOpenTelemetryLoki

    Cover the biggest gaps first: SLO & error budgets, Incident command.

  4. 4. Master advanced Site Reliability Engineer skills

    6–10 weeks

    Learn

    • Performance engineering
    • Distributed systems

    Technologies

    TempoPostgreSQLEnvoy

    Handle the advanced topics: Performance engineering, Distributed systems.

  5. 5. Get productive with the Site Reliability Engineer toolchain

    4–8 weeks

    Technologies

    GoOpenTelemetryLokiTempoPostgreSQLEnvoyIstioPagerDuty

    Be hands-on with Go, OpenTelemetry, Loki and the rest of the target stack.

  6. 6. Practise Site Reliability Engineer work in real conditions

    4–8 weeks

    Ship a portfolio project or take on Site Reliability Engineer tasks at work.

  7. 7. Get certified and position yourself as a Site Reliability Engineer

    4–8 weeks

    Technologies

    CKA / CKADGoogle Professional Cloud DevOps EngineerAWS Solutions Architect

    Update your CV and LinkedIn around Site Reliability Engineer, then apply to target roles.

Learning outcomes

  • Define SLI and SLO and use error budgets to arbitrate between features and reliability.
  • Instrument a service with metrics, logs and traces using OpenTelemetry.
  • Reduce operational toil through automation and runbooks.
  • Lead incident response and write blameless post-mortems that drive change.

Practical projects

  • Define an SLO for a service you run — Pick a service, choose a user-facing SLI (request success rate or latency), set an SLO (e.g. 99.9%), and compute the monthly error budget. Present it to a product owner to practise the negotiation.
  • Instrument a service with OpenTelemetry — Add metrics and traces to a small service, visualise them in Grafana or Jaeger, and answer "where is the time going?" for a slow request.
  • Automate an on-call toil — Identify a repetitive on-call task (restart, cleanup, check), automate it with a script or tool, and measure the toil reduction over a sprint.

Alternative routes