Terraform vs Pulumi vs CloudFormation: Which IaC Skills to List on Your Resume in 2026

Quick Answer: In 2026, list Terraform first on any DevOps, Cloud, or Platform Engineer resume — it appears in roughly three times more job postings than CloudFormation and remains the de facto multi-cloud standard with a 60-76% market share. Add CloudFormation if you have shipped real AWS-native work, since it still anchors many AWS-only shops. Add Pulumi only if you have used it in production, because it is gaining traction quickly with developer-centric teams but is still a differentiator rather than a baseline. OpenTofu is now a credible signal for senior engineers and worth listing if you have actually migrated state. Never list all four to look complete: recruiters and ATS systems read tool stuffing as a junior signal, and hiring managers will probe any tool you name in the first technical screen.

The Infrastructure-as-Code market crossed roughly 2.1 billion US dollars in 2026, with a compound annual growth rate near 28%. IBM’s late-2024 acquisition of HashiCorp closed at 6.4 billion dollars, the OpenTofu fork has shipped real divergent features since splitting from Terraform 1.5, and Pulumi is now appearing in 196 plus IT services job postings as a primary requirement rather than a nice-to-have. The result is the most fragmented IaC hiring market the industry has ever seen, and the resume-side decision of which tools to list, in what order, with what depth, has become surprisingly consequential.

This guide breaks down the 2026 hiring data, the technical and licensing context recruiters now expect senior candidates to understand, and a clear framework for positioning Terraform, Pulumi, CloudFormation, and OpenTofu on your resume without overstating expertise or under-selling real production work.

Written by Taliane Tchissambou, founder of LevStack, drawing on analysis of thousands of DevOps, Cloud, SRE, and Platform Engineer job postings across North America and Europe.

The 2026 IaC Market in One Page

Before deciding what to list on your resume, it is worth understanding what hiring managers see when they look at the IaC landscape in 2026. The numbers behind the four tools are no longer close, but they are also no longer the simple Terraform-versus-the-rest story they were three years ago.

Three takeaways for a 2026 resume. First, Terraform is still the floor: not listing it is a red flag for any role above junior, even if you wrote everything in Pulumi. Second, the market has clearly bifurcated between IaC for ops (Terraform, OpenTofu, CloudFormation) and IaC for developers (Pulumi, AWS CDK), and your resume positioning should match the team you are applying to. Third, license literacy now matters: senior candidates are expected to understand why OpenTofu exists, what the BSL change in 2023 actually changed, and how the IBM acquisition shifts vendor-risk conversations inside enterprises.

If you want to see how IaC tools fit into the broader keyword landscape recruiters and ATS systems screen against, our breakdown of 60+ ATS keywords for DevOps and Cloud resumes in 2026 covers the full keyword inventory by category.

Why Tool Equivalence Matters More Than Tool Stuffing

The most common resume mistake LevStack sees on senior infrastructure profiles is listing every IaC tool the candidate has ever touched, in a flat skills line, with no signal of depth. A 2026-era recruiter pipeline reads that pattern as a junior signal, regardless of years of experience.

The reason is structural. Modern resume parsers and AI-assisted screening systems no longer just match keywords; they cluster equivalent technologies and look for depth in at least one cluster. Listing Terraform, Pulumi, CloudFormation, AWS CDK, OpenTofu, Crossplane, Ansible, and Chef on a single line tells the model you have surface exposure to many tools and proven mastery of none. Listing Terraform with three quantified bullets, plus CloudFormation as a secondary tool tied to one specific AWS migration, tells the same model you own one cluster deeply.

This is exactly why LevStack treats IaC tools as an equivalence class internally. Terraform, Pulumi, OpenTofu, and CloudFormation all solve the same problem — declarative cloud resource provisioning — and the conceptual transferability between them is much higher than recruiters typically credit. A candidate who has shipped real Pulumi work in TypeScript can pick up Terraform HCL inside two weeks. A senior CloudFormation operator can move to Terraform inside a sprint. The strongest 2026 resumes lean into this equivalence rather than hiding it: they name the primary tool, name one or two equivalents, and then quantify the actual outcome.

A skills line written this way reads with much more authority:

Weak: Terraform, Pulumi, CloudFormation, AWS CDK, OpenTofu, Crossplane, Ansible

Strong: Infrastructure as Code: Terraform (primary, 6 yrs across AWS, GCP, Azure), CloudFormation (AWS-native migrations), Pulumi (TypeScript pilot, 14-service rollout)

The strong version costs eight more words and signals depth, scope, and intent. It also gives the hiring manager three concrete things to dig into during the technical screen instead of fourteen vague tool names with no anchor. For a longer treatment of how to think about transferable tooling on a senior resume, see our guide on DevOps resume tips for senior engineers.

