Á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 Google Cloud Engineer on real projects
Projects where the Google ecosystem is yours: which dataset gets structured, which service deploys and which model gets served. Shakers connects you with companies that already pay for the cloud and don't use it.
What gets read about the Google ecosystem is certification guides or cloud comparisons. Neither tells you how to start building on a real company's project piece by piece. 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 Google Cloud Engineer owns weekly
A Google Cloud Engineer builds and operates systems on Google Cloud: they structure data in BigQuery, deploy services on Cloud Run or GKE, connect Vertex AI models with company processes and leave infrastructure defined in Terraform. It is the least noisy cloud niche: fewer job ads than AWS, and less competition for each consultancy project.
You decide which dataset gets structured and who queries it, which service runs on Cloud Run and which on a cluster, and which model is already served in Vertex. You also decide what the project does not need: a piece stood up for testing gets switched off with the same cleanliness it was switched on. The project belongs to the company; what works inside it, to you.
Google CloudBigQueryCloud RunGKEVertex AITerraformPub/SubDockerPythonSQLLookerCI/CD
BigQueryCloud RunGKEVertex AITerraformLooker
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 Google Cloud Engineer delivers at Shakers
The brief arrives with the project
Shakers is hiring infrastructure: the project arrives with the Google cloud already paid for and the specific question, not with a list of technologies.
Pieces you can audit
You deliver every piece with its cost and permissions written down, including the one you discarded and why: the project is understood without you in the room.
What happens when something fails
You set what gets monitored, at what threshold and who responds. Every service with its telemetry before closing the milestone.
Real projects built
Having built on a company project and being able to tell which piece you chose wrong the first time and how you corrected it.
The right piece
Choosing by continuity with the ecosystem, not catalogue. Sometimes the honest answer is a simple function, and defending it.
Where your brief ends
You build inside Google Cloud; full data governance is Data Engineer 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 Google Cloud?
The daily core: BigQuery and SQL first, Cloud Run to deploy and Terraform to define it. Vertex AI when the project touches models. Certification looks at real projects.
Which tools do you use daily?
BigQuery and SQL almost always, Cloud Run or GKE depending on load, Pub/Sub to join pieces and Looker when results need showing.
Is there less Google Cloud work than AWS?
Less volume: 1,213 job ads mention Google Cloud versus 6,170 for AWS in the Spanish corpus. Also less competition per brief. A consultancy niche, not a certification race.
How much do you earn as a freelance Google Cloud Engineer?
You invoice per project and scope sets the band: which pieces get built and what operation remains. You agree the budget before accepting.
Is Google Cloud work something you can do remotely?
Almost everything: the project and services live in the cloud. Only the odd local-hardware deployment asks for presence.
How do you join Shakers as a Google Cloud Engineer?
You create your profile, pass the certification process and enter the collective: only 4 percent make it. Then you choose your Google projects.
The daily shape of the craft
The spreadsheet acting as database, the model left in demo and the project with far too many permissions. Fewer certificates accumulated, more Google pieces that finally talk to each other.
The least noisy cloud niche
1,213 active tech job ads in Spain mention Google Cloud, according to Shakers' market analysis (n=30,508, September 2026). One fifth of AWS: less total demand, and fewer profiles competing for each consultancy brief.
How people get here
The frequent door is the analyst tired of spreadsheets who discovered BigQuery. Another is the developer whose deployment quietly became Cloud Run.
What this role is not
Not designing the multi-cloud strategy nor building the full data pipeline: making Google's pieces work together. If the problem is deployment, the role is DevOps.
The roles a Google Cloud project crosses
Four roles from the collective cross your path inside the Google ecosystem, from the one designing the platform to the one governing the data.
Cloud Architect
Decides whether Google is the cloud and in what shape: their decisions frame where your project makes sense.
Data Engineer
The full governance of data: pipelines and quality. When BigQuery stops being platform and becomes their territory.
AWS Engineer
The builder of the Amazon ecosystem: when the client lives in AWS, that page comes in and yours is not needed.
DevOps Engineer
The automation of the software's path: their pipeline deploys what your ecosystem holds in production.
Boundaries between these roles are agreed per project: the job title doesn't set them.
Take the next step with Shakers
Want projects that actually use the cloud?
Pass Shakers certification and choose which Google ecosystem projects you take on.
