Production Engineer → Site Reliability Engineer

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

Difficulty: Hard6 stepsDuration: 16 to 20 monthsOverlap: 42%

Transition from Production Engineer to Site Reliability Engineer.

Transferable skills

  • Observability & tracing
  • Programming (Go/Python)
  • Linux internals
  • Incident command

Skills to learn

  • Kubernetes
  • SLO & error budgets
  • Performance engineering
  • Terraform
  • Distributed systems

Prerequisites

  • Strong production operations experience: monitoring, incidents, releases and on-call.
  • A programming language used for real automation (Python or Go preferred).
  • Linux internals and performance troubleshooting at the process and kernel level.
  • Familiarity with containers and at least basic Kubernetes concepts.

Step-by-step learning plan

  1. 1. Build on your Production Engineer experience

    2–4 weeks

    Leverage

    • Observability & tracing
    • Programming (Go/Python)
    • Linux internals
    • Incident command

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

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

    6–10 weeks

    Learn

    • SLO & error budgets
    • Kubernetes
    • Performance engineering

    Technologies

    GoOpenTelemetryLoki

    Cover the biggest gaps first: SLO & error budgets, Kubernetes, Performance engineering.

  3. 3. Master advanced Site Reliability Engineer skills

    6–10 weeks

    Learn

    • Distributed systems
    • Terraform

    Technologies

    TempoArgoCDAWS

    Handle the advanced topics: Distributed systems, Terraform.

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

    4–8 weeks

    Technologies

    GoOpenTelemetryLokiTempoArgoCDAWSGCPKafka

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

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

    4–8 weeks

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

  6. 6. 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 — Pick a service you run, choose a user-facing SLI (e.g. request success rate), set an SLO and compute the monthly error budget.
  • 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?”.
  • Automate an on-call toil — Identify a repetitive on-call task, automate it with a script or tool, and measure the toil reduction over a sprint.

Alternative routes