CI/CD Engineer → GitOps Engineer

A realistic transition from CI/CD Engineer to GitOps Engineer: transferable skills, the gaps to close, a step-by-step learning plan and alternative routes. Estimated skill overlap 10%. Difficulty: Medium.

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

Transition from CI/CD Engineer to GitOps Engineer.

Skills to learn

  • GitOps (ArgoCD/Flux)
  • Helm & Kustomize
  • Terraform
  • Git workflows
  • CI/CD
  • Policy as code (OPA)

Step-by-step learning plan

  1. 1. Build on your CI/CD Engineer experience

    2–4 weeks

    Map your current strengths against the GitOps Engineer role.

  2. 2. Close the partial gaps toward GitOps Engineer

    3–6 weeks

    Improve

    • Kubernetes

    Raise Kubernetes to the level a GitOps Engineer relies on.

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

    6–10 weeks

    Learn

    • GitOps (ArgoCD/Flux)
    • Git workflows
    • Helm & Kustomize
    • CI/CD

    Technologies

    FluxKustomizeCrossplane

    Cover the biggest gaps first: GitOps (ArgoCD/Flux), Git workflows, Helm & Kustomize.

  4. 4. Master advanced GitOps Engineer skills

    6–10 weeks

    Learn

    • Terraform
    • Observability
    • Policy as code (OPA)

    Technologies

    OPAGrafanaAWS

    Handle the advanced topics: Terraform, Observability, Policy as code (OPA).

  5. 5. Get productive with the GitOps Engineer toolchain

    4–8 weeks

    Technologies

    FluxKustomizeCrossplaneOPAGrafanaAWSGCP

    Be hands-on with Flux, Kustomize, Crossplane and the rest of the target stack.

  6. 6. Practise GitOps Engineer work in real conditions

    4–8 weeks

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

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

    4–8 weeks

    Technologies

    CKAArgo Project CertifiedTerraform Associate

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

Alternative routes