When to Lead With Terraform

Terraform should be the first IaC tool on your resume in almost every case. Even if you spend 80% of your day writing Pulumi or CloudFormation, Terraform is the keyword the ATS, the recruiter, and the hiring manager are scanning for first. It is the lingua franca of multi-cloud DevOps hiring in 2026.

The data is unambiguous. Across U.S. and EU job boards, Terraform is mentioned in roughly three times more DevOps and Platform Engineer postings than CloudFormation. It is listed as a hard requirement (not a nice-to-have) in the majority of senior infrastructure roles at companies running on more than one cloud. It has 4,800 plus providers, an enormous public module ecosystem, and a hiring signal that translates across vendors.

Lead with Terraform if any of the following apply. You operate or have operated infrastructure across more than one cloud provider. You have written reusable Terraform modules consumed by other teams. You have run Terraform Cloud, Terraform Enterprise, or a self-hosted state and policy backend such as Atlantis or Spacelift. You have implemented policy-as-code with Sentinel, OPA, or Checkov in a real CI pipeline. You have managed state migrations, refactors, or split monoliths into multi-state architectures.

A strong Terraform bullet for a senior or staff resume looks like this:

Designed and shipped a 40-module Terraform monorepo consumed by 12 product teams across AWS and GCP; introduced OPA policy gates in CI that blocked 130+ non-compliant changes pre-merge in the first quarter and reduced infra review cycle time by 38%.

That bullet names the artifact (40-module monorepo), the scope (12 teams, two clouds), the technical depth (OPA in CI), and a quantified business outcome. It will read as senior on every screen it touches.

When CloudFormation Earns Its Place

CloudFormation occupies a narrower but still meaningful position in 2026. It is not a multi-cloud tool, it is not the multi-cloud market leader’s competitor, and listing it as a primary skill on a resume targeting GCP-heavy or Azure-heavy roles will read as a mismatch. But for AWS-only shops, regulated industries pinned to AWS GovCloud, and teams running Service Catalog or AWS Control Tower, CloudFormation is still embedded deeply enough that real expertise is rare and recruiter-visible.

List CloudFormation prominently on your resume in three scenarios. First, when you are applying to AWS-only teams, especially in financial services, healthcare, or government — CloudFormation is the AWS-native expectation and is often required for compliance reasons rather than technical ones. Second, when you have real experience with CloudFormation StackSets across multi-account AWS Organizations setups, which is a high-signal capability that few senior candidates can claim credibly. Third, when you have done large-scale AWS CDK work that compiles down to CloudFormation, which is a strong signal for engineering-led teams at AWS-native companies.

For everyone else, CloudFormation belongs in a secondary tools line, paired with the specific AWS context that makes it relevant. A bullet like “Migrated 200+ legacy CloudFormation templates to Terraform modules across three AWS accounts, preserving zero downtime through staged drift detection and import” is far stronger than listing CloudFormation as a generic IaC tool: it shows depth in both directions and signals real production exposure.

If your resume is mostly framed around AWS, also reference our Cloud Architect resume guide for how to position AWS-specific tooling at the architect level.

When Pulumi Is Actually a Differentiator

Pulumi is the most strategically interesting tool on a 2026 resume. It is gaining real ground in developer-centric organizations and is now appearing on roughly 196 plus IT services job postings as a primary requirement, but it is still rare enough that listing it credibly will set you apart from the 80% of DevOps candidates who only know Terraform.

The catch is that Pulumi is also the easiest tool to overstate. Recruiters and senior engineers screening at scale know that listing Pulumi without depth is a common pattern, and they will probe in the first technical screen with questions about the Automation API, dynamic providers, ComponentResources, or stack references. If you list Pulumi, you should be ready to discuss at least three of those topics in detail.

List Pulumi as a primary IaC tool only if you have shipped real production Pulumi code in TypeScript, Python, Go, or .NET. Real production work means stacks running services with active users, state stored in a managed Pulumi backend or self-hosted equivalent, and CI/CD integration that promotes through environments. If your Pulumi exposure is a side project or a proof-of-concept that never made it to production, list it as “Pulumi (POC)” or place it in a separate exploratory-tools line so it is still discoverable by ATS scans without overstating depth.

A strong Pulumi bullet for a senior resume looks like this:

Built and rolled out a Pulumi-based platform abstraction in TypeScript covering 14 microservices across two AWS regions, replacing 9,000 lines of Terraform HCL; reduced new-service infra onboarding from 3 days to under 2 hours through reusable ComponentResources and Automation API self-service flows.

That bullet quantifies scope, scale, and outcome, and it names two Pulumi-specific concepts (ComponentResources, Automation API) that are difficult to fake on a screen. It is exactly the kind of bullet that gets pulled into the recruiter call as a discussion point.

