Á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
Build your career as a .NET Developer
Projects where the ecosystem is you: which service leaves legacy .NET Framework, which endpoint gets versioned and who decides what goes to Azure. Shakers connects you with teams that keep ERP, banking and industry running on the Microsoft stack, many remote.
What gets read about the role is either course routes or the annual video with everything you need to know; about .NET by project, a translated Reddit thread nobody answered. Neither tells how the real Microsoft stack gets sustained project by project: what gets migrated from Framework 4.x, how you enter Navision. 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 .NET Developer owns every week
A .NET Developer builds and sustains the systems of the Microsoft ecosystem: services with C#, ASP.NET Core and Web API, data with Entity Framework, LINQ and SQL Server, legacy WPF desktop, the Azure cloud and, in the Spanish company, the Dynamics or Navision ERP that holds the business. Their craft is the whole Microsoft house, from legacy .NET Framework 4.x to the modern versions renewing it, and their proof of level is sustained production: migrate in stages without stopping the system, version without breaking.
You decide which service migrates off .NET Framework and in what order, which endpoint goes into the next Web API version and what goes to Azure. You also decide what the system refuses: a deployment without tests does not ship. The business belongs to the client; the judgement over the ecosystem, to you.
C#.NETASP.NET CoreWeb APIEntity FrameworkLINQSQL ServerAzureAzure DevOpsmicroserviciosAPIs RESTDockerKubernetesCI/CDBlazorWPFAngularKafka
ASP.NET CoreSQL ServerAzureEntity FrameworkREST APIsLiving legacy
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.
Software Engineering 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 you execute as a .NET Developer on a Shakers project
The project arrives with the system
The brief arrives with a Microsoft system behind it: a Navision ERP, a desktop WPF or an ASP.NET service. The conversation starts from the concrete pain.
Migrations that stop nothing
Legacy .NET Framework 4.x gets renewed in stages: one service at a time, with regression tests and rollback. The business never notices the move.
What gets modernised and what stays
You decide which service leaves legacy Framework, which endpoint gets versioned and what goes to Azure: by risk and by value, never by fashion.
Production, told
Having sustained real .NET systems and knowing how to tell it: your last serious incident, how you reverted it and what you instrumented so it never repeated.
The complete dialect
C# with LINQ and Entity Framework, ASP.NET Core in the services, the house SQL Server and Azure at deploy. The whole ecosystem, not just the language.
Where your brief ends
You build and sustain the .NET; the interface and the cluster have their own page. If the project asks for full stack or DevOps, it gets said at kickoff.
Frequently asked questions
Any other questions? Write to us and we will reply.
Is .NET obsolete in 2026?
No: modern .NET ships every year and senior job ads ask for C#, ASP.NET Core, Azure and containers. With 1,413 active job ads in Spain mentioning .NET, the ecosystem renews itself, not switches off.
How do I start taking on .NET projects?
With a channel and a portfolio: you create the profile, pass the certification and enter where the project scope is already closed. The portfolio gets built sustaining real systems, not with courses.
Can you make a living from .NET projects in Spain?
Yes, with production briefs: keep the Navision nobody touches, migrate legacy Framework, version APIs with living contracts. Projects arrive with scope closed before you accept.
How much do you earn as a .NET Developer by project?
The market and the scope set it: which system you keep running, with which stack and how much migration comes in. At Shakers you agree the budget per project before accepting.
Should I name myself .NET or C# Developer?
The market writes them together: real job ads title .NET/C#. To position yourself, name the platform and leave C# as the language of the stack.
How do you join Shakers as a .NET Developer?
You create your profile, pass the certification process and enter the collective: only 4 percent make it. Then you choose which .NET projects you take on.
The daily shape of the craft
The WPF that gets modernised without rewriting it, the endpoint that gets versioned without breaking anyone, the Framework migration that advances one service per sprint. A system real people stand on.
The tools are the craft
1,413 active tech job ads in Spain mention .NET, more than the 1,157 asking for Spring Boot (Shakers market analysis, n=31,162, September 2026). C# and SQL Server in almost all; Azure and containers at senior level.
How people get here
Two doors: the one who grew up in consultancy maintaining legacy Framework, and the backend from another language who crossed to C#. The mixed .NET with Angular job ad is full-stack land.
What this role is not
If the brief is the interface with Angular or React, the full-stack page sets the cut; Spring or the JVM is java land; the pipeline, DevOps. The boundary is declared at kickoff.
The roles a .NET project crosses
Four roles cross your path as you keep the Microsoft stack running: the java twin, the Angular pair, the backend and the full stack.
Java Developer
The enterprise twin from the other world: java keeps Spring, Kafka and the JVM; you keep C#, ASP.NET and the house SQL Server. Whoever names their stack chose.
Angular Developer
The classic pair of enterprise .NET: the mixed job ad gets published as .NET with Angular. When the interface of the brief weighs, it splits with this page.
Backend Developer
.NET is a backend with a surname: when the brief names no platform nor ecosystem, the generic filter is theirs; the .NET and C# lexeme is yours.
Full Stack Developer
The role intent of the .NET full stack lives on this page: the brief mixing Microsoft backend and frontend splits according to how much each part weighs.
Boundaries between these roles are agreed per project: the job title doesn't set them.
Take the next step with Shakers
Want to keep the .NET that already runs?
Pass Shakers certification and choose which .NET projects you take on.
