My current work involves Azure, but most deployments and changes are still done manually through the portal. I have built up solid Azure experience across several projects and understand services, architecture, networking, identity, security, and how different resources fit together. Outside work, I have been learning Terraform and Infrastructure as Code, including resource deployment, modules, variables, outputs, dependencies, and state. I have also created a basic Azure DevOps CI/CD pipeline to understand how infrastructure changes can be planned, reviewed, and deployed.
Although I have not used Terraform professionally yet, I feel capable of building an environment from scratch for a technical assessment or personal project. That could include networking, application services, databases, monitoring, identity and access controls, private connectivity, reusable modules, and a simple deployment pipeline. I know it would take me longer than someone with extensive production experience, and I may still have gaps around areas such as remote state, imports, recovery, testing, and troubleshooting failed deployments.
I am interested in cloud engineering, DevOps, or platform roles where Azure infrastructure is managed through Terraform or another IaC tool. How much professional Terraform experience would employers typically expect? Is strong Azure knowledge combined with solid personal Terraform projects enough to apply, even if my previous workplace relied mainly on portal-based deployments?
4 Answers
Make sure your projects demonstrate more than Terraform syntax and a successful apply. Build a complete environment, such as a small three-tier application with networking, private connectivity, identity, RBAC, monitoring, and a database. Use remote state, reusable modules, variables and outputs, and a CI/CD workflow with validation and approval steps.
Also practice importing existing resources, handling state safely, recovering from failed changes, managing secrets, and explaining how you would monitor and roll back a deployment. The important question is whether you understand the operational consequences of the code, not just whether you can create resources.
There is no single readiness level because cloud engineer, DevOps, and platform roles can have very different expectations. Some positions focus heavily on architecture and Azure services, while others expect deep experience with pipelines, state management, testing, Kubernetes, networking, or platform design.
Read the job descriptions carefully and apply to roles where your Azure background is relevant. In an interview, explain what you have done professionally, what you have built independently, and where you are still developing. A strong understanding of Azure combined with the ability to learn Terraform is often more valuable than someone who knows Terraform commands but does not understand the infrastructure they are creating.
Be realistic about the gap between personal practice and production experience. You may understand the tools well, but production work also involves existing conventions, shared modules, state ownership, code review, change control, security requirements, and diagnosing failures under pressure. That does not mean you need to wait before applying; it means you should describe your level accurately and be ready to learn those practices on the job.
A focused portfolio project can help a lot. Host a small application, automate its infrastructure, document the architecture, show how secrets are handled, and explain monitoring, recovery, and cost decisions. A complete, thoughtfully designed project is more convincing than a large collection of isolated resource definitions.
You should not let the lack of professional Terraform experience stop you applying. If you already understand Azure architecture, that is a major advantage; Terraform is a way of describing and managing that architecture rather than a replacement for understanding it.
Most teams are not creating an entire environment from zero every week. The day-to-day work is more likely to involve modifying existing modules, adding resources, reviewing pull requests, troubleshooting state and pipelines, and investigating why a deployment did not produce the expected result. Be honest in interviews that your production Azure work has mainly been portal-based, while you have built Terraform environments and pipelines independently. Demonstrating that you learn outside work is generally a positive signal, so start applying rather than waiting until you meet every requirement.
That makes sense. I can design Azure solutions and have also reproduced many of them with Terraform, although writing everything from scratch takes me longer. I was mainly worried that employers would dismiss the experience because it was not gained in a job.
A basic three-tier setup with networking and proper RBAC is a reasonable practical benchmark for a mid-level engineer. If you have only done that manually, it still proves useful Azure knowledge, but you should build at least one comparable environment with Terraform before presenting yourself as fully experienced with IaC.