Why Terraform shows up in almost every strong DevOps JD
Infrastructure as Code is table stakes for product-company cloud roles in India. Terraform remains the most requested tool: modules for VPCs and EKS/AKS/GKE, state management, policy-as-code hooks, and drift detection. Some teams use Terragrunt for multi-environment layouts; others evaluate Pulumi or Crossplane — we include those when the posting is clearly IaC-centred.
Interviewers care less about memorising every provider resource and more about safe change management: remote state, workspaces or separate state files, plan reviews, least-privilege IAM for runners, and how you recover from a bad apply. Cost-aware design (right-sizing, tagging, idle cleanup) increasingly appears in senior JDs.
IaC skills that separate candidates
- Module design: reusable, versioned modules vs copy-paste root modules
- State & collaboration: remote backends, locking, and CI plan/apply workflows
- Cloud depth: networking, IAM, and Kubernetes cluster provisioning — not only VMs
- Secrets: never baking secrets into state; integrating Vault, SSM, or cloud secret managers
- Policy & quality:
tflint, checkov/tfsec, and branch protection on infra repos
How we select Terraform listings
Roles appear when Terraform, Terragrunt, Pulumi, or “infrastructure as code” is explicit in the title or skills, or when our metadata tags Terraform. As with all FzlOps pages, apply links must resolve to a real posting. Combine this filter with Kubernetes jobs if you want platform-heavy IaC work.
Related guides
Every listing on this page is checked for scope and a live apply link. See how we verify jobs and the State of DevOps Hiring in India report for market context.