Freelance .NET developer

Freelance .NET developer for teams that need a senior now

For when you need a senior .NET developer and the job ad has been open for months. I join your repository, your tickets and your code review, take the parts that need experience, and leave the knowledge with you. No agency in between.

Vlado Pandžić

Vlado Pandžić · Founder · Senior .NET architect
14 years in .NET, Blazor in production since 2020. Lead backend engineer at Bugatti Rimac from 2020 to 2024. You work with him directly, not with an agency.

OrderQueries.cs
Task<List<OrderRow>> GetOpenOrders(int customerId) =>    db.Orders        .AsNoTracking()        .Where(o => o.CustomerId == customerId)        .Where(o => o.Status == OrderStatus.Open)        .OrderByDescending(o => o.CreatedAt)        .Select(o => new OrderRow(o.Id, o.Total))        .ToListAsync();
14
years in .NET
2020
Blazor in production since
CET
working hours overlap with most of Europe
EU
company, contract and invoicing

What I do in your team

The work that needs experience, in your code and by your rules, not somewhere on the side.

01

Feature development

ASP.NET Core, APIs and business logic in your existing codebase. Tickets from your board, pull requests reviewed by your team.

  • ASP.NET Core
  • REST APIs
  • Business logic
02

Blazor

Blazor applications from the first screen to production, the right render mode and fast large screens. Web Forms migration, one screen at a time.

  • Blazor Server
  • WebAssembly
  • Web Forms migration
03

Upgrades and migrations

.NET Framework to .NET 10, moving off .NET 8 before end of support on 10 November 2026, EF6 to EF Core. Without stopping development.

  • .NET 10
  • EF Core
  • Incremental migration
04

Performance

Slow screens, reports and queries. Measure first, then fix: EF Core queries, SQL Server indexes, caching.

  • EF Core
  • SQL Server
  • Profiling
05

Architecture and code review

The hard decisions, code review and mentoring for a younger team, so the team works better after we part than before.

  • Code review
  • Architecture
  • Mentoring
06

Azure and AI

App Service, Azure SQL, pipelines and Application Insights. AI features with Azure OpenAI inside your own subscription.

  • Azure
  • Azure DevOps
  • Azure OpenAI

Three ways to work together

From a few days a month to full time on a project. You always know who works on your code.

01

Monthly block of days

ForTeams that need a senior a few days a month, not full time.

Includes
  • /Development in your repository
  • /Code review and architecture
  • /Firefighting in production
  • /Mentoring the team
You get

An agreed number of days a month, used for whatever matters most that month.

Duration
Monthly, cancel at any time
Price
Day rate, billed monthly
02

Full time on a project

ForTeams with a project and a deadline that need a senior every day while it runs.

Includes
  • /Daily stand-ups and your process
  • /The critical parts of the project
  • /Code review for the rest of the team
  • /Handover at the end
You get

A senior .NET developer in your team every working day, for as long as the project runs.

Duration
From 3 months, extendable
Price
Day rate, agreed after a free call
03

Fixed-scope task

ForCompanies that need one specific job done: an upgrade, a migration assessment or a performance fix.

Includes
  • /Scope and result agreed up front
  • /Work in your repository
  • /Documentation and handover
You get

The job done, and a team that knows how it was done.

Duration
Depends on scope, usually a few weeks
Price
Fixed, agreed after a free call

Why teams bring in a freelance .NET developer

Rarely because they need another pair of hands. Almost always because of one of these.

01

The job ad has been open for months

There is no senior .NET developer to hire, and when there is, they have a notice period. The project cannot wait that long, so someone has to step in now.

02

A deadline without people

The customer is waiting and the team is already full. A few months of senior help is the difference between on time and late.

03

A migration nobody on the team has done

Upgrading from .NET Framework or from .NET 8 needs someone who has done it before and knows where the traps are.

04

All the knowledge in one head

The only senior has left or is leaving. Someone has to take over the code, write down what they know and pass it on to the rest of the team.

05

The application is slow and nobody knows why

Users complain and the team guesses. Measuring, EF Core queries and indexes usually show the cause within the first few days.

See the ways to work together →

How we start

The goal is a first merged pull request in the first week.

  1. 01

    A 30-minute call

    What you are building, where the team is stuck and what done looks like.

  2. 02

    Access and a first task

    Repository, tickets and environments. The first task is small but real.

  3. 03

    Your rhythm

    Your stand-ups, your ticketing tool, pull requests reviewed by your team.

  4. 04

    Handover

    Everything is documented and in your repository, so the knowledge stays with you when the work ends.

When it fits, and when it doesn’t

A good fit when

  • +You have .NET code and a team, and need senior experience
  • +Remote work suits you, with an occasional visit
  • +You want the code and the knowledge to stay in your company
  • +You need someone who knows .NET, Blazor and Azure together

Not a fit when

  • −You need someone in the office five days a week
  • −You need a team of ten by next month
  • −The lowest hourly rate is the only criterion
  • −Your system is not built on .NET

Stack

From the blog

Software and business

All articles →

Questions

With Vlado directly. ProCoding is a sole-trader studio, and the person you speak to on the first call is the person who writes the code.

Both are possible: a monthly block of days, or full time for the length of a project. On the call we say openly when we can start.

A business-to-business contract and one invoice a month. For business clients in other EU countries, invoices are issued under the reverse-charge rule.

You do, from day one. All work goes into your repository. NDA on request, and a data processing agreement where personal data is involved.

Yes. We can work behind you, in your process and under your name if you prefer, and you stay the client’s contact.

The day rate or the price of a fixed task is agreed after a free 30-minute call, once we know the scope and the duration.

Need a senior .NET developer in your team?

Tell us what you are building and from when you need someone. A free 30-minute call is enough to see whether it fits.

Book a free 30-minute call →
  • EU company, Split, Croatia
  • Central European working hours
  • NDA on request
  • You work with the engineer who writes the code

Useful to include

  • /What the team is building
  • /Stack and .NET version
  • /From when, and how many days a month
  • /Remote or partly on site
[email protected]
[email protected]
© 2026 ProCoding — All rights reserved.Legal notice and privacyTerms of useSplit, Croatia