Technical screening questions
Ask for one example per question and listen for specifics.
- How do you structure modules? A good answer: Small reusable modules with clear inputs and outputs.
- How do you manage state? A good answer: Remote backend, locking and separation by environment.
- How do you test Terraform? A good answer: Validate, plan review and test frameworks.
- How do you handle secrets? A good answer: Secret managers instead of state or code.
- How do you handle drift? A good answer: Detection, import and reconciliation.
Quick screening questions
Use these when you have only a few minutes.
- How do you structure Terraform modules for reuse?
- How do you manage state and locking across a team?
- How do you detect and handle configuration drift?
What separates the levels
Match the level to the requirement before you submit.
- Junior: edits modules.
- Mid: writes modules and pipelines.
- Senior: designs the IaC platform.
Red flags
Any of these is a reason to probe further.
- Only edited existing code.
- Cannot explain state.
- No pipeline.
Tools you should hear mentioned
A Terraform engineer with real experience usually names several of these without prompting.
- Terraform
- A cloud provider
- Terragrunt
- CI/CD tools
- Policy as code
- Git
Run the call well
Ask for the last project first, then dig into the second or third question. Take notes on versions, team size and outcomes, and record them with the submission so the vendor’s later technical interview does not surprise you.
Frequently asked questions
How long should a Terraform engineer screening call take?
Fifteen to twenty minutes is enough to cover the project, three technical questions and availability, rate and work authorization.
Do recruiters need to know the technology?
Working vocabulary is enough. Use the sourcing guide for the role and listen for specifics instead of judging technical depth yourself.