Terraform is the leading infrastructure-as-code tool, and its interviews center on the concept that trips up most people: state. Master state, the plan/apply workflow, and modules, and most Terraform questions follow. Essential for DevOps, cloud, and platform roles. Here are the Terraform interview questions that actually get asked. (See also our DevOps and AWS guides.)
Fundamentals & workflow
- What is infrastructure as code, and why Terraform?
- The core workflow —
init,plan,apply,destroy. - Declarative vs imperative — how Terraform reconciles desired vs actual state.
- What are providers and resources?
State (the key topic)
- What is the Terraform state file, and why does it exist?
- Why and how do you use remote state (S3 + locking)?
- What is state locking, and why does it matter for teams?
- What happens if state drifts from reality?
Modules & practical concerns
- What are modules and why use them?
- Variables, outputs, and locals.
- Workspaces and managing multiple environments.
- How do you handle secrets in Terraform?
How to prepare
Terraform rounds probe state and the workflow verbally. Practise explaining remote state and the plan/apply cycle out loud. Greenroom runs spoken technical interviews that follow up on your reasoning. Pair it with our DevOps and cloud engineer guides.
Frequently asked questions
What are the most common Terraform interview questions?
Common Terraform questions cover infrastructure as code, the init/plan/apply/destroy workflow, declarative reconciliation of desired vs actual state, providers and resources, the state file and why it exists, remote state and state locking, state drift, modules, variables and outputs, workspaces and multiple environments, and handling secrets. State is the most heavily probed topic.
What is the Terraform state file and why is it important?
The state file maps your configuration to the real resources Terraform manages, tracking metadata and the current known state of your infrastructure. Terraform uses it to determine what to create, update or destroy on each apply. It's critical because without accurate state, Terraform can't reconcile desired versus actual infrastructure, so teams store it remotely (e.g. in S3) with locking to avoid conflicts and corruption.
Why do teams use remote state in Terraform?
Teams use remote state (for example an S3 bucket with DynamoDB locking) so the state file is shared, versioned and protected rather than living on one person's laptop. Remote state with locking prevents two people from running apply simultaneously and corrupting the state, enables collaboration, and keeps sensitive infrastructure data centralized and backed up. It's essential for any multi-person Terraform setup.
How should I prepare for a Terraform interview?
Focus on state above all — why the state file exists, remote state with locking, and drift — plus the plan/apply workflow, providers, and module design. Practise explaining remote state and how Terraform reconciles desired versus actual infrastructure out loud with a voice-based mock interview that follows up, since these rounds probe real team-level understanding.