Terraform resume examples for infrastructure engineers
Terraform has become the standard IaC tool for cloud infrastructure — it appears in the majority of DevOps and SRE job descriptions regardless of cloud provider. The gap between a junior Terraform user and a senior infrastructure engineer shows up clearly in how you phrase your resume bullets.
What recruiters look for
Module authorship vs. consumption — writing reusable modules is a seniority signal. List the providers you've written modules for (AWS, GCP, Azure) and whether they're published to an internal or public registry.
State management — remote state in S3/GCS/Azure with locking (DynamoDB, GCS versioning), workspace strategies for environment separation, and any state migration experience. Ops engineers want to see you've thought about drift and blast radius.
CI/CD integration — Terraform running in GitHub Actions, GitLab CI, Atlantis, or Spacelift. Manual terraform apply is a red flag in 2026 job descriptions; show it runs in a pipeline.
Scale indicators — number of resources managed, number of environments, multi-region or multi-account configurations. A one-person startup and a 500-person organisation have very different Terraform footprints.
How to phrase it — weak vs strong
Used Terraform to provision AWS infrastructure
Managed 3,000+ AWS resources across 12 environments via Terraform; structured as a module library with remote state in S3/DynamoDB; integrated with Atlantis for PR-based plan and apply workflows
Wrote Terraform modules for our team
Authored 18 reusable Terraform modules (VPC, EKS, RDS Aurora) used by 6 product teams; published to private Terraform Registry; enforced tagging and naming standards that reduced mis-tagged cost attribution by 85%
Migrated infrastructure to Terraform from manual provisioning
Led migration of 600 manually provisioned AWS resources to Terraform over 8 weeks; zero downtime using targeted apply and import; eliminated 3 hours/week of manual change work
Set up Terraform CI/CD for the infrastructure team
Built a Spacelift-based GitOps workflow for infrastructure changes; enforced plan review gates and policy-as-code checks via OPA; reduced average infrastructure change lead time from 3 days to 4 hours
Related skills in this category
Engineers hiring for Terraform roles often look for these adjacent skills. Including them in your resume — where you genuinely have the experience — improves your match score across a wider set of job descriptions.
Frequently asked questions
Should I list Terragrunt separately from Terraform on my resume?
Yes. Terragrunt is a wrapper layer with its own patterns (DRY configurations, remote_state blocks, run-all) and signals infrastructure-at-scale thinking. List them separately: 'Terraform + Terragrunt' in your skills section, and reference Terragrunt explicitly in any bullet where it was the orchestration layer.
How do I quantify Terraform experience on a resume?
Use resource count (resources under management), environment count, number of teams served, and time-based efficiency gains. If you don't know exact resource counts, run 'terraform state list | wc -l' in your state directory — it gives you the number.
Is CDK an equivalent substitute for Terraform on a resume?
They fill the same IaC niche but are not interchangeable in ATS scoring — a JD mentioning 'Terraform' will penalise a resume that only lists CDK. If you have both, list both. If you only have CDK, note it and mention your Terraform familiarity; most concepts transfer directly.
Related guides
Tailor your resume for this role
Free skill-gap analysis — no credit card. Paste your resume and any DevOps, SRE, or data engineering job description. Get an ATS score, gap breakdown, and domain-aware AI rewrite.