Á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 Kubernetes Engineer on live clusters
Projects where the cluster is yours: which workload gets orchestrated, what gets declared in Helm and who answers when a pod falls over at 4 a.m. Shakers connects you with teams whose containers are ready and nobody to orchestrate them.
What gets read about the role is either the official documentation or the Reddit thread explaining how to monetise Kubernetes in English. Neither tells you how to start orchestrating a real team's cluster in Spain, brief after brief. 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 ShakersWhat a Kubernetes Engineer decides every single week
A Kubernetes Engineer designs, deploys and sustains clusters of containers: they write the manifests and Helm releases that declare how each service lives, configure the autoscaling and self-healing with which the platform recovers on its own, and run the engine with kubectl across the three clouds (EKS, AKS, GKE). Helm, GitOps and operators are their daily workshop; orchestration is the craft.
You decide which workload gets orchestrated and with what resources, what gets declared in Helm and what stays outside, which rollout enters and how, and who answers when a pod falls at 4 a.m. You also decide what the engine refuses: a release without rollback does not go in. The cluster is the team's; the orchestration that keeps it alive, yours.
KubernetesDockerHelmTerraformCI/CDAWSAzureGCPPrometheusLinuxPythonGoGitOpsArgoCDAnsibleOpenShift
OrchestrationHelmGitOpsAutoscalingSelf-healingEKSAKSGKE
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 Kubernetes Engineer delivers at Shakers
The brief arrives with the migration
Shakers is hiring infrastructure: the project arrives with the containers ready and the jump to production pending, not with a list of technologies.
Clusters you can audit
You deliver the manifests, the Helm releases and the reasoning behind each scaling decision, including what you decided not to orchestrate and why.
What happens when a pod falls
You set the rollout strategy, the rollback and who answers in each window. The small hours get designed before the first failure.
Sustained clusters, not mock-ups
Having operated real production and knowing how to tell the story of a failure: what broke, what you did and what changed so it never repeated.
Orchestrate or not
Choosing the cluster by the real size of the problem, not fashion. Sometimes the honest answer is plain Docker, and defending it.
Where your brief ends
You orchestrate the engine; you don't write the application or design the cloud. If the project needs pipeline or architecture, you say so at kickoff.
Frequently asked questions
Any other questions? Write to us and we will reply.
What should you learn to work as a Kubernetes Engineer?
The object model first: pods, deployments and services with kubectl. Helm after, and GitOps once the team matures. The CKA is the market's seal; in Shakers certification, real clusters.
Which tools do you use daily?
Helm and kustomize almost daily, ArgoCD once deployment is GitOps, and Terraform or Ansible around the cluster. The cloud is the client's environment: EKS, AKS or GKE wherever the stack runs.
Am I a DevOps Engineer or a Kubernetes Engineer?
The market publishes the hybrid DevOps & Kubernetes Engineer: the boundary is agreed per project. If your bigger half is the cluster, this is your page; if it is the pipeline, the DevOps one.
How much do you earn as a Kubernetes Engineer by project?
You invoice per project and scope sets the band: which workloads get orchestrated, which cloud and whether there is on-call. At Shakers you agree the budget before accepting the brief.
Is Kubernetes work something you can do remotely?
Almost everything: the cluster lives in the cloud and gets operated with kubectl from anywhere. Only the odd physical node in a datacentre asks for presence, and less each time.
How do you join Shakers as a Kubernetes Engineer?
You create your profile, pass the certification process and enter the collective: only 4 percent make it. Then you choose which orchestration projects you take on.
The daily shape of the craft
The pod that heals itself at 4 a.m., the Helm release you review before deploying and the node that joins and leaves the cluster unnoticed. Less manual firefighting, more platform that holds itself up.
The tools are the craft
4,426 active tech job ads in Spain mention kubernetes and 606 ask for Helm, according to Shakers market analysis (n=31,020, September 2026). Terraform and Ansible close the stack.
How people get here
Two frequent doors: the DevOps Engineer who inherited the cluster, and the sysadmin who came from virtual machines. The CKA (Certified Kubernetes Administrator) certification seals the level in both.
What this role is not
Not the course that explains what a pod is, nor the architect who designs the cloud: if the problem is the pipeline, the role is DevOps; if it is architecture, Cloud Architect. Your ground is the engine.
The roles a Kubernetes project crosses
Five roles from the collective cross your path while you orchestrate containers: who deploys, who designs the cloud, who audits it.
DevOps Engineer
The duo the market publishes together: their pipeline deploys what your cluster orchestrates. Many Kubernetes Engineers come from DevOps.
SRE
Kubernetes is their core stack: when the cluster runs and what pages you is reliability, on-call and incidents become theirs.
Cloud Architect
Designs the cloud where your cluster lives: their platform and cost decisions are the ceiling of what your orchestration can sustain.
AWS Engineer
The Amazon ecosystem specialist: when the cluster is EKS, infrastructure and orchestration split the brief.
Security Engineer
Audits the cluster for ISO 27001 or ENS: RBAC, network policies and secrets reviewed alongside your work when the project must comply.
Boundaries between these roles are agreed per project: the job title doesn't set them.
Take the next step with Shakers
Want projects where the cluster is yours?
Pass Shakers certification and choose which orchestration projects you take on.
