Production Engineer → DevOps Engineer

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

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

Transition from Production Engineer to DevOps Engineer.

Transferable skills

  • Linux
  • Python / Go scripting
  • Observability

Skills to learn

  • CI/CD pipelines
  • Kubernetes
  • Terraform
  • Cloud (AWS/Azure/GCP)
  • Git & branching strategies
  • Security in pipelines

Prerequisites

  • Strong production operations experience: monitoring, incidents, deployments and on-call.
  • Linux administration and scripting (Bash, Python) used for real automation.
  • Familiarity with at least one CI/CD tool and basic container concepts.
  • Git for versioning scripts and configuration.

Step-by-step learning plan

  1. 1. Build on your Production Engineer experience

    2–4 weeks

    Leverage

    • Linux
    • Python / Go scripting
    • Observability

    Map transferable skills — Linux, Python / Go scripting, Observability — against what a DevOps Engineer needs.

  2. 2. Close the partial gaps toward DevOps Engineer

    3–6 weeks

    Improve

    • Docker

    Raise Docker to the level a DevOps Engineer relies on.

  3. 3. Learn the core of the DevOps Engineer role

    6–10 weeks

    Learn

    • CI/CD pipelines
    • Git & branching strategies
    • Terraform

    Technologies

    GitHub ActionsArgoCDHelm

    Cover the biggest gaps first: CI/CD pipelines, Git & branching strategies, Terraform.

  4. 4. Master advanced DevOps Engineer skills

    6–10 weeks

    Learn

    • Kubernetes
    • Cloud (AWS/Azure/GCP)
    • Security in pipelines

    Technologies

    AWSAzureGCP

    Handle the advanced topics: Kubernetes, Cloud (AWS/Azure/GCP), Security in pipelines.

  5. 5. Get productive with the DevOps Engineer toolchain

    4–8 weeks

    Technologies

    GitHub ActionsArgoCDHelmAWSAzureGCPVaultKafka

    Be hands-on with GitHub Actions, ArgoCD, Helm and the rest of the target stack.

  6. 6. Practise DevOps Engineer work in real conditions

    4–8 weeks

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

  7. 7. Get certified and position yourself as a DevOps Engineer

    4–8 weeks

    Technologies

    CKAHashiCorp Terraform AssociateAWS DevOps Engineer Professional

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

Learning outcomes

  • Build and maintain a CI/CD pipeline that tests and deploys an application automatically.
  • Provision infrastructure reproducibly with Terraform and version it in Git.
  • Package and operate containerised workloads with Docker and basic Kubernetes.
  • Apply infrastructure as code and GitOps practices to a real workload.

Practical projects

  • Containerise a production application — Write a Dockerfile for an app you already operate, build the image, run it locally, and verify it behaves the same as the non-containerised version.
  • Build a CI/CD pipeline from scratch — Connect a Git repository to GitHub Actions or GitLab CI: run tests on every commit, build an image on merge, and deploy to a staging environment automatically.
  • Provision infrastructure with Terraform — Take one server you currently build manually and reproduce it as a Terraform module: VM, networking, security group. Destroy and recreate it to prove reproducibility.

Alternative routes