OpenTofu: The 2026 Senior Signal

OpenTofu deserves its own line in this guide because it has crossed from emerging to credible inside roughly 18 months. The Linux Foundation fork of Terraform, born after HashiCorp’s August 2023 license change to the Business Source License, is now backed by the CNCF ecosystem, has 9.8 million plus downloads, and reports notable enterprise migrations including Fidelity Investments moving 50,000 plus state files across 2,000 plus applications.

For resume purposes, OpenTofu is now a senior-level signal. It tells a hiring manager that you have engaged with the licensing reality of 2024-2026 IaC, that you understand vendor-neutrality concerns, and that you can run a state migration without breaking production. Junior and mid-level candidates do not gain much by listing it; senior, staff, and platform-lead candidates absolutely do.

Add OpenTofu to your resume if you have actually run a Terraform-to-OpenTofu migration, evaluated it formally as part of a vendor-risk review, or contributed to OpenTofu modules or the upstream project. The strongest framing pairs Terraform and OpenTofu together as a single line item: “Terraform / OpenTofu (drop-in compatible, migrated state across 18 production stacks).” That phrasing signals depth in both, technical fluency with the fork, and the operational maturity to run a migration cleanly.

Avoid listing OpenTofu as a standalone primary skill if you have not actually used it. The questions that follow on screens are sharp: state encryption, provider-defined functions, divergence from Terraform 1.6 plus, and the specific licensing reasoning behind your migration.

A 2026 Resume Skills Line Framework

The following patterns are what LevStack recommends across senior DevOps, Cloud, SRE, and Platform Engineer profiles. Pick the one that matches your actual experience honestly; the closer the match, the better the signal.

Multi-cloud DevOps engineer:

Infrastructure as Code: Terraform (primary, 6 yrs), OpenTofu (state migration, 18 stacks), CloudFormation (legacy AWS workloads), Pulumi (POC)

AWS-native Cloud Engineer:

Infrastructure as Code: CloudFormation / AWS CDK (primary, multi-account StackSets), Terraform (cross-account modules, 4 yrs), AWS Service Catalog

Platform Engineer with developer-centric IaC:

Infrastructure as Code: Pulumi (TypeScript, 3 yrs production), Terraform (4 yrs, module ecosystem), Crossplane (Kubernetes-native control plane)

SRE with reliability-first IaC framing:

Infrastructure as Code: Terraform (primary, GitOps via Atlantis), Helm and Kustomize (Kubernetes), policy-as-code with OPA and Checkov

Each version names a primary tool, signals depth with one concrete artifact (years, scope, or pattern), and adds equivalence class context without inflating the list. For more on how to structure the broader skills section around IaC, our DevOps resume guide walks through the full skills layout for senior engineers.

How to Quantify IaC Work in Bullet Points

The IaC skills line gets you past the keyword scan. The bullet points are what convince a hiring manager. Strong IaC bullets in 2026 quantify three things: scope, depth, and business outcome.

Compare these two bullets, both describing similar work:

Weak: Used Terraform to manage AWS infrastructure for the engineering team.

Strong: Owned a 12-service Terraform module monorepo across 3 AWS accounts; introduced OPA policy-as-code in CI, reducing manual infra review time by 42% and blocking 80+ non-compliant changes pre-merge over two quarters.

The strong version names the artifact (module monorepo), the scope (12 services, 3 accounts), the depth (OPA in CI, policy-as-code), and the quantified business outcome (42% review time, 80+ blocks). It also signals seniority: the implicit subject of the bullet is a platform owner, not a ticket consumer.

Use the same structure for Pulumi, CloudFormation, and OpenTofu bullets. Always lead with what you owned, then quantify scope and depth, then close with an outcome the business already measures (deployment time, incident reduction, cost savings, onboarding time, drift remediation, compliance posture). For a much deeper dive on bullet structure across DevOps roles, our companion guide on how recruiters read DevOps resumes walks through the ten-second human scan in detail.

Common IaC Resume Mistakes to Avoid

Across thousands of DevOps and Cloud profiles, the same five IaC mistakes show up repeatedly on otherwise strong resumes. Each one materially weakens the read.

The first mistake is listing every IaC tool in existence on a single line with no depth signals. As covered above, this reads as junior regardless of years of experience.

The second mistake is listing Pulumi or OpenTofu without real production exposure. Senior screens will probe specifics, and a missed answer there often costs the round.

The third mistake is forgetting Terraform when the entire stack is Pulumi or CloudFormation. Even if you have not touched Terraform in two years, listing it as a secondary tool keeps you discoverable in the keyword filter that most recruiter pipelines still run first.

The fourth mistake is treating IaC as a sub-bullet under cloud rather than its own first-class skill grouping. In 2026, IaC has its own row in most ATS skill taxonomies, and burying it costs visibility.

