If you have not touched your infrastructure-as-code toolchain since 2023, the ground has moved. HashiCorp's license change, the OpenTofu fork, and Pulumi's steady climb in developer-heavy shops have all reshaped what clients ask for on contract postings.
This matters for your rate and your pipeline. A consultant who can only speak Terraform HCL is still fine for most gigs. A consultant who can also read a Pulumi stack or explain why a client migrated to OpenTofu closes more interviews.
Here is what is actually showing up in requisitions right now, and what to prioritize depending on where you sit in your career.
The licensing backstory, briefly
In August 2023, HashiCorp moved Terraform from the Mozilla Public License to the Business Source License (BSL 1.1). That license restricts competing commercial products built on top of Terraform, though it does not affect normal internal use by companies running their own infrastructure.
The response was the OpenTofu fork, launched under the Linux Foundation later that year and built from the last MPL-licensed Terraform codebase. It runs on Apache 2.0, a true open-source license with no BSL restrictions.
Then in 2024, IBM announced its acquisition of HashiCorp, which closed in early 2025. Terraform itself stayed BSL-licensed under IBM. Nothing forces enterprises to switch, but the acquisition gave already-nervous legal and procurement teams one more reason to evaluate alternatives.
Where each tool actually shows up in postings
Contract requisitions rarely say "Terraform vs OpenTofu" outright. You read between the lines: the client's industry, their compliance posture, and how their DevOps team is structured.
| Tool | Typical client profile | What drives the choice |
|---|---|---|
| Terraform | Large enterprises, regulated industries, existing multi-year IaC investment | Mature module ecosystem, HCP Terraform (formerly Terraform Cloud), deep provider coverage, sunk cost in existing state and pipelines |
| OpenTofu | Enterprises with strict legal review of vendor licensing, cost-sensitive orgs avoiding HCP Terraform fees, some fintech and public sector | Apache 2.0 license, drop-in compatibility with existing HCL modules, growing but smaller managed-service ecosystem |
| Pulumi | Dev-heavy shops, platform teams building internal developer platforms, startups and scaleups | Real programming languages (TypeScript, Python, Go, C#), easier unit testing, tighter integration with application code repos |
Terraform still dominates raw posting volume. Most job descriptions that say "infrastructure as code" without further detail mean Terraform by default. OpenTofu postings are growing but remain a minority, concentrated in organizations that ran a formal licensing risk assessment. Pulumi shows up disproportionately in job descriptions that also mention Kubernetes operators, internal developer platforms, or "full-stack" engineering teams.
What clients actually ask about in interviews
- State management: remote backends, locking, drift detection, and how you handle state file corruption under pressure
- Module design: how you structure reusable modules versus copy-paste sprawl across environments
- Migration experience: whether you have moved a codebase from Terraform to OpenTofu, or explained the tradeoffs to a client considering it
- Policy as code: familiarity with Sentinel, OPA, or Checkov for guardrails, regardless of which core tool sits underneath
- CI/CD integration: how you wire plan and apply steps into GitHub Actions, GitLab CI, or Jenkins with proper approval gates
Practical picks by role and stage
If you are early in your IaC career, learn Terraform first. It is the lingua franca. Every OpenTofu shop still expects you to read and write HCL fluently, and the syntax is nearly identical between the two.
If you are mid-career and want to differentiate, add OpenTofu migration experience to your story. Even a personal lab project where you fork a Terraform repo, run it through tofu init and tofu plan, and document the differences gives you a concrete talking point clients notice.
If you are targeting platform engineering or SRE roles at product companies, invest in Pulumi. Being able to write infrastructure in the same language as the application team is a genuine differentiator, and it pairs well with Kubernetes and internal developer platform work.
- Confirm the client's current tool before the interview. Recruiters usually know; ask directly.
- If they mention OpenTofu, ask why they moved. The answer tells you about their risk tolerance and procurement culture.
- Keep one working example of state migration in your portfolio. A five-minute walkthrough beats a paragraph on your resume.
- Do not assume certifications carry equal weight. HashiCorp's Terraform Associate certification still carries the most recognition; OpenTofu and Pulumi lean more on demonstrated project work.
A quick reality check on rates
Tool choice alone rarely moves your bill rate. What moves it is depth: multi-cloud module design, policy-as-code enforcement, and the ability to walk into a client's messy existing codebase and stabilize it without a rewrite. Terraform, OpenTofu, and Pulumi are all just vehicles for that skill set. Clients pay for the judgment, not the syntax.
The consultants who stay engaged year over year are the ones who can speak to all three without pretending to be a purist about any of them.
Josh Pros LLC works with contract technologists navigating exactly these tool-stack decisions across cloud, data, and platform roles. If you want a candid read on which IaC skill set fits your next contract, reach out to contact@joshpros.com or visit https://joshpros.com.
#Terraform #OpenTofu #Pulumi #InfrastructureAsCode #IaC #CloudEngineering #PlatformEngineering #SRE #DevOpsJobs #ContractConsulting #TechContracting #CloudCertifications
Talk to a real recruiter, not a bot.
We'll tell you the rate, the client, and the terms before you interview. And if we're not the right fit, we'll say so.