.NET Developer Job Description: Template, Skills and 2026 Rates

★ The role

What does a .NET developer do?

A .NET developer builds the server side your product runs on, in C#: the APIs, business logic, data access and background jobs that everything else depends on. The job also covers the parts nobody demos, meaning transactions, async concurrency, error handling and behavior under load, plus the scheduled jobs, reconciliation and audit logging that regulated US businesses depend on, where you also have to prove the controls are actually in place.

That description is accurate and almost useless for writing a posting, because it fits a contractor who wires up CRUD endpoints and a senior engineer who owns an insurance platform that cannot lose a transaction. The gap between them is not C# syntax. It is judgment about how data is modeled, where transaction boundaries sit, and what happens when two requests hit the same record at once. Your job description is the first place that judgment can be filtered for, so it should describe the system, not the language.

★ First decision

The first line of a .NET posting has to say which .NET

This is the change that improves a .NET posting the most, and it has no equivalent in most other stacks. "The .NET developer" hides a fork in the platform that decides who you should hire. Old .NET Framework 4.8 is Windows-only and in maintenance. Modern .NET (8 and 9) is cross-platform and where all new work happens. A candidate who is great at one is not automatically the right hire for the other, and moving between them is a migration project, not a version bump. Work out which row below you are in, then write only that row's requirements.

A strong ASP.NET Core backend developer is not automatically a Blazor or desktop specialist, and a modernization engineer who is brilliant at untangling old Web Forms may not be who you want greenfielding a new service at speed. If you genuinely need more than one, hire the primary role now and add the next when the work is real. If the front end is a separate JavaScript app rather than Blazor, post it on its own and hire React developers for it.

★ Template

.NET developer job description template you can copy

Fill every bracket. A bracket you cannot fill is a scoping decision you have not made yet, and candidates will find it in the first call anyway.

That last line does more filtering than the rest of the posting combined. It cannot be answered by a template reply, and the answer tells you whether someone has run a system long enough to regret a data-model or architecture choice. For scoping the work itself, our freelance job brief template covers deliverables, milestones and acceptance criteria.

★ Skills

What skills are required for a .NET developer?

Require modern C# and current .NET, ASP.NET Core, relational data modeling with SQL and EF Core, a real grasp of transactions and async concurrency, REST API design, Git, and testing with xUnit. Treat Azure or another cloud, Docker and Kubernetes, message brokers, Blazor and gRPC as preferred, because requiring every one of them at once shrinks your candidate pool for no gain.

If the front end is a real JavaScript app rather than Blazor, post it as its own role and hire React developers for it. Two specialists on defined milestones almost always beat one generalist stretched across both ends.

★ Seniority

How many years of experience should a senior .NET developer have?

Five or more years of professional backend work with at least three in C# and ASP.NET Core is the usual bar, but the years matter less than what they contain. A genuine senior has run a .NET service in production, debugged something that only failed under load, and made a data-model or architecture decision they can now explain the trade-offs of. Someone with six years of building similar CRUD services from a spec is a competent mid-level, not a senior.

Published 2026 data puts the median US freelance .NET rate near $85 per hour, with seniors in the $100 to $150 range. For comparison, US employers report .NET backend salaries roughly in the $95,000 to $150,000 range depending on market and seniority, so a contractor at $110 per hour part time on a defined scope is often the cheaper way to get a backend built. Full cross-role numbers are in our freelance developer rates guide, and the role page has the detail: hire freelance .NET developers.

★ Red flags

Five lines that quietly shrink your candidate pool

These appear in nearly every copied template, and each one costs you good applicants without improving the ones you get.

• A stack list with eighteen items. Naming C#, ASP.NET Core, EF Core, Azure, Docker, Kubernetes, Redis, SQL Server, Blazor, gRPC and eight more reads as a team that does not know what it needs. Confident senior people assume the role is unfocused and move on. List the five to seven things you truly use.
• Not saying which .NET. A posting that lists both .NET Framework and .NET 8 without saying which the job is on reads as a team that has not decided, or is hiding a big migration behind a feature role. Say it plainly.
• No rate or salary range. The strongest freelancers have work and will not spend an hour discovering your budget is half their rate. A range is the cheapest filter you have, and it works in both directions.
• A take-home that takes a weekend. Anything over three hours filters for availability, not skill. A short timed task against a real schema, or an hour reading their existing service together, tells you more.
• Requiring a decade of a specific framework. "10+ years of ASP.NET" excludes strong people, and half of that history was a different platform anyway. Ask for production .NET experience and let them prove the depth in the interview.

★ Screening

Four screening questions that sort the field fast

You do not need a whiteboard. These four take about twenty minutes and separate people who have shipped and operated .NET from people who have finished a course.

If the posting goes out publicly, the bottleneck moves from writing it to reading the replies. A .NET posting on a large job board can pull several hundred applications in a week, most of them template matches, and it is worth using something that can read every inbound resume against your criteria before you spend evenings doing it manually. The general vetting checklist is in how to vet a freelancer.

★ Contract or employee

Adapting the description for a contractor

An employee job description sells a career: growth, team, ownership over time. A contract brief sells a defined piece of work, so three things change. Replace responsibilities with deliverables, because "own the backend" means nothing when the engagement is eight weeks. Replace the salary band with an hourly rate and an estimated weekly commitment. Add the practical terms: who owns the repository (yours, from day one), how milestones are approved and paid, what handoff includes, and what happens if scope changes.

Keep the classification clean while you are at it. A contractor sets their own hours, uses their own equipment and is paid per milestone or invoice, not on your payroll cycle. Our guide to 1099 vs W2 covers where US teams get that wrong, and what to include in a freelance contract covers IP assignment, which matters more than most first-time hirers expect when the deliverable is a service your business depends on.

★ FAQ

.NET developer job description: common questions