Álvaro
Data Scientist
“In a climate this uncertain, Shakers gives you a layer of reassurance and confidence. What I like most, without a doubt, is the flexibility and getting to work on top-tier projects.”
Join ShakersShakers for expert talent
Work as a Terraform Engineer, project by project
Projects where the infrastructure gets declared in your code: which modules get reused, who reviews the plan before the apply and what happens with drift. Shakers connects you with teams that want to stop touching their clouds by hand.
What gets read about Terraform is HashiCorp's documentation or the thread of the day about switching to OpenTofu. Neither tells you how to start coding a real team's infrastructure by project, plan after plan and module after module. Here is that.
- Higher-paying projects
- More continuity between projects
- Greater recognition for your experience
+3,000
Tech projects published on Shakers
+90
Tech, Product and Data specialisms are part of Shakers
6 months
Average length of a project with Shakers
4.7/5
Our AI Builders' satisfaction on Trustpilot
AI Builder careers powered by Shakers
See how other AI Builders access better projects, build their reputation and grow their careers.
Amelia
AI Agent Developer
“I have been building AI agents for years. Thanks to Shakers I stopped chasing clients and started genuinely choosing which projects I wanted to work on. I work with some of the best companies in Europe, at my own rate, and I focus on what I am good at and what I love: building.”
Join Shakers
Luz
Backend Developer & Data Engineer
“Shakers adds a lot of value because it connects you with sharper projects, already filtered and better defined. It saves you a big part of the upfront work of understanding the client, quoting and weighing up whether it is worth it, and that means that as a contractor you can go far more directly to the opportunities that genuinely fit you.”
Join Shakers
Rubén
Software Developer
“Life as a contractor has a lot going on and it is not always easy. We like to focus on what we are good at, but you also have to manage clients, invoicing and go looking for work. For me, Shakers has been key because it does that prospecting for me, it gives the client confidence from the very first moment, and it lets us be part of a community with real enthusiasm.”
Join Shakers
Alejandro
AI Developer
“Shakers was key to getting my company off the ground: it gave me the flexibility to keep contracting while I built my next chapter. Without Shakers, I would have had to raise funding or push the project back.”
Join Shakers
Toño
Product Designer
“With Shakers I have landed recurring projects that give me peace of mind and room to grow professionally. It is not just about reaching quality clients: it is feeling that you have a network behind you, one that connects you with real opportunities and helps you move forward as a freelancer.”
Join ShakersThe decisions a Terraform Engineer owns every week
A Terraform Engineer turns infrastructure into code: they write declarative configuration in HCL, manage the providers that talk to each cloud, keep the remote state that remembers what exists and control the drift between code and reality. AWS, Azure and GCP are their environment. Terragrunt and OpenTofu complete the craft's ecosystem. Their boundary: they do not choose the cloud nor administer machines; they decide how infrastructure gets declared, versioned and reproduced.
You decide what infrastructure gets declared in code and what gets imported as is, how it splits into modules, where the state lives and who reviews the plan before each apply. You also decide what the repository refuses: a change without a reviewed plan does not go in. The cloud belongs to the team; the code that declares it, to you.
TerraformHCLmodulesremote stateprovidersplan and applydriftAWSAzureGCPKubernetesCI/CDTerragruntOpenTofuAnsibleDockerPython
HCL and modulesRemote statePlan and applyDrift controlTerragruntOpenTofu
Free to join, no hidden fees
How Shakers works for talent
Create your profile
Tell us who you are, what you can do, the projects you want to work on and what your availability and rate are.
Get your certification
We certify your experience and your use of AI so companies understand and trust what you bring.
Match with projects
We connect you with well-paid projects that fit your expertise and your preferences.
DevOps and Cloud projects that live up to your expectations
Work on real projects, with teams that need your expertise, without wasting time looking for opportunities.
Projects that fit you
Work with companies that need your stack and experience to take their projects to production.
Opportunities that come to you
Our AI matching connects your profile with the projects that fit your preferences.
You build. Shakers handles the rest
Set your own terms based on your seniority. We manage contracts, payments and paperwork.
What a Terraform Engineer delivers on a Shakers project
The brief arrives with the console open
Shakers is hiring infrastructure: the project arrives with the infrastructure that hurts and its account, not with a list of technologies.
Infrastructure that reproduces
You deliver the repository with its HCL, its modules and the remote state: any environment stands up again and every change gets reviewed in the plan.
What happens before each apply
The plan gets reviewed with the team, drift gets caught in time and the rollback is designed before it is needed.
Real infrastructure, not tutorials
Having maintained production written in Terraform and being able to tell the day drift taught you something: what drifted, what you did and what changed.
Module or script
Choosing what becomes a module and what is overkill, by impact and not fashion. Sometimes the honest answer is a simple script, and knowing how to defend it.
Where your brief ends
You write the infrastructure; you don't choose the cloud nor deploy the application. If the project asks for architecture or pipeline, you say so at kickoff.
Frequently asked questions
Any other questions? Write to us and we will reply.
Is Terraform still relevant in 2026?
It still is. The BUSL licence forked the ecosystem and the craft covers both banks: Terraform dominates job ads and OpenTofu is already being asked for. HCL, state and modules are common to both.
What should you learn first as a Terraform Engineer?
The vocabulary of the craft: HCL, providers, state and modules. After that, one cloud in depth and the pipeline where the plan gets applied. Certification looks at real repositories.
Which tools do you use daily?
The Terraform CLI with its plan and its apply, one cloud underneath and the module repository as your workshop. Terragrunt and OpenTofu are the marks of a senior profile.
How much do you earn as a Terraform Engineer by project?
You invoice per project and scope sets the band: how much infrastructure gets coded and across how many environments. At Shakers you agree the budget before accepting the brief.
Is Terraform work something you can do remotely?
Almost everything: the infrastructure lives in the cloud, the code in the repository and teams work distributed. Only the odd physical kickoff asks for presence.
How do you join Shakers as a certified Terraform Engineer?
You create your profile, pass the certification process and enter the collective: only 4 percent make it. Then you choose which IaC projects you take on.
The daily shape of the craft
The plan you have to read before the apply, the module that finally serves a third environment and drift found on a Tuesday: less console, more infrastructure that holds up.
The skill the market asks for without the name
2,598 active tech job ads in Spain mention terraform and 627 talk about infrastructure as code, according to Shakers' market analysis (n=31,020, September 2026). It almost never makes the title: DevOps, Data and Platform carry it as a skill. Selling yourself as an IaC specialist is the gap.
How people get here
Two doors: the DevOps who wanted to own the origin of everything and the sysadmin tired of the console. Both arrive with half the craft done.
What this role is not
Not administering machines nor choosing the cloud. If the problem is the pipeline, DevOps; the architecture, Cloud Architect; what already runs in production, SRE.
The roles an IaC project crosses
Five roles cross your path when you turn clouds into code, from the one who deploys to the one who keeps production alive.
DevOps Engineer
Their pipeline deploys what your code declares: the classic boundary of the craft and the way in for many IaC profiles.
Cloud Architect
Decides the cloud and its shape: their architecture decisions are the ceiling of your modules and your environments.
AWS Engineer
The builder of the Amazon ecosystem: there Terraform is their tool and the environment is the identity of the page.
Azure Developer
The same cut on Microsoft's cloud: when the project lives in Azure, the tool accompanies both pages.
Site Reliability Engineer
Keeps in production what your code stands up: when what you delivered already runs and pages, the on-call is theirs and the fix is shared.
Boundaries between these roles are agreed per project: the job title doesn't set them.
Take the next step with Shakers
Make other people's infrastructure your craft
Pass Shakers certification and choose which IaC projects you take on.
