.NET Developer Resume Examples & Free Template (PDF, Word)

Fill in this .NET developer resume template for free, then download it in PDF or Word. Further down are 3 C# developer resume examples for ASP.NET Core roles, from junior to lead, and the 6 steps I use as an ex-Google recruiter to write one.

4.9 5.0
The .NET Developer resume template filled in for a senior C# developer at Stack Overflow: profile summary, 7 skills rows, education and 11 work experience bullets
Emmanuel Gendre Ex-Google recruiter / Tech resume writer Updated Free, ATS-friendly, no signup

Interactive resume template generator

Interactive .NET Developer Resume Template

Fill in the side panel, then download your resume as a PDF or a Word file.

Edits update live as you type. Toggle Edit to rewrite paper text directly.

Edit mode is on. Click anywhere on the resume to rewrite text. Side-panel placeholders still update live.

Connor McGee Senior .NET Developer

New York, NY • connor.mcgee@gmail.com • +1 646-555-0193

Profile Summary

  • Senior .NET Developer with 9 years of experience building web apps and APIs on .NET and Microsoft Azure for a developer knowledge-sharing SaaS and an online legal services platform, focused on .NET modernization, ASP.NET Core APIs, and SQL Server performance.
  • Hands-on with languages (C#, T-SQL), web (ASP.NET Core, Angular), data access (Entity Framework Core, Dapper), databases (SQL Server, Redis), messaging (Azure Service Bus), cloud and CI/CD (Microsoft Azure, Azure DevOps), and testing (xUnit), backed by a strong command of async/await, LINQ, and SOLID design.
  • Deep experience in incremental .NET Framework to .NET 8 migrations, versioned public API design, SQL Server query tuning, and event-driven background processing, applying clean architecture with CQRS and integration tests on every pull request to deliver daily releases that don’t break the integrations customers rely on.
  • Partners closely with product managers, designers, front-end engineers, SRE, and customer support in two-week sprints with trunk-based development, from agreeing on an API contract with the teams that call it to fixing the bugs support escalates.
  • Coaches developers on EF Core performance and async/await pitfalls through code review and pairing, runs a monthly .NET upgrade clinic, and maintains the service template every new .NET project at the company starts from.

Technical Skills

Languages & Runtimes:
C#, .NET 8, .NET 10, .NET Framework 4.8, T-SQL, TypeScript, PowerShell
Web & API Frameworks:
ASP.NET Core, Web API, Minimal APIs, MVC, Razor Pages, Blazor, SignalR, gRPC, Angular
Data Access & Databases:
Entity Framework Core, Dapper, LINQ, SQL Server, Azure SQL Database, PostgreSQL, Redis
Architecture & Messaging:
Microservices, Clean Architecture, Domain-Driven Design, CQRS, MediatR, Azure Service Bus, RabbitMQ, MassTransit, Hangfire
Cloud & DevOps:
Microsoft Azure (App Service, Functions, AKS), Azure DevOps, Docker, GitHub Actions, Bicep
Testing Frameworks:
xUnit, Moq, NUnit, FluentAssertions, Testcontainers, Playwright, SonarQube
Security & Observability:
OAuth 2.0, OpenID Connect, Microsoft Entra ID, Azure Key Vault, Application Insights, OpenTelemetry, Serilog

Education

Rutgers University B.S. in Computer Science
New Brunswick, NJ • Sep 2013 to May 2017

Work Experience

Stack Overflow Senior .NET Developer
New York, NY • Apr 2020 to Present
  • Moved the Stack Overflow for Teams web app from .NET Framework 4.8 to .NET 8 one route at a time behind a YARP reverse proxy, upgrading 38 projects with the .NET Upgrade Assistant and no customer downtime, which cut compute cost for the web tier by 36%.
  • Designed version 3 of the Teams public REST API in ASP.NET Core Minimal APIs with OpenAPI contracts, OAuth 2.0 scopes and per-tenant rate limits, shipping 85 endpoints with zero breaking changes for the 1,400 customer integrations still on version 2.
  • Rewrote the slowest Entity Framework Core queries behind Teams search and reporting as Dapper calls with covering indexes on SQL Server, using execution plans and Query Store data to pick the targets, cutting p95 dashboard query time from 2.8 seconds to 310ms.
  • Split billing and permissions out of the Teams monolith into 3 bounded contexts with clean architecture layers, CQRS handlers in MediatR and architecture tests that block cross-module references, cutting lead time for billing changes from 9 days to 2.
  • Moved webhook delivery, email digests and search indexing off the request path onto Azure Service Bus with MassTransit, the outbox pattern and idempotent consumers, handling 3.6 million messages a day and cutting failed webhook deliveries from 2.1% to 0.04%.
  • Profiled the Teams question page with dotTrace and BenchmarkDotNet, removed hot-path allocations with Span<T> and pooled buffers, and cached tag and permission lookups in Redis, cutting p95 page latency from 480ms to 140ms at the weekday peak.
  • Built an integration test suite on xUnit, WebApplicationFactory and Testcontainers that runs against real SQL Server instances on every pull request, with SonarQube quality gates in CI, cutting bugs that reached production from 14 a quarter to 4.
  • Containerized 16 .NET services with Docker and moved them from VMs to Azure Kubernetes Service, with Azure DevOps YAML pipelines, Bicep templates and Application Insights alerts on every service, taking production releases from weekly to 8 a day.
LegalZoom .NET Developer
Glendale, CA • Jun 2017 to Mar 2020
  • Rebuilt the business formation checkout as an Angular front end on ASP.NET Web API endpoints, with server-side validation for 50 state filing rules, cutting checkout abandonment from 31% to 23%.
  • Added OAuth 2.0 sign-in with IdentityServer4 and role-based access to the customer document vault, closing all 12 findings from the annual penetration test before the next audit.
  • Automated the nightly state filing batch with Hangfire jobs and SQL Server stored procedures, saving the operations team 25 hours of manual filing work a week.

Done editing? Download a real PDF (selectable text, ATS-friendly, US Letter) or an editable Word file if a recruiter asks for one.

About this template

A .NET Developer resume template, built by a tech recruiter.

A .NET developer builds and looks after the software a lot of companies run on: banking platforms, insurance claims systems, hospital portals, internal tools. Day to day, you’re writing C# on .NET 8 or .NET 10, exposing it through ASP.NET Core APIs, storing data in SQL Server with Entity Framework Core and shipping it to Azure. You’ll often keep older .NET Framework code running while you move it forward, too.

The trouble is that most .NET resumes, by nature, tend to show the same stack and similar projects: C#, ASP.NET Core, Entity Framework, SQL Server, Azure. With that list alone, a recruiter can’t tell you apart from everyone else who lists it. What gets you the call is proof of what you did with those tools. Think of the legacy app you moved to modern .NET, the slow queries you fixed, the API other teams build on or the releases you made safer.

I’ve designed this .NET resume template so that proof has a place to go. Job 1 gets a bullet for each of the 8 areas recruiters screen .NET developers on, from modernization to Azure deployment. The 3 C# resume samples below do the same at junior, senior and lead level. Further down, I’ve split the writing into 6 steps to write a .NET Developer resume.

Would you rather have a recruiter look at the resume you already have? Upload it for a free CV review and I’ll go through it myself.

Industry signal

What the market says about .NET Developer roles

There’s steady demand for .NET developers in 2026, but you’re competing with a big pool. Software developers were the most posted tech job in the US in September, with 47,598 new openings according to CompTIA, and 27% of developers in Stack Overflow’s 2026 survey did extensive C# work in the past year. Hiring also favors experience: Indeed found that 71% of the past year’s growth in software development postings came from senior roles. So your resume has to show senior-level results from the first lines.

+10% Growth in US software developer jobs by 2035 US Bureau of Labor Statistics
$55.84/hr Average hourly pay, US .NET Developer job ads Indeed
  • Anton Martyniuk @AntonMartyniuk · Microsoft MVP, .NET software architect
    Dear recruiters, if you're looking for a .NET developer who knows: 1. C#, Java, Python, and Go 2. Modern ASP .NET Core and the old .NET Framework 3. Docker and Kubernetes in production 4. Azure, AWS, and GCP (all three, naturally) 5. Terraform for infrastructure as code…
  • Mukesh Murugan @iammukeshm · Microsoft MVP, teaches .NET at codewithmukesh
    The system design round decides most senior .NET offers. And almost nobody asks you to design Instagram. They ask about things you'd actually build at work. A nightly 2 GB import that must not take the API down. An export that takes four minutes to finish.
  • Julio Casal @julioc · Founder of .NET Academy, ex-Microsoft
    Junior .NET devs keep asking me what skills to focus on. I analyzed 100+ Senior .NET job posts to find out. These are the skills that show up again and again, the ones employers expect senior .NET developers to master…

Resume Samples

.NET Developer Resume Examples

How different should your .NET developer resume look at 2 years, 9 years and 14? It’s very different, because hiring managers expect more scope at each step. I’ve written 3 .NET developer resume examples to show it. The junior moved from application support into a bank’s API team in Dublin, and the senior owns insurance claims services in Brno. The lead is taking warehouse software in Atlanta off .NET Framework. You can download each one as a PDF or a Word file, free and with no signup.

Junior .NET Developer Resume Example

Nobody expects a junior .NET developer to own the architecture, so your resume should prove you ship: the endpoints, queries and tests you wrote under review, and one bug fix you can measure.

Years of experience
2 years
Industry
Retail banking
Stack
C#.NETSQL ServerAzure DevOps
Download PDF Download Word

Click to download the Junior .NET Developer resume example as a PDF or a Word file. Free / No signup.

Ruairi Donnelly

Junior .NET Developer

Dublin, Ireland · ruairi.donnelly@gmail.com · +353 1 555 0142 · linkedin.com/in/ruairidonnelly

Profile Summary

  • Junior .NET Developer with 2 years building ASP.NET Core services for an Irish retail bank, after 3 years in application support on public sector .NET systems in Belfast.
  • Writes C# on .NET 8 and .NET 10, builds APIs in ASP.NET Core, uses EF Core on SQL Server, sends messages on Azure Service Bus with MassTransit, and tests with xUnit and Testcontainers.
  • Learning clean architecture and CQRS from the senior engineers, works within Central Bank of Ireland complaint handling rules, and writes a failing test for every bug before fixing it.
  • Part of a 7-person squad with 2 senior developers, a business analyst and a tester, plans in 2-week sprints, and meets the complaints operations team weekly to go through case bugs.
  • Keeps the squad’s production support runbook current, walks new joiners through Application Insights traces in their first week, and pairs with the tester on Playwright checks for the complaints screens.

Technical Skills

Languages & Runtimes:
C#, .NET 8, .NET 10, T-SQL, PowerShell
Web & API Frameworks:
ASP.NET Core Web API, Minimal APIs, Razor Pages (basics)
Data Access & Databases:
Entity Framework Core, LINQ, SQL Server, Dapper (basics)
Architecture & Messaging:
Clean Architecture, MediatR, Azure Service Bus, MassTransit
Cloud & DevOps:
Microsoft Azure (App Service), Azure DevOps, Docker, Git
Testing Frameworks:
xUnit, Moq, FluentAssertions, Testcontainers, Playwright
Security & Observability:
Application Insights, Serilog, Azure Key Vault, OAuth 2.0 (basics)
Page 2 of 2

Work Experience

AIB Junior .NET Developer Dublin, Ireland · Oct 2024 to Present
  • Built ASP.NET Core endpoints for the Verification of Payee check customers see before adding a new payee, with OpenAPI docs and request validation, handling 284,000 checks in the first month.
  • Moved the open complaints screen from stored procedures to EF Core and added the index the SQL Server execution plan called for, cutting load time from 4.2 seconds to 0.6.
  • Upgraded 4 internal services to .NET 10 before .NET 8 support ends in November 2026, then turned on nullable reference types and fixed the 23 null reference bugs they exposed.
  • Wrote a MassTransit consumer on Azure Service Bus that sends complaint acknowledgement letters with retries and a dead-letter queue, cutting late letters from 37 a quarter to 2.
  • Split case notes out of a 2,400-line controller into MediatR commands and queries using the team’s clean architecture template, cutting the time to add a complaint type from 4 days to 1.
Kainos Application Support Engineer Belfast, UK · Jul 2021 to Sep 2024
  • Traced a memory leak in a public sector client’s .NET Windows service with memory dumps and PerfView, then gave developers the heap analysis, cutting unplanned restarts from 6 a month to 0.
  • Wrote Playwright smoke tests for the 12 most used journeys on 3 client web apps and ran them after every release, catching 7 broken releases before any user reported a problem.
  • Moved release checks for 3 client apps into Azure DevOps pipelines with approval gates and Application Insights availability tests, cutting rollbacks after release from 6 a year to 1.

Education

Ulster University BSc (Hons) in Computing Science Jordanstown, UK · Sep 2017 to Jun 2021

Senior .NET Developer Resume Example

At senior level, your .NET resume has to show what you own end to end: a domain or a group of services, the design calls behind them, and the numbers that changed once they were yours.

Years of experience
9 years
Industry
Insurance (claims)
Stack
.NETApache KafkaKubernetesRedis
Download PDF Download Word

Click to download the Senior .NET Developer resume example as a PDF or a Word file. Free / No signup.

Katarina Novotná

Senior .NET Developer

Brno, Czechia · katarina.novotna@gmail.com · +420 605 555 197 · linkedin.com/in/katarinanovotna

Profile Summary

  • Senior .NET Developer with 9 years in insurance and consumer security software, now owning the claims handling services at Czechia’s second-largest insurer, from first notice of loss to payout.
  • Builds with C# on .NET 8 and .NET 10, ASP.NET Core, EF Core and Dapper on SQL Server, Apache Kafka and RabbitMQ, Redis, Docker and Kubernetes, and ships through Azure DevOps.
  • Models claims with domain-driven design in the claims team’s own terms (FNOL, reserves, subrogation), sends every payment event through a transactional outbox, and load tests releases against the last storm season peak.
  • Works with claims handlers, actuaries and loss adjusters, plans 2-week sprints with 2 product owners, and agrees every API change with the core insurance system team at a monthly integration review.
  • Mentors 3 mid-level developers, runs the design review for any change that touches payments, and wrote the claims coding guidelines every new developer reads in their first week.

Technical Skills

Languages & Runtimes:
C#, .NET 8, .NET 10, .NET Framework 4.8, T-SQL, PowerShell
Web & API Frameworks:
ASP.NET Core Web API, Minimal APIs, CoreWCF, Blazor, gRPC
Data Access & Databases:
Entity Framework Core, Dapper, LINQ, SQL Server, Redis, PostgreSQL
Architecture & Messaging:
Domain-Driven Design, Clean Architecture, CQRS, MediatR, Apache Kafka, RabbitMQ, MassTransit
Cloud & DevOps:
Microsoft Azure (AKS, Key Vault), Azure DevOps, Docker, Kubernetes, Bicep
Testing Frameworks:
xUnit, NSubstitute, FluentAssertions, Testcontainers, k6, SonarQube
Security & Observability:
OAuth 2.0, OpenID Connect, Microsoft Entra ID, OpenTelemetry, Dynatrace, Grafana
Page 2 of 2

Work Experience

Kooperativa (Vienna Insurance Group) Senior .NET Developer Brno, Czechia · Jan 2021 to Present
  • Broke the claims codebase into 4 bounded contexts (intake, assessment, payment, recovery) inside a modular monolith, cutting lead time for a claims rule change from 3 weeks to 4 days.
  • Published claim payment events to Apache Kafka through a transactional outbox, with idempotent consumers keyed on payment ID in the finance service, taking duplicate payouts from 11 a year to 0.
  • In the September 2024 floods, profiled the claim intake API with dotTrace, cut upload allocations and cached policy lookups in Redis, holding p95 at 380 ms at 6 times normal volume.
  • Designed the versioned ASP.NET Core API partner garages use to report motor damage, with OpenAPI contracts and OAuth 2.0 client credentials, moving 38% of motor claims off email.
  • Built Azure DevOps pipelines that ship the claims services as Docker images to Azure Kubernetes Service with Bicep and Key Vault, taking releases from once a month to 3 a week.
Avast Software Engineer Brno, Czechia · Sep 2017 to Dec 2020
  • Moved the license activation service from .NET Framework 4.7 to .NET Core 3.1 on Linux containers and rewrote its WCF endpoints as REST, cutting its servers from 18 to 7.
  • Replaced Entity Framework 6 queries on the subscription renewal path with Dapper and covering indexes in SQL Server, cutting database CPU during the nightly renewal run from 86% to 41%.
  • Added xUnit integration tests and SonarQube quality gates to every pull request on the billing services, which cut payment bugs found after release by 61% in a year.

Education

Masaryk University M.Sc. in Informatics Brno, Czechia · Sep 2012 to Jun 2017

Lead .NET Developer Resume Example

For a lead .NET developer, the resume is about other engineers as much as code: the migration plan you wrote, the standards several teams follow, and the developers you’ve helped grow into senior roles.

Years of experience
14 years
Industry
Supply chain software (WMS)
Stack
.NETMicrosoft AzureRabbitMQTerraform
Download PDF Download Word

Click to download the Lead .NET Developer resume example as a PDF or a Word file. Free / No signup.

Terrance Boateng

Lead .NET Developer

Atlanta, GA · terrance.boateng@gmail.com · +1 404-555-0136 · linkedin.com/in/terranceboateng

Profile Summary

  • Lead .NET Developer with 14 years in supply chain and airline software at Manhattan Associates and Delta Air Lines, now leading .NET platform work on the Manhattan SCALE warehouse management system.
  • Chooses the stack for 2 teams: C# on .NET 8 moving to .NET 10, ASP.NET Core, EF Core and Dapper on SQL Server, RabbitMQ, Azure (AKS, Key Vault), Terraform and Azure DevOps.
  • Expert in warehouse execution (waves, pick tasks, RF handhelds), strangler fig migrations off .NET Framework, and event-driven integration, checking each release against the peak season throughput of the busiest sites.
  • Works with product management, customer support, cloud operations and the consultants who run go-lives, owns the quarterly technical roadmap, and joins the escalation call for every Sev-1 at a live warehouse.
  • Leads 9 engineers across 2 teams, chairs the SCALE architecture review, wrote the .NET coding standards 6 R&D teams follow, and has promoted 3 engineers to senior since 2022.

Technical Skills

Languages & Runtimes:
C#, .NET 8, .NET 10, .NET Framework 4.8, T-SQL, TypeScript, PowerShell
Web & API Frameworks:
ASP.NET Core, ASP.NET Web API, Minimal APIs, YARP, SignalR, Angular
Data Access & Databases:
Entity Framework Core, Dapper, SQL Server, Azure SQL Database, Redis
Architecture & Messaging:
Microservices, Clean Architecture, Vertical Slice Architecture, CQRS, RabbitMQ, MassTransit, Hangfire
Cloud & DevOps:
Microsoft Azure (AKS, App Service, Key Vault), Azure DevOps, Docker, Terraform
Testing Frameworks:
xUnit, Moq, Testcontainers, Playwright, SonarQube
Security & Observability:
OAuth 2.0, OpenID Connect, Microsoft Entra ID, Application Insights, OpenTelemetry
Page 2 of 2

Work Experience

Manhattan Associates Lead Software Engineer, R&D Atlanta, GA · Apr 2018 to Present
  • Wrote the migration plan that moved 47 SCALE services from .NET Framework 4.8 to .NET 8 over 6 releases, routing traffic service by service through YARP, with 0 customer rollbacks.
  • Set the reference architecture for new SCALE services (clean architecture, vertical slices, ADRs) and ran the weekly design review for 6 teams, cutting design approval from 3 weeks to 5 days.
  • Replaced database polling for pick task assignment with RabbitMQ and idempotent MassTransit consumers, cutting the wait between wave release and the first task on RF handhelds from 40 seconds to 2.
  • Moved cloud-hosted SCALE environments onto Docker images on AKS with Terraform and Azure DevOps pipelines, cutting the setup of a new customer environment from 3 weeks to 2 days.
  • Brought Testcontainers integration suites and SonarQube quality gates into every SCALE pull request and coached 9 engineers on writing the tests, cutting customer-found defects per release by 47%.
Delta Air Lines Senior Software Development Engineer Atlanta, GA · Jun 2012 to Mar 2018
  • Built versioned ASP.NET Web API services for crew scheduling data, secured with OAuth 2.0 tokens, replacing 6 nightly file feeds and giving 11 internal apps crew changes within a minute.
  • Profiled the crew reassignment service with PerfView during irregular operations, removed per-flight allocations and cached crew legality rules in Redis, cutting a storm-day recalculation from 22 minutes to 4.
  • Redesigned the SQL Server schema behind crew pay and pairing history with partitioned tables and filtered indexes, cutting the monthly crew pay close from 2 days to 5 hours.

Education

Georgia Institute of Technology B.S. in Computer Science Atlanta, GA · Aug 2008 to May 2012

Free resume review

A recruiter screen, but with feedback

You applied to hundreds of jobs: no result. Companies won’t give you feedback, so you’re stuck in a loop. Rejections will keep coming until you know what’s wrong.

Let’s break this cycle today!

I’ll screen your resume the same way I did at Google.

You’ll get:

  • Your resume sections and content scored.
  • A clear list of what to improve, why, and how.
  • Behind the scenes secrets on the screening process.

How I rewrite .NET Developer resumes

How to write a .NET Developer resume

Emmanuel Gendre, ex-Google recruiter

Emmanuel Gendre Ex-Google recruiter, tech resume writer

I worked in recruiting for 13 years, and many of those years were at Google. Now I rewrite tech resumes, and .NET ones tend to follow the same pattern: years of solid enterprise work squeezed into lines like “Developed and maintained C# applications”. But hiring managers need to understand how, which you need to show by adding the techniques, tools and numbers behind each piece of work: the framework version you moved off, the query you made 10 times faster, the outage your message queue prevented.

When a C# developer hires my tech resume writing service, I rewrite the resume line by line and suggest what to add, so every bullet carries that kind of detail. If you’re doing it yourself, though, focus on these 6 steps. I’ve written every one of them with .NET examples.

  1. Step 1 Format & layout One column, plain section titles and a PDF that any ATS can read. Go to step 1
  2. Step 2 Profile Summary 5 bullets up top that show your seniority and stack at a glance. Go to step 2
  3. Step 3 Work Experience Cover all 8 areas a .NET hiring manager checks in your latest job. Go to step 3
  4. Step 4 Bullet Points Turn “maintained C# services” into a bullet a hiring manager believes. Go to step 4
  5. Step 5 Technical Skills Which .NET tools go in your 7 skills rows, plus 5 soft skills. Go to step 5
  6. Step 6 Keywords & Metrics The keywords .NET recruiters search for and 24 numbers that prove your work. Go to step 6

Step 1 · Format & Layout

.NET Developer resume format and layout

Let’s get the easy part out of the way first. Two readers see your resume before anyone judges your C#: the ATS, which pulls the text out of the file, and a recruiter hunting for your title and current employer within seconds. If your layout and file format are right, both of them find what they need.

01ATS Compliance

ATS compliance for your .NET Developer resume

Almost every company you apply to keeps resumes in an Applicant Tracking System (ATS), which breaks each file into fields such as job title, company, dates and skills. Months later, a recruiter can search all of it for “.NET 8” and “SQL Server”. Tables, text boxes and two-column layouts mess up that split, so your skills can land under the wrong heading, where the search never looks. My article on how ATS software indexes a resume covers the mechanics. For .NET roles, everything here comes down to 3 rules:

The 3 rules
  1. Use a 100% text based format (no Canva!)

  2. Avoid tables, pictures, and complex structures.

  3. Use the most predictable section names, like “Profile Summary” and “Work Experience”

02Design & Layout

.NET Developer resume design and layout

Developers sometimes send me resumes with skill bars, a dark code-editor theme or a sidebar full of Microsoft logos. I get it. Still, recruiters hate fancy designs. They’ve read so many resumes that their eyes jump straight to where the job title and dates usually sit. Move those with a creative layout and they’ll have to hunt, which most of them won’t bother to do.

Go plain and predictable instead: one column, one font, black text and the usual section titles. If there’s real C# work on your GitHub, add the link to your header. .NET hiring managers do click it. This .NET template follows every spec on the list below. You’ll only need the list if you build your resume from scratch in Word or Google Docs.

Layout Spec
Columns
One. No sidebars, tables, columns, pictures or tabs.
Margins
0.7 in on all four sides
Body size
10 to 11 pt
Type
One family, weight for hierarchy
Length
One page under 5 years, two after
Section order
Summary, Skills, Experience, Education
PDF

03File Format

Resume file format for your .NET Developer resume

PDF is the right default for a .NET resume. Your layout looks identical on the recruiter’s laptop, and an ATS won’t have any trouble with a PDF exported from Word or Google Docs. Don’t switch to Word unless a posting or an agency asks for it: some staffing firms that place developers in Microsoft shops reformat every candidate into their own branded layout. For other cases, like plain-text forms, see my article on picking a file format for your resume.

Format Guide
PDF
Your default. Layout holds, text stays selectable.
Word (.docx)
When the posting or a recruiter asks for it. Use the Word download above.
Plain text
For portals that make you paste into a box
Never
Images, scans, password-protected PDFs, shared-drive links
File name
Connor-McGee-NET-Developer.pdf

Step 2 · Profile Summary

.NET Developer profile summary

Start your resume with a profile summary, even if you’re a junior. My article on the way recruiters screen resumes explains why: screening runs in 2 steps, and the first one is quick. For many .NET candidates, these 5 bullets are all a recruiter’s going to read in that first step.

On a .NET resume, those bullets have 3 questions to answer fast. Which .NET versions and frameworks do you work in? How big and how critical are your systems? Do you work well with the people around the code? Each bullet below handles part of that, in this order. My profile summary guide for tech resumes goes through the full method.

  1. 1

    Title, years and scope

    Open with the exact title from the posting (.NET Developer, C# Developer or Software Engineer), then your years, what you build and the industry you build it for. By the last word, a recruiter shouldn’t have to guess your level.

  2. 2

    Your stack

    Group your tools like .NET job ads do: languages, web frameworks, data access, databases, messaging, cloud and testing. Recruiters go down the requirements and look for each group here, so your stack line should carry the posting’s own product names.

  3. 3

    Domain expertise

    Your strongest areas, like .NET Framework migrations, API design or SQL Server tuning, and the practices you use there (clean architecture, CQRS, integration tests). That’s how a hiring manager guesses what you’d own in your first month.

  4. 4

    Collaboration

    The people you build with (product, design, front-end, QA, SRE) and how you work together: sprints, code review, release planning. Many .NET teams support business users directly, so show them you’re comfortable talking to those users too.

  5. 5

    Leadership

    How you help other developers: code reviews, pairing sessions, a service template, an upgrade guide. Direct reports are optional here. The hiring manager wants to know the team gets better with you on it.

.NET Developer resume summary example, from the template above
  • Senior .NET Developer with 9 years of experience building web apps and APIs on .NET and Microsoft Azure for a developer knowledge-sharing SaaS and an online legal services platform, focused on .NET modernization, ASP.NET Core APIs, and SQL Server performance.
  • Hands-on with languages (C#, T-SQL), web (ASP.NET Core, Angular), data access (Entity Framework Core, Dapper), databases (SQL Server, Redis), messaging (Azure Service Bus), cloud and CI/CD (Microsoft Azure, Azure DevOps), and testing (xUnit), backed by a strong command of async/await, LINQ, and SOLID design.
  • Deep experience in incremental .NET Framework to .NET 8 migrations, versioned public API design, SQL Server query tuning, and event-driven background processing, applying clean architecture with CQRS and integration tests on every pull request to deliver daily releases that don’t break the integrations customers rely on.
  • Partners closely with product managers, designers, front-end engineers, SRE, and customer support in two-week sprints with trunk-based development, from agreeing on an API contract with the teams that call it to fixing the bugs support escalates.
  • Coaches developers on EF Core performance and async/await pitfalls through code review and pairing, runs a monthly .NET upgrade clinic, and maintains the service template every new .NET project at the company starts from.

Step 3 · Work Experience

.NET Developer work experience

Here’s the second step of the screen from Step 2. Now the recruiter actually reads your experience, newest job first, and that job carries roughly 95% of the decision. That’s logical: your current work is the best evidence of the developer they’d be hiring.

So in your latest job, give every area of the .NET Developer role profile its own bullet. The role profile is the checklist hiring managers hold your resume against, and a missing area reads as a gap. If there’s nothing about testing, for instance, they’ll wonder whether you test at all.

.NET Developer role profile
  1. C# & .NET Modernization

    You move old .NET code onto a version Microsoft still supports. Many companies hiring .NET developers in 2026 still run .NET Framework apps, and that backlog’s often the reason the job exists. Show them how you used incremental migration and the .NET Upgrade Assistant to move apps over without an outage.

    Techniques
    incremental migration, side-by-side routing, dependency upgrades, nullable reference types
    Tools
    .NET Upgrade Assistant, YARP, .NET 8, .NET 10
    Metrics
    projects upgraded, hosting cost, response time
  2. ASP.NET Core API Design & Security

    You design the APIs other teams and customers build on. A breaking change or a leaky endpoint lands on someone else’s desk, which is why hiring managers ask how you version and secure your APIs. Walk them through how you used OpenAPI contracts and OAuth 2.0 scopes to add features without breaking a single client.

    Techniques
    contract-first design, API versioning, rate limiting, input validation
    Tools
    ASP.NET Core, Minimal APIs, OpenAPI, Microsoft Entra ID
    Metrics
    endpoints shipped, breaking changes, API error rate
  3. EF Core & SQL Server Data Access

    You keep the data layer fast and correct. Slow queries sit behind a lot of .NET performance complaints, and plenty of hiring managers have watched a harmless-looking LINQ query turn into a full table scan. Tell them how you used execution plans and Dapper on the hot paths to bring query times down.

    Techniques
    query tuning, indexing, N+1 fixes, zero-downtime migrations
    Tools
    Entity Framework Core, Dapper, SQL Server, Query Store
    Metrics
    query time, database CPU, query timeouts
  4. Clean Architecture & Domain Design

    You shape the code so the next change is easy to make. A tangled solution slows every feature down, and that’s often why a senior .NET role is open in the first place. Describe how you used bounded contexts and CQRS with MediatR to make a part of the system safe to change again.

    Techniques
    domain-driven design, bounded contexts, dependency injection, architecture tests
    Tools
    MediatR, NetArchTest, Visual Studio, Rider
    Metrics
    lead time for changes, defects per release, modules separated
  5. Messaging & Background Processing

    You run the work that happens after the request returns. Emails, payments and data syncs that fail with no alert cost money and trust, so managers want proof that nothing’s getting lost. Point out how you used Azure Service Bus with the outbox pattern to keep messages flowing through retries and outages.

    Techniques
    outbox pattern, idempotent consumers, dead-letter handling, retries with backoff
    Tools
    Azure Service Bus, RabbitMQ, MassTransit, Hangfire
    Metrics
    messages a day, failed deliveries, processing lag
  6. Performance Tuning & Caching

    You find out why a page is slow, then fix it. Users leave and cloud bills climb when an endpoint takes a second too long, and guessing won’t find the cause. Explain how you used dotTrace or BenchmarkDotNet and a Redis cache to cut latency, and give the numbers from before and after.

    Techniques
    profiling, allocation cuts, caching, load testing
    Tools
    dotTrace, BenchmarkDotNet, Redis, k6
    Metrics
    p95 latency, cache hit rate, memory allocations
  7. Automated Testing & Code Quality

    You stop bugs before they reach customers. A bug in production costs a hotfix, a support ticket and a little trust, so teams look for developers who write tests without being told to. Mention how you used xUnit with Testcontainers and CI quality gates to cut the bugs that slip through.

    Techniques
    unit tests, integration tests, contract tests, code review
    Tools
    xUnit, Moq, Testcontainers, SonarQube
    Metrics
    escaped bugs, test run time, code coverage
  8. Azure Deployment & CI/CD

    You ship your own code to Azure and watch it once it’s live. More .NET teams now deploy and run their own services, and a hiring manager will ask whether you’ve done it yourself. Let them know how you used Azure DevOps pipelines and Application Insights to release more often with fewer rollbacks.

    Techniques
    containerization, deployment slots, infrastructure as code, release monitoring
    Tools
    Azure DevOps, Docker, Azure Kubernetes Service, Bicep
    Metrics
    release frequency, failed deployments, recovery time

If the posting says full-stack .NET, give your front-end work in Angular, React or Blazor its own bullet. Coming from IT support or QA? The debugging, test automation and release work you did there counts as .NET experience once each piece comes with a result.

Submit your resume for a free review!

Step 4 · Bullet Points

.NET Developer resume bullet points

Bullet points take most of the hours I put into a rewrite. Over the years, my way of writing them became the Level System, which extends the XYZ formula from my Google days with the layers a technical resume needs. My article on how I write resume bullet points for tech roles explains it in full.

There are 5 levels, each one a question about your work, and whatever you answer gets added to the bullet. On a .NET resume, the final answer tends to be a response time, a query time, an error rate or a release count. Below, you’ll see one bullet grow a level at a time until it’s finished.

  1. Level 1Task

    What did I work on? Start with a strong verb and one piece of work you finished. On its own, it’s just a Jira ticket, so keep going.

    Rebuilt the claims intake service.

  2. Level 2+ Techniques

    How did I do it? Add the techniques. They show a hiring manager which engineering calls were yours.

    Rebuilt the claims intake service, adding async processing and idempotent retries.

  3. Level 3+ Tools

    What tools did I use? Write the real product names. A recruiter searching for “Azure Service Bus” won’t find “a message queue”.

    Rebuilt the claims intake service on .NET 8 with ASP.NET Core and Azure Service Bus, adding async processing and idempotent retries.

  4. Level 4+ Method

    What method did I follow? Mention the pattern or practice behind the work. Few candidates do, and it tells a hiring manager how you plan for failure.

    Rebuilt the claims intake service on .NET 8 with ASP.NET Core and Azure Service Bus, adding async processing and idempotent retries, following the outbox pattern with a dead-letter queue for every message type.

  5. Level 5+ Metric

    What was the result? End with one number someone outside engineering cares about. It’s the part that makes the rest believable.

    Rebuilt the claims intake service on .NET 8 with ASP.NET Core and Azure Service Bus, adding async processing and idempotent retries, following the outbox pattern with a dead-letter queue for every message type, and cut claims stuck in manual review from 1,900 a week to 140.

    1. 01 Task What you worked on
    2. 02 Techniques How you did it
    3. 03 Tools The stack you used
    4. 04 Method The method you followed
    5. 05 Metric The result, one number

Most of these numbers are sitting in tools you use every week. Application Insights keeps response times and failure rates, Azure DevOps logs every release, Query Store remembers your slowest queries and Jira counts the bugs. Open them before you write a single bullet.

Step 5 · Technical Skills

.NET Developer resume skills

Most .NET job ads sort their requirements into the same buckets: C# and .NET versions, ASP.NET Core, data access, messaging, Azure, testing and security. Copy each product name exactly as the ad writes it. A recruiter who filters the ATS for “EF Core” might never see a resume that only says “Entity Framework”.

Still, only list what your bullets can back up. If gRPC or Blazor is on your resume, expect an interviewer to ask about the project. Under this step you’ll find my 7 skill categories for .NET resumes, a finished set of skills rows, and the soft skills .NET teams care about most. Keywords get their own step next.

The 7 skill categories for a .NET Developer resume

A star means most .NET job descriptions I see ask for that item, so lead each row with the starred ones. Add the rest only if you’ve used them at work.

Languages & Runtimes

C# first, with the .NET versions you’ve shipped on. Listing .NET Framework next to .NET 8 or 10 shows you’re comfortable with old and new code.

C#.NET 8.NET 10.NET Framework 4.8T-SQLTypeScriptPowerShell

Web & API Frameworks

ASP.NET Core and how you use it (Web API, Minimal APIs, MVC, Blazor), plus a front-end framework if the job is full stack.

ASP.NET CoreASP.NET Web APIMinimal APIsASP.NET MVCRazor PagesBlazorSignalRgRPCAngular

Data Access & Databases

Your ORM, your database and how you query it. Entity Framework Core with SQL Server is the pair most .NET postings ask for.

Entity Framework CoreSQL ServerDapperLINQAzure SQL DatabasePostgreSQLAzure Cosmos DBRedis

Architecture & Messaging

Your design patterns and your message broker. Senior postings often pair microservices with Azure Service Bus or RabbitMQ.

MicroservicesAzure Service BusClean ArchitectureDomain-Driven DesignCQRSMediatRRabbitMQMassTransitHangfire

Cloud & DevOps

The Azure services you deploy to, your CI/CD platform, Docker and the tool you use for infrastructure as code.

Microsoft AzureAzure DevOpsDockerAzure App ServiceAzure FunctionsAzure Kubernetes ServiceGitHub ActionsBicepTerraform

Testing Frameworks

Your test framework, a mocking library and the tools that run tests against real dependencies. xUnit with Moq is the most common pair.

xUnitMoqNUnitNSubstituteFluentAssertionsTestcontainersPlaywrightSonarQube

Security & Observability

How users sign in and how you watch production: OAuth 2.0 and Entra ID on one side, Application Insights and logging on the other.

OAuth 2.0Application InsightsMicrosoft Entra IDOpenID ConnectASP.NET Core IdentityAzure Key VaultOpenTelemetrySerilog

A finished .NET Developer skills section

Technical Skills sample, from the template above
Languages & Runtimes
C#, .NET 8, .NET 10, .NET Framework 4.8, T-SQL, TypeScript, PowerShell
Web & API Frameworks
ASP.NET Core, Web API, Minimal APIs, MVC, Razor Pages, Blazor, SignalR, gRPC, Angular
Data Access & Databases
Entity Framework Core, Dapper, LINQ, SQL Server, Azure SQL Database, PostgreSQL, Redis
Architecture & Messaging
Microservices, Clean Architecture, Domain-Driven Design, CQRS, MediatR, Azure Service Bus, RabbitMQ, MassTransit, Hangfire
Cloud & DevOps
Microsoft Azure (App Service, Functions, AKS), Azure DevOps, Docker, GitHub Actions, Bicep
Testing Frameworks
xUnit, Moq, NUnit, FluentAssertions, Testcontainers, Playwright, SonarQube
Security & Observability
OAuth 2.0, OpenID Connect, Microsoft Entra ID, Azure Key Vault, Application Insights, OpenTelemetry, Serilog

Soft skills for a .NET Developer resume

Nobody believes “excellent communicator” in a skills list. Proof in a bullet works much better. Here are 5 that hiring managers on .NET teams look for, each paired with a bullet you could put on your resume.

  • Taking on the legacy code nobody else wants to touch

    Resume bulletTook over a WCF billing service no one had changed in years, documented it and retired it within 6 months.

  • Explaining what an upgrade costs and saves to non-engineers

    Resume bulletGot budget for the .NET 8 upgrade by showing finance a $140,000 yearly saving in Windows server licenses and support.

  • Pairing with junior developers until they ship on their own

    Resume bulletPaired twice a week with 3 junior developers, who each shipped a production feature on their own within their first 4 months.

  • Protecting an API contract other teams depend on

    Resume bulletBlocked a field rename that would have broken 9 partner integrations, and shipped the change as a versioned v2 endpoint instead.

  • Staying on a production bug until the root cause is fixed

    Resume bulletTraced random timeouts in the order service to a sync-over-async deadlock, ending 3 weeks of failed checkouts for customers.

Step 6 · Keywords & Metrics

.NET Developer resume keywords and metrics

The last thing I check on any C# resume is simple: would it show up in a recruiter’s search, and would it convince anyone once it did? The first part is about keywords, the terms recruiters type into their ATS, like “ASP.NET Core” or “Azure Service Bus”. The second is about metrics: numbers that back up what your bullets claim.

Go through the 3 keyword tiers first, then test a real job ad in the keyword finder. The table at the bottom sorts 24 metrics by the 8 role-profile areas, and you’ll see each one inside a sample .NET bullet.

+42%

.NET Developer resume keywords, ranked

Click a keyword and you’ll see how job ads tend to word it. The same requirement comes in a few forms, and you want to recognize all of them.

Must-have

7

Put each one in your summary, in a Work Experience bullet and in your skills section.

In a job description“Strong experience writing production code in C#”

Strong supporting

10

Add the ones you’ve really used. When 2 resumes look alike, these often tip it.

In a job description“Build and maintain CI/CD pipelines in Azure DevOps”

Bonus

8

Nice extras. Mention them in a bullet or your skills section only if they’re true for you.

In a job description“Experience with Blazor for internal tools is a plus”

Extract .NET Developer keywords from a job description

Copy a .NET developer, C# developer or ASP.NET job description into the box. The finder pulls out the frameworks, Azure services, data tools and patterns it mentions and sorts them by tier, so you can see which must-haves you’re missing before you apply.

Must-have
Put these in your skills section and back each one with a bullet.
Strong supporting
Add the ones you’ve actually worked with. Skip the rest.

Nothing is uploaded: it all happens in your browser.

Metrics for a .NET Developer resume

Every area of the .NET role profile has 3 metrics here, and each one sits in a sample bullet. Pick one per bullet: any real number, even a small one, makes the bullet easier to believe.

MetricExample bullet
C# & .NET Modernization
Projects upgraded Count Projects or services moved from .NET Framework to modern .NET.Upgraded 38 projects in the Teams solution from .NET Framework 4.8 to .NET 8 with no customer downtime.
Hosting cost Money What the servers or cloud resources behind the app cost each year.Cut yearly hosting cost for the web tier by $210,000 after moving it from Windows VMs to Linux containers on .NET 8.
Response time after the upgrade Time Average or p95 response time before and after the move.Brought average API response time from 210ms to 95ms by moving the Teams API from .NET Framework 4.8 to .NET 8.
ASP.NET Core APIs
Endpoints shipped Count Public or internal API endpoints you built and own.Shipped 85 endpoints for version 3 of the public API in ASP.NET Core Minimal APIs, each documented in OpenAPI.
Breaking changes Count Releases that forced API consumers to change their code.Released 2 major API versions with 0 breaking changes for 1,400 customer integrations.
API error rate Percent Share of requests that end in a server error.Cut the 5xx error rate on the public API from 0.9% to 0.06% with request validation and per-tenant rate limits.
EF Core & SQL Server
Query time Time How long your slowest or most frequent queries take.Cut p95 dashboard query time from 2.8 seconds to 310ms by moving hot Entity Framework Core reads to Dapper.
Database CPU Percent Average CPU load on the database server at peak.Brought peak SQL Server CPU from 85% to 41% by fixing N+1 queries and adding covering indexes.
Query timeouts Count Queries that hit the timeout limit each week.Cut weekly SQL timeouts on the reporting pages from 320 to 9 after reading execution plans in Query Store.
Architecture & Domain Design
Lead time for changes Time Time from starting a change to running it in production.Cut lead time for billing changes from 9 days to 2 by splitting billing into its own bounded context.
Defects per release Count Bugs found after a release in the code you restructured.Reduced bugs per permissions release from 7 to 1 after moving the module to CQRS handlers with MediatR.
Modules separated Count Parts of a monolith moved into their own bounded context or service.Separated 3 modules from the Teams monolith, each with its own database schema and architecture tests.
Messaging & Background Jobs
Messages processed Count Messages your consumers handle each day.Process 3.6 million messages a day on Azure Service Bus with MassTransit consumers that are safe to retry.
Failed deliveries Percent Share of messages or webhooks that never reach their target.Cut failed webhook deliveries from 2.1% to 0.04% with the outbox pattern and dead-letter replay.
Processing lag Time Time between an event and the end of its background job.Brought search index lag after a new post from 14 minutes to 20 seconds by moving indexing to a queue.
Performance & Caching
p95 latency Time Response time for the slowest 5% of requests.Cut p95 latency on the question page from 480ms to 140ms after profiling it with dotTrace.
Cache hit rate Percent Share of reads answered by the cache.Raised the Redis hit rate for tag and permission lookups to 96%, taking that load off SQL Server.
Memory allocations Percent Memory allocated per request, which drives garbage collection pauses.Cut allocations per request on the rendering path by 63% with Span<T> and pooled buffers.
Testing & Code Quality
Escaped bugs Count Bugs that reach production before anyone catches them.Cut bugs reaching production from 14 a quarter to 4 with integration tests on every pull request.
Test run time Time How long the test suite takes in CI.Brought the CI test run from 38 minutes to 11 by running the Testcontainers suites in parallel.
Code coverage Percent Share of code your automated tests exercise.Raised line coverage on the billing module from 41% to 83%, starting with the code behind past incidents.
Azure & CI/CD
Release frequency Frequency How often your team deploys to production.Went from weekly releases to 8 a day after moving 16 services to Azure DevOps YAML pipelines on AKS.
Failed deployments Percent Share of deployments rolled back or followed by a hotfix.Cut failed deployments from 12% to 3% with deployment slots and automatic rollback on Application Insights alerts.
Mean time to recovery Time Average time to restore service after an incident.Brought mean time to recovery for API incidents from 47 minutes to 12 with alerts that link straight to a runbook.

What if you don’t have exact numbers?

  • 1

    Start with your own dashboards. Most of the metrics above already live in Application Insights, your Azure DevOps release history, SQL Server Query Store or your Jira board, often going back a year or more.

  • 2

    Round down when you estimate. “About 40 endpoints” or “close to 2 million messages daily” works on a resume, as long as the math behind it would hold up in an interview.

  • 3

    Count what you support. Without a before and after, the services, users, transactions or developers relying on your code still show the size of what you handle.

Free resume review

A recruiter screen, but with feedback

You applied to hundreds of jobs: no result. Companies won’t give you feedback, so you’re stuck in a loop. Rejections will keep coming until you know what’s wrong.

Let’s break this cycle today!

I’ll screen your resume the same way I did at Google.

You’ll get:

  • Your resume sections and content scored.
  • A clear list of what to improve, why, and how.
  • Behind the scenes secrets on the screening process.

Frequently asked

.NET Developer resume FAQ

It is, and there’s nothing to sign up for. Edit the panel, save your file as a PDF or in Word, and reopen the page whenever you change jobs or upgrade to a newer .NET version.

Yes. Click Word, next to Download PDF, and you’ll get a .docx you can change in Microsoft Word or Google Docs. Each of the 3 .NET resume examples has its own Word download as well. For applications, the PDF is still the better file. Keep the .docx for the agencies that ask for one.

Yes. American employers use the two words for one document, so send this template when a C# or .NET job ad asks for your CV. If you’re applying in the UK, keep the same layout and leave out a photo and your date of birth. The C# CV examples above work for both.

Yes. It uses a single column, plain section titles and real, selectable text in the PDF, and that’s what an ATS needs to read a resume correctly. After you’ve edited yours, test it with my free ATS checker for resumes to see exactly what the software pulls out.

With less than 5 years of experience, keep it to one page. With more experience, especially across several .NET versions, 2 pages is fine. Length isn’t what gets a resume rejected. Vague bullets are, so give every bullet a system you worked on and what changed.

Use the title from the posting. Companies say .NET Developer, C# Developer, ASP.NET Developer and Software Engineer (.NET) for the same job, and some job boards spell it “Dot Net Developer” or “dotnet developer”. Recruiters often search for the exact title, so it’s worth matching. If you’re applying to several, put the most common one in your header and mention both C# and .NET in your first summary bullet, so every search finds you. If you write C# for Unity games, my game developer resume template is a closer match.

Write the versions you’re working with, and add “.NET Core” once in brackets, like “.NET 8 (.NET Core)”. Microsoft dropped “Core” from the name with .NET 5, the release after .NET Core 3.1, but plenty of job ads still ask for a “.NET Core developer”. ASP.NET Core and Entity Framework Core kept the word, so write those in full.

Yes, if you’ve worked with it. Plenty of employers still run .NET Framework 4.8 apps, and they’re hiring people who can move them to modern .NET. List the version next to .NET 8 or .NET 10, and write a bullet about what you upgraded or kept running, so a recruiter reads it as experience you’ve built on.

Write a .NET developer resume that leads with the web side. Open your headline and summary with ASP.NET Core, and show which parts you’ve built with: Web API or Minimal APIs, MVC or Razor Pages, Blazor, SignalR. If you still maintain ASP.NET MVC 5 or Web Forms apps, list them and say which ones you’ve moved to ASP.NET Core.

Mention Azure in your headline and in the first line of your summary. Then write the services into your bullets: App Service, Functions, AKS, Service Bus, Key Vault, Application Insights. Many Azure .NET roles also want you to deploy your own code with Azure DevOps or GitHub Actions, so give that a bullet. If your job is mostly pipelines and infrastructure, my DevOps engineer resume template is the better fit.

Microsoft retired the Azure Developer Associate exam (AZ-204) on July 31, 2026, so if you already hold that certification, keep it on your resume with its date. Its replacement is the Azure AI Cloud Developer Associate (exam AI-200). If you’re a junior, the free Foundational C# certification from Microsoft and freeCodeCamp is a decent start. Certifications get you into more keyword searches, but a hiring manager still judges you on what your bullets show you’ve built.

Use a profile summary in its place. Recruiters screening a .NET developer resume want your title, your .NET stack and one result in the first lines, and a summary gives them that. That’s true for juniors as well, and the 5-bullet structure in Step 2 fits any level.

Choose numbers that mean something outside your team: API response times, query times, error rates, how often you release, bugs that reached production, and hosting or license costs an upgrade saved. Step 6 groups 24 of them by area, with a .NET example bullet for every one.

A .NET resume is narrower. The recruiter’s filtering for C#, ASP.NET Core and usually Azure, so put those words in your title, summary and bullets as well as your skills list. For a broader profile, see my back-end engineer resume examples, which cover more languages, or the full-stack developer resume template, where the front end counts as much as the back end. If a .NET posting mentions Angular or React, give your front-end work its own bullet, like the ones in my React developer resume template.

That you ship on your own inside a team. Give each kind of work its own bullet: endpoints, EF Core queries, tests, and a bug fix with a number attached. At 2 years, recruiters look for C#, .NET 8, ASP.NET Core, SQL Server and xUnit, and they don’t expect architecture decisions yet. Ruairi, the junior example above, has exactly 2 years, and every one of his bullets ends on a result.

If you’re a .NET fresher with no job yet, put your Education section and any internship near the top. After that, list 2 or 3 projects built like real team work, say an ASP.NET Core API using Entity Framework Core, tested with xUnit and deployed to Azure, each with a result. Already in IT support or QA? Write up the debugging, test automation and release work you did there, the way Ruairi does in the junior example.

More resources

More help with your .NET Developer resume