The fifth mistake is not naming the operating model around IaC. Senior bullets that mention GitOps, Atlantis, Spacelift, Terraform Cloud, policy-as-code, drift detection, or state encryption read with much more authority than bullets that only name the tool. The operating model is the seniority signal. We cover the broader pattern of avoidable resume failures in 10 DevOps resume mistakes that get you rejected.

How LevStack Handles IaC Tool Equivalence

LevStack’s positioning engine treats IaC tools as an explicit equivalence class. When you upload a resume, the engine clusters Terraform, Pulumi, OpenTofu, CloudFormation, AWS CDK, and Crossplane together and looks for depth in at least one tool plus credible breadth across the cluster. It then matches that profile against the IaC requirements of any target job posting and surfaces the gaps you should address.

This matters in practice because most candidates underestimate how much their existing IaC experience transfers. A senior CloudFormation engineer applying to a Terraform-first GCP role often does not realize that 70% of their resume already speaks the right operating language; the gap is keyword positioning, not skill. LevStack flags that gap, suggests the equivalence-aware bullet rewrites, and produces an IaC skills line that matches the target role without inflating expertise.

If you are about to apply to a role that mentions any IaC tool you have not used directly but have a clear equivalent for, the equivalence-aware rewrite is usually the difference between a missed match and a first-round screen.

Frequently Asked Questions

Should I list Terraform on my resume if I only use Pulumi?

Yes. Terraform is the keyword that recruiter and ATS pipelines scan against first, and not listing it on a 2026 DevOps or Cloud resume is a red flag that costs more than it saves. List Pulumi as your primary tool with depth signals, and add Terraform as a secondary tool with honest scoping such as “Terraform (HCL fluent, multi-cloud module reviews)” if you have read and reviewed Terraform code without owning it. The transferability is high enough that recruiters expect senior candidates to be conversant in both.

Is CloudFormation still worth learning in 2026?

Only in two narrow cases. If you are targeting AWS-only roles in regulated industries (financial services, healthcare, government) or AWS-native shops running Service Catalog or Control Tower at scale, CloudFormation is genuinely valuable and recruiter-visible. For everyone else, time spent learning CloudFormation in 2026 is better invested in Terraform fluency, Pulumi for developer-centric teams, or OpenTofu for vendor-neutral enterprise contexts. The 3-to-1 job posting ratio in Terraform’s favor is unlikely to invert.

Does listing OpenTofu help or hurt my resume?

It helps at senior and staff levels, neutral at mid-level, and is mostly noise at junior level. OpenTofu signals license literacy, vendor-neutrality awareness, and migration competence — all senior-level concerns. List it paired with Terraform if you have actually used both, and be ready to discuss the BSL-versus-MPL licensing context, IBM’s HashiCorp acquisition implications, and the technical divergence in features such as state encryption.

How many IaC tools should I list on my resume?

Two to four maximum, with one clearly identified as primary. The pattern that works best for senior engineers is one primary tool with depth signals, one or two secondary tools tied to specific contexts, and at most one tool listed as proof-of-concept or exploratory. Listing six or more IaC tools reads as keyword stuffing and is the single most common reason senior infrastructure resumes get filtered out at the human scan.

Should I list Ansible or Chef alongside Terraform on a 2026 resume?

Configuration management tools (Ansible, Chef, Puppet, SaltStack) are no longer interchangeable with declarative provisioning tools (Terraform, Pulumi, CloudFormation) in 2026 hiring frameworks. List them in a separate skills line or under a configuration-management heading. The exception is Ansible used for orchestration in modern hybrid setups, which still appears in roughly a third of senior DevOps job postings and remains a credible add to the IaC adjacent toolset.

How do I show Terraform expertise without sounding generic?

Lead with the operating pattern, not the tool. Mention modules consumed across teams, policy-as-code in CI, state architecture (single state, multi-state, workspace strategy), and Terraform Cloud or Atlantis or Spacelift if you ran one. Quantify scope (modules, providers, environments, services managed) and depth (refactors, state migrations, custom providers, internal module registries). The combination of operating pattern plus scope plus depth is what distinguishes a senior Terraform resume from a generic one.

Position Your IaC Skills With LevStack

Most candidates underestimate how much their existing IaC experience transfers across tools, and they overestimate how forgiving recruiter pipelines are with tool stuffing. LevStack reads your resume against the equivalence-aware ATS taxonomies modern hiring pipelines actually use, flags missed Terraform / Pulumi / CloudFormation / OpenTofu signals, and rewrites your skills section and bullets so the same real experience reads as senior, scoped, and outcome-driven.

Join the LevStack waitlist to get early access to the resume positioning engine purpose-built for senior DevOps, Cloud, SRE, and Platform Engineers in 2026.