What is Infrastructure as Code, and why check the plan of a change?
Review note: The answer refers to the original author's CV or target job offer — adapt it to your own experience.
Answer out loud or in your head first, then compare.
Answer
It's describing infrastructure in files that can be versioned and reviewed like application code. A tool, e.g. Terraform, compares the description with the existing resources and proposes changes. That makes it easier to recreate an environment and spot differences between intent and reality. Terragrunt helps organise the configuration and dependencies between parts of such infrastructure, e.g. for several environments sharing settings.
But the plan has to be read: it may delete a database or widen permissions. An agent shouldn't apply it to production unchecked. You also need to protect the tool's state and limit concurrent changes. Rolling back application code doesn't automatically reverse a data migration. Don't claim Terraform experience if you don't have it — understanding the purpose and risks is an honest start.
Why it matters: IaC tools are in the full scope of the offer.
Possible follow-ups: What if someone changes a resource by hand outside the versioned description?
How did it go? Be honest — “Not yet” puts the question on your review list.
Start with
- E-P01 · What is cloud computing? — AWS, Cloudflare and infrastructure
- E-P03 · What is Cloudflare, and what is it for? — AWS, Cloudflare and infrastructure
- E-P04 · How does Cloudflare differ from AWS? — AWS, Cloudflare and infrastructure
Further reading
- RAS Tech: Our Recruitment Process — All You Need to Know(opens in a new tab)Process; accessed 22.10.2026. A general description of the technical stage, internet access and AI; no guarantee of your round's format.
- Terragrunt: Overview(opens in a new tab)Accessed 22.10.2026. Shared configuration and infrastructure dependencies.