Shakers for expert talent

Work as an Azure Developer on real estates

Projects where the Microsoft ecosystem is your territory: which application migrates, which function gets built and which integration closes. Shakers connects you with companies already paying for Azure and not using it.

What gets read about the Microsoft ecosystem is either certification syllabi or endless consultancy job ads. Neither tells you how to start building on a real company's subscription project by project. 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 Azure
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 Azure Developer owns every week

An Azure Developer builds applications on Microsoft Azure: they migrate .NET services running on-premise, program serverless functions in Azure Functions, close identities with Entra ID and deploy with Azure DevOps. Their identity is the whole Microsoft ecosystem, from C# and PowerShell to SQL and Cosmos DB.

You decide which application migrates and with what strategy, what becomes serverless and what stays a service, and how every identity entering the subscription is closed. You also decide what stays untouched: a legacy .NET system running payroll is not rewritten on a Friday. The cloud belongs to the company; what gets built inside it, to you.

Azure.NETC#Azure FunctionsAzure DevOpsEntra IDTerraformDockerPowerShellSQLCosmos DBCI/CD Azure Functions.NET and C#Azure DevOpsCloud migrationEntra IDCloud cost

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 Azure Developer delivers on a Shakers project

At Shakers

The brief arrives with the subscription

Shakers is hiring infrastructure: the project arrives with the Microsoft cloud already paid and the legacy system that hurts, not with a list of technologies.

Delivery

An inventory and plan you can audit

You deliver what migrates, what gets modernised and what stays, with the cost of each decision written before a single line moves.

Operations

What happens when the function fails

You set the monitoring, the alert threshold and who responds. Serverless gets operated too: every function with its telemetry.

What we ask

Real systems migrated

Having built or migrated on a real company subscription and being able to tell what broke along the way and how you resolved it.

Judgement

Migrate or rewrite

Choosing by cost and risk, not fashion. Sometimes the honest answer is the application stays where it is, and defending that.

Boundary

Where your brief ends

You build inside Azure; you don't design the multi-cloud platform or automate someone else's pipeline. 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 Azure?
The ecosystem first: C# and .NET, Azure Functions and Entra ID. The AZ-204 certification opens doors, but Shakers certification looks at real systems you have built.
Which tools do you use daily?
Visual Studio and Azure DevOps every day, Azure Functions and Entra ID almost always, Terraform when the client wants infrastructure as code.
Is an Azure Developer a different role from DevOps on Azure?
Yes. You build the application inside the cloud; DevOps automates the path to production. On Microsoft projects you cross paths daily and agree the boundary.
How much do you earn as a freelance Azure Developer?
You invoice per project and scope sets the band: which applications migrate and which integrations close. At Shakers you agree the budget before accepting.
Is Azure work something you can do remotely?
Almost everything: the subscription and the code live in the cloud. Only the odd on-premise deployment asks for presence.
How do you join Shakers as an Azure Developer?
You create your profile, pass the certification process and enter the collective: only 4 percent make it. Then you choose your Microsoft projects.
The daily shape of the craft

The .NET Framework application nobody dares touch, the function consuming the message queue and the identity that must close before Friday. Less inherited maintenance, more services being built.

The most-mentioned ecosystem in the corpus

5,180 active tech job ads in Spain mention Azure, one in six of the corpus, according to Shakers' market analysis (n=30,508, September 2026). The inherited cloud of the Spanish enterprise holds the demand.

How people get here

The frequent door is the .NET developer tired of local servers. Another is the Microsoft consultant who wants their own code instead of billable hours.

What this role is not

Not installing the platform nor designing the cloud: building inside it. If the problem is the pipeline, the role is DevOps; multi-cloud architecture, Cloud Architect.

The roles an Azure project crosses

Four roles from the collective cross your path inside the Microsoft ecosystem, from the one automating to the one designing the platform.

Boundary

DevOps Engineer

Their pipeline deploys what you build: the automation of the path, with no cloud identity.

View profile →

AWS cut

AWS DevOps Engineer

The same craft on the Amazon cloud: when the client lives in AWS, that page joins the brief and you don't.

View profile →

Platform

Cloud Architect

Decides whether Azure is the cloud and how it is structured: their decisions are the frame you build within.

View profile →

Code

Backend Developer

The services you later deploy: when the logic lives in code rather than cloud, diagnosis is shared.

View profile →

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

Take the next step with Shakers

Want subscriptions with code inside them?

Pass Shakers certification and choose which Microsoft ecosystem projects you take on.