Shakers for expert talent

Work as an AWS Engineer on real accounts

Projects where the account is yours: which service holds each piece, what gets defined in code and which permissions close. Shakers connects you with teams already living in AWS and building it blind.

What gets read about the Amazon ecosystem is certification syllabi or exam forums. Neither tells you how to start building on a real company's account project by project, service by service. Here is that.

  • Higher-paying projects
  • More continuity between projects
  • Greater recognition for your experience
Shakers panel showing four available profiles and their match percentage
Looking for projects on AWS
Allianz
BBVA
Bankinter
Microsoft
Qida
Accenture
Deloitte
Dcycle
HP
Línea Directa
Podo
Clicars
Sonosuite
Eroski
Civitatis
Alten
Vivla
Wayra
Cabify
Affinity
+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.

Portrait of Álvaro, Data Scientist in the Shakers collective Ready to build

Á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 Shakers
Portrait of Amelia, AI Agent Developer in the Shakers collective Ready to build

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
Portrait of Luz, Backend Developer and Data Engineer in the Shakers collective Ready to build

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
Portrait of Rubén, Software Developer in the Shakers collective Ready to build

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
Portrait of Alejandro, AI Developer in the Shakers collective Ready to build

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
Portrait of Toño, Product Designer in the Shakers collective Ready to build

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 Shakers

The decisions an AWS Engineer owns every week

An AWS Engineer builds and operates systems on Amazon Web Services: they choose the right service for each workload (EC2, Lambda, S3), define infrastructure with CloudFormation or Terraform and close permissions with IAM. When the project touches AI, they extend the account with Bedrock: models over the data that already lives there.

You decide which service holds each piece and at what cost, what gets defined in code and what closes with minimal permissions. You also decide what the account does not need: a service stood up for fashion gets switched off with the same cleanliness it was switched on. The account belongs to the company; what gets built inside, to you.

AWSEC2LambdaS3CloudFormationTerraformDockerKubernetesPythonIAMBedrockCI/CD ServerlessAWS architectureTerraformCloudFormationIAMBedrock

Free to join, no hidden fees

How Shakers works for talent

Join Shakers

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.

Specialist sitting on a sofa with a tablet and a Ready_to_build label

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 an AWS Engineer delivers on a Shakers project

At Shakers

The brief arrives with the account

Shakers is hiring infrastructure: the project arrives with the AWS account already running and the specific symptom, not with a list of technologies.

Delivery

Architecture you can audit

You deliver the service map with its cost and risk, and every new decision written as a template, including the one you discarded and why.

Operations

What happens when something fails

You set what gets monitored, at what threshold and who responds. Every service with its telemetry before being called done.

What we ask

Real accounts built

Having built on a company account and being able to tell which service you chose wrong the first time and how you corrected it.

Judgement

The right service

Choosing by workload and cost, not catalogue. Sometimes the honest answer is a simple instance, and knowing how to defend it.

Boundary

Where your brief ends

You build and operate inside AWS; the deployment pipeline is DevOps ground. If the project needs it, you say so at kickoff.

Frequently asked questions

Any other questions? Write to us and we will reply.

What should you learn to work with AWS?
The catalogue with judgement: EC2, Lambda, S3 and IAM first, then CloudFormation or Terraform to define it in code. Certification looks at real accounts built.
Which tools do you use daily?
The console and the CLI every day, CloudFormation or Terraform to define infrastructure, and Python as the glue. IAM always: the craft nobody sees.
How is it different from the AWS DevOps Engineer?
You build and operate the service architecture; AWS DevOps automates the pipeline deploying on the same cloud. You cross paths on every project.
How much do you earn as a freelance AWS Engineer?
You invoice per project and scope sets the band: which services get built and what operation remains. You agree the budget before accepting.
Is AWS work something you can do remotely?
Almost everything: the account and services live in the cloud. Only the odd hardware deployment asks for presence.
How do you join Shakers as an AWS Engineer?
You create your profile, pass the certification process and enter the collective: only 4 percent make it. Then you choose your Amazon projects.
The daily shape of the craft

The account with more roles than services, the function scaling without control and the bill nobody understands. Fewer certificates accumulated, more architecture that holds itself up.

The cloud with the most demand

6,170 active tech job ads in Spain mention AWS, one in five of the corpus, according to Shakers' market analysis (n=30,508, September 2026). The cloud with the most projects and the most noise: choosing services well is the difference.

How people get here

Two frequent doors: the developer who ended up managing the client's account and the sysadmin who moved the load into the cloud. Both arrive knowing half: choosing well is what's missing.

What this role is not

Not accumulating certifications nor keeping the inherited lights on. If the problem is the pipeline, the role is DevOps; multi-cloud strategy, Cloud Architect.

The roles an AWS project crosses

Four roles from the collective cross your path inside the Amazon account, from the one automating deployment to the one living in the data.

DevOps cut

AWS DevOps Engineer

The DevOps cut of the ecosystem: their pipeline deploys what your architecture holds up. The most frequent boundary of your week.

View profile →

Generalist

DevOps Engineer

The automation of the software cycle with the three clouds as environments: when the problem is the path, not the account.

View profile →

Platform

Cloud Architect

Decides whether AWS is the cloud and how it is structured: their decisions frame where your account makes sense.

View profile →

Data

Data Engineer

Kinesis, Glue and the lake: when the AWS part of the project is the data feeding your services.

View profile →

Boundaries between these roles are agreed per project: the job title doesn't set them.

Take the next step with Shakers

Want accounts built with judgement?

Pass Shakers certification and choose which Amazon projects you take on.