Learning priority #6 of 10

Terraform and infrastructure as code

Terraform has 94 positions plus 49 for Infrastructure as Code. AWS+Terraform co-occur in 68 positions, and Terraform appears in 20% of DevOps roles (30 of 149) and in 30 Data Engineering roles. It is a strong add-on once AWS and containers are in place.

4,022 remote positions from 975 source pagesData captured October 2026
Priority
#6
in the ranked recommendations
Positions naming any
118
9.3% of skill-tagged listings
Positions naming all
25
ask for the full bundle
Largest family
DevOps / SRE

The skills in this priority

How the bundle overlaps

Positions naming both skills in each pair

SkillTerraformInfrastructure as Code
Terraform9425
Infrastructure as Code2549

The diagonal shows each skill's own total.

Where it pays off

Role families of positions naming any skill in the priority

A practical sequence

  1. Learn the Terraform workflow: providers, resources, variables, outputs, plan and apply.
  2. Understand state: remote backends, locking and why state must never be edited by hand.
  3. Refactor into reusable modules with clear inputs and outputs.
  4. Run Terraform in CI with plan output on pull requests and gated applies.
  5. Add policy and drift detection, and practice importing existing resources.

A portfolio project that proves it

Define a small but realistic cloud environment (network, compute, storage and IAM) as Terraform modules with remote state, run plan in CI on every pull request, and show a clean destroy and rebuild.

How to show each skill

  • Terraform: Write reusable Terraform modules that provision a small environment, use remote state with locking, and run terraform plan automatically on pull requests.
  • Infrastructure as Code: Provision a complete environment from code with Terraform or a similar tool, run plans in CI on pull requests, and show that it can be destroyed and recreated cleanly.