.NET Fullstack: market
Data as of November 19, 2026: 280 open .NET Fullstack jobs, 33% remote among jobs that state a work format; median advertised salary $6,166/mo (from 36 postings that state a salary). Source: Zorky, updated daily.
.NET Fullstack — full-stack development in the Microsoft / .NET ecosystem: one engineer builds both the server side in C# and ASP.NET Core and the user interface. Important clarification about the term: «.NET Fullstack» in practice means two different stacks. Variant 1 — «pure» .NET Fullstack: backend on ASP.NET Core + frontend on Blazor (Microsoft's component UI framework, where the interface is also written in C#) — the whole product in one language, almost no JavaScript. Variant 2 — .NET + SPA: backend on ASP.NET Core + frontend on React / Angular / TypeScript — classic split, frontend on the JavaScript stack. Both variants occur en masse in vacancies; when reading a vacancy, look at which frontend is specified. Role family: .NET Fullstack Developer (general — ASP.NET Core + Blazor or SPA), C# Fullstack Engineer, ASP.NET Core Developer with frontend responsibilities, Blazor Developer (focus on the Blazor frontend). Stack 2026: C# (must — 12 / 13), .NET 8 / 9 (LTS — .NET 8), ASP.NET Core (web framework), Entity Framework Core (ORM), Blazor (Server + WebAssembly + unified .NET 8 rendering model — Blazor United), SignalR (real-time), or React / Angular + TypeScript for the SPA variant, MS SQL Server or PostgreSQL, Redis, REST / gRPC / GraphQL, xUnit / NUnit (tests), Docker + Kubernetes, clouds — Azure (natural for .NET, but in CIS often replaced with local clouds and on-prem due to import substitution), CI/CD. Top stack: sql, react, c#, angular, azure. Among jobs with a stated work format, 33% are remote.
Data as of:
Key numbers for the .NET Fullstack market: open jobs, median salary, observed talent pool and remote share.
The .NET Fullstack market currently has 280 open roles, 240 of them freshly observed. Median salary $6,166/mo.
Among jobs with a stated work format, 33% are remote. Development is done well remotely; the nuance — .NET is strong in enterprise, and enterprise projects on average are slightly less remote-flexible than product startups (more often hybrid, especially in the financial and public sector).
⚠ salary known for 36 of 280 jobs; remote share from 220 with a stated format; 240 counted as fresh observations; trend and hiring difficulty are not shown
Timeline: postings and sources
How many .NET Fullstack postings appeared each week since Jun 1, and from how many sources. The lower chart separates market growth from coverage growth: a jump in the week new sources were connected means we started seeing more, not that the market grew.
New postings per week
Chart data
| Period | New postings per week |
|---|---|
| 2026-06-01 | 32 |
| 2026-06-08 | 29 |
| 2026-06-15 | 23 |
| 2026-06-22 | 57 |
| 2026-06-29 | 35 |
| 2026-07-06 | 51 |
| 2026-07-13 | 60 |
| 2026-07-20 | 44 |
| 2026-07-27 | 22 |
| 2026-08-03 | 25 |
| 2026-08-10 | 23 |
| 2026-08-17 | 26 |
| 2026-08-24 | 17 |
| 2026-08-31 | 23 |
| 2026-09-07 | 25 |
| 2026-09-14 | 24 |
| 2026-09-21 | 66 |
| 2026-09-28 | 71 |
| 2026-10-05 | 55 |
| 2026-10-12 | 146 |
| 2026-10-19 | 63 |
| 2026-10-26 | 83 |
| 2026-11-02 | 51 |
| 2026-11-09 | 62 |
Active sources per week
Sources over the period: 89. ▲ — a week with a large batch of new sources.
Chart data
| Period | Active sources |
|---|---|
| 2026-06-01 | 3 |
| 2026-06-08 | 5 |
| 2026-06-15 | 2 |
| 2026-06-22 | 13 |
| 2026-06-29 | 16 |
| 2026-07-06 | 13 |
| 2026-07-13 | 19 |
| 2026-07-20 | 22 |
| 2026-07-27 | 14 |
| 2026-08-03 | 14 |
| 2026-08-10 | 15 |
| 2026-08-17 | 12 |
| 2026-08-24 | 12 |
| 2026-08-31 | 12 |
| 2026-09-07 | 15 |
| 2026-09-14 | 11 |
| 2026-09-21 | 25 |
| 2026-09-28 | 23 |
| 2026-10-05 | 24 |
| 2026-10-12 | 23 |
| 2026-10-19 | 22 |
| 2026-10-26 | 24 |
| 2026-11-02 | 23 |
| 2026-11-09 | 29 |
New sources connected: Jun 22 +10 · Jun 29 +9 · Jul 6 +6 · Jul 13 +8 · Jul 20 +9 · all weeks (23) in the table
| Week | New sources | New postings |
|---|---|---|
| Jun 8 | +4 | 29 |
| Jun 15 | +1 | 23 |
| Jun 22 | +10 | 57 |
| Jun 29 | +9 | 35 |
| Jul 6 | +6 | 51 |
| Jul 13 | +8 | 60 |
| Jul 20 | +9 | 44 |
| Jul 27 | +2 | 22 |
| Aug 3 | +2 | 25 |
| Aug 10 | +2 | 23 |
| Aug 17 | +3 | 26 |
| Aug 24 | +1 | 17 |
| Aug 31 | +2 | 23 |
| Sep 7 | +1 | 25 |
| Sep 14 | +2 | 24 |
| Sep 21 | +4 | 66 |
| Sep 28 | +3 | 71 |
| Oct 5 | +2 | 55 |
| Oct 12 | +3 | 146 |
| Oct 19 | +3 | 63 |
| Oct 26 | +2 | 83 |
| Nov 2 | +2 | 51 |
| Nov 9 | +5 | 62 |
The current week is not over yet and is not shown: an incomplete week would look like a drop.
Week = posting first-seen date, all statuses; postings are selected by the same rule as this page's counter. Sources are distinct collection channels; their names are not published.
Chart data
| Week | New postings per week | Active sources |
|---|---|---|
| 2026-06-01 | 32 | 3 |
| 2026-06-08 | 29 | 5 |
| 2026-06-15 | 23 | 2 |
| 2026-06-22 | 57 | 13 |
| 2026-06-29 | 35 | 16 |
| 2026-07-06 | 51 | 13 |
| 2026-07-13 | 60 | 19 |
| 2026-07-20 | 44 | 22 |
| 2026-07-27 | 22 | 14 |
| 2026-08-03 | 25 | 14 |
| 2026-08-10 | 23 | 15 |
| 2026-08-17 | 26 | 12 |
| 2026-08-24 | 17 | 12 |
| 2026-08-31 | 23 | 12 |
| 2026-09-07 | 25 | 15 |
| 2026-09-14 | 24 | 11 |
| 2026-09-21 | 66 | 25 |
| 2026-09-28 | 71 | 23 |
| 2026-10-05 | 55 | 24 |
| 2026-10-12 | 146 | 23 |
| 2026-10-19 | 63 | 22 |
| 2026-10-26 | 83 | 24 |
| 2026-11-02 | 51 | 23 |
| 2026-11-09 | 62 | 29 |
Remote work over time
Share of .NET Fullstack postings offering fully remote work, per week.
Remote postings, %
Chart data
| Period | Remote |
|---|---|
| 2026-06-01 | 90.6 |
| 2026-06-08 | 92.9 |
| 2026-06-15 | 95.5 |
| 2026-06-22 | 48.1 |
| 2026-06-29 | 56.7 |
| 2026-07-06 | 83.3 |
| 2026-07-13 | 42.2 |
| 2026-07-20 | 52.9 |
| 2026-07-27 | 41.2 |
| 2026-08-03 | 21.1 |
| 2026-08-10 | 30.8 |
| 2026-08-17 | 44.4 |
| 2026-08-24 | 61.5 |
| 2026-08-31 | 50 |
| 2026-09-07 | 40 |
| 2026-09-14 | 53.3 |
| 2026-09-21 | 39.5 |
| 2026-09-28 | 44.1 |
| 2026-10-05 | 36.4 |
| 2026-10-12 | 57.1 |
| 2026-10-19 | 48.1 |
| 2026-10-26 | 33.3 |
| 2026-11-02 | 27.5 |
| 2026-11-09 | 32.6 |
The share is among postings that state a format (remote, hybrid, office). Weeks with fewer than 10 such postings are left blank.
Chart data
| Week | Remote |
|---|---|
| 2026-06-01 | 90.6 |
| 2026-06-08 | 92.9 |
| 2026-06-15 | 95.5 |
| 2026-06-22 | 48.1 |
| 2026-06-29 | 56.7 |
| 2026-07-06 | 83.3 |
| 2026-07-13 | 42.2 |
| 2026-07-20 | 52.9 |
| 2026-07-27 | 41.2 |
| 2026-08-03 | 21.1 |
| 2026-08-10 | 30.8 |
| 2026-08-17 | 44.4 |
| 2026-08-24 | 61.5 |
| 2026-08-31 | 50 |
| 2026-09-07 | 40 |
| 2026-09-14 | 53.3 |
| 2026-09-21 | 39.5 |
| 2026-09-28 | 44.1 |
| 2026-10-05 | 36.4 |
| 2026-10-12 | 57.1 |
| 2026-10-19 | 48.1 |
| 2026-10-26 | 33.3 |
| 2026-11-02 | 27.5 |
| 2026-11-09 | 32.6 |
Technologies over time
How the share of .NET Fullstack postings mentioning each of the top technologies changed.
Postings mentioning the technology, %
Chart data
| Period | C# | React | SQL |
|---|---|---|---|
| 2026-08-17 | 36.4 | 72.7 | 4.5 |
| 2026-08-24 | — | — | — |
| 2026-08-31 | 35 | 25 | 10 |
| 2026-09-07 | 20 | 65 | 10 |
| 2026-09-14 | — | — | — |
| 2026-09-21 | 56.9 | 56.9 | 25.5 |
| 2026-09-28 | 59 | 34.4 | 49.2 |
| 2026-10-05 | 65.2 | 50 | 45.7 |
| 2026-10-12 | 70 | 41.7 | 40 |
| 2026-10-19 | 62.3 | 39.6 | 47.2 |
| 2026-10-26 | 56.9 | 52.8 | 56.9 |
| 2026-11-02 | 52.3 | 56.8 | 47.7 |
| 2026-11-09 | 56.6 | 50.9 | 50.9 |
The series starts on Aug 17: there is no data before that.
Share among postings with a tagged stack; the series starts on Aug 10: earlier stack tags were assigned differently. Weeks with fewer than 20 tagged postings are left blank.
Chart data
| Week | C# | React | Angular | Azure | SQL |
|---|---|---|---|---|---|
| 2026-08-10 | — | — | — | — | — |
| 2026-08-17 | 36.4 | 72.7 | 22.7 | 9.1 | 4.5 |
| 2026-08-24 | — | — | — | — | — |
| 2026-08-31 | 35 | 25 | 25 | 10 | 10 |
| 2026-09-07 | 20 | 65 | 30 | 40 | 10 |
| 2026-09-14 | — | — | — | — | — |
| 2026-09-21 | 56.9 | 56.9 | 31.4 | 25.5 | 25.5 |
| 2026-09-28 | 59 | 34.4 | 34.4 | 16.4 | 49.2 |
| 2026-10-05 | 65.2 | 50 | 47.8 | 39.1 | 45.7 |
| 2026-10-12 | 70 | 41.7 | 42.5 | 30.8 | 40 |
| 2026-10-19 | 62.3 | 39.6 | 30.2 | 41.5 | 47.2 |
| 2026-10-26 | 56.9 | 52.8 | 38.9 | 47.2 | 56.9 |
| 2026-11-02 | 52.3 | 56.8 | 38.6 | 29.5 | 47.7 |
| 2026-11-09 | 56.6 | 50.9 | 41.5 | 35.8 | 50.9 |
Countries over time
How the share of .NET Fullstack postings in each of the top countries changed, per week.
Postings in the country, %
Chart data
| Period | Poland | USA | India |
|---|---|---|---|
| 2026-06-01 | 96.8 | 3.2 | 0 |
| 2026-06-08 | 89.3 | 0 | 3.6 |
| 2026-06-15 | 95.7 | 4.3 | 0 |
| 2026-06-22 | 84.9 | 3.8 | 1.9 |
| 2026-06-29 | 48.4 | 12.9 | 6.5 |
| 2026-07-06 | 16.1 | 3.2 | 6.5 |
| 2026-07-13 | 60 | 0 | 12 |
| 2026-07-20 | 31.6 | 7.9 | 10.5 |
| 2026-07-27 | — | — | — |
| 2026-08-03 | 27.3 | 18.2 | 9.1 |
| 2026-08-10 | 0 | 10 | 10 |
| 2026-08-17 | — | — | — |
| 2026-08-24 | — | — | — |
| 2026-08-31 | — | — | — |
| 2026-09-07 | 5 | 10 | 15 |
| 2026-09-14 | 14.3 | 19 | 9.5 |
| 2026-09-21 | 21.2 | 23.1 | 15.4 |
| 2026-09-28 | 24.6 | 17.5 | 8.8 |
| 2026-10-05 | 37.5 | 14.6 | 6.2 |
| 2026-10-12 | 21.4 | 17.5 | 11.7 |
| 2026-10-19 | 35.8 | 9.4 | 9.4 |
| 2026-10-26 | 29.7 | 14.9 | 12.2 |
| 2026-11-02 | 25 | 12.5 | 17.5 |
| 2026-11-09 | 21.1 | 17.5 | 14 |
Share among postings with a known country; the chart shows the five countries with the most postings over six months. Weeks with fewer than 20 postings with a known country are left blank. A rising share can mean a newly connected source in that country rather than market growth.
Chart data
| Week | Poland | USA | India | UK | Australia |
|---|---|---|---|---|---|
| 2026-06-01 | 96.8 | 3.2 | 0 | 0 | 0 |
| 2026-06-08 | 89.3 | 0 | 3.6 | 0 | 0 |
| 2026-06-15 | 95.7 | 4.3 | 0 | 0 | 0 |
| 2026-06-22 | 84.9 | 3.8 | 1.9 | 0 | 0 |
| 2026-06-29 | 48.4 | 12.9 | 6.5 | 0 | 0 |
| 2026-07-06 | 16.1 | 3.2 | 6.5 | 0 | 6.5 |
| 2026-07-13 | 60 | 0 | 12 | 4 | 6 |
| 2026-07-20 | 31.6 | 7.9 | 10.5 | 23.7 | 5.3 |
| 2026-07-27 | — | — | — | — | — |
| 2026-08-03 | 27.3 | 18.2 | 9.1 | 18.2 | 4.5 |
| 2026-08-10 | 0 | 10 | 10 | 25 | 30 |
| 2026-08-17 | — | — | — | — | — |
| 2026-08-24 | — | — | — | — | — |
| 2026-08-31 | — | — | — | — | — |
| 2026-09-07 | 5 | 10 | 15 | 25 | 25 |
| 2026-09-14 | 14.3 | 19 | 9.5 | 19 | 14.3 |
| 2026-09-21 | 21.2 | 23.1 | 15.4 | 9.6 | 1.9 |
| 2026-09-28 | 24.6 | 17.5 | 8.8 | 7 | 1.8 |
| 2026-10-05 | 37.5 | 14.6 | 6.2 | 10.4 | 6.2 |
| 2026-10-12 | 21.4 | 17.5 | 11.7 | 1 | 0 |
| 2026-10-19 | 35.8 | 9.4 | 9.4 | 5.7 | 1.9 |
| 2026-10-26 | 29.7 | 14.9 | 12.2 | 9.5 | 5.4 |
| 2026-11-02 | 25 | 12.5 | 17.5 | 5 | 7.5 |
| 2026-11-09 | 21.1 | 17.5 | 14 | 3.5 | 8.8 |
Clean market: hiring index
The same 7,505 employer job boards; the posting count comes from the board itself. Connecting new sources does not move this index — it shows the market, not our coverage. This is the whole panel market, not just .NET Fullstack.
Hiring index, Oct 16 = 100
Chart data
| Period | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
Chain index: each day compares only boards polled on both that day and the previous one; outliers and platform-wide polling outages are excluded. Days with no comparable pairs are left blank.
Chart data
| Day | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
How many open .NET Fullstack jobs there are and how many matching specialists Zorky observes.
Demand and observed supply
Chart data
| Metric | Value |
|---|---|
| Open demand | 280 |
| Open demand | 280 |
| Observed supply | — not published |
.NET Fullstack — an in-demand, enterprise-oriented stack with steady demand. Drivers 2026: strong positions of .NET in banks, corporate and industrial software; Blazor (especially the unified .NET 8 model) made «fullstack in one language» a mass option; import substitution in CIS shifts the cloud from Azure to local clouds and on-prem, but demand for .NET itself holds.
⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown
How salaries in .NET Fullstack jobs are distributed, in US dollars per month.
Salary distribution
Chart data
| Metric | Value |
|---|---|
| <$1k | 0 |
| $1–2k | 0 |
| $2–3k | 2 |
| $3–4k | 5 |
| $4–5k | 1 |
| $5–6k | 8 |
| $6–7k | 4 |
| $7–8k | 3 |
| $8–9k | 3 |
| $9–10k | 5 |
| $10–12k | 4 |
| $12–15k | 1 |
| $15–20k | 0 |
| $20k+ | 0 |
- usable for the calculation: 36 (12.9%)
- stated but not converted to USD/month: 28 (10%)
- not stated: 216 (77.1%)
One in ten postings offers under $3,500, one in ten over $10,507. Half of the postings offer between $5,000 and $9,000. Sample: 36.
Chart data
| Metric | Lower bound | Upper bound | Count |
|---|---|---|---|
| <$1k | 0 | 1,000 | 0 |
| $1–2k | 1,000 | 2,000 | 0 |
| $2–3k | 2,000 | 3,000 | 2 |
| $3–4k | 3,000 | 4,000 | 5 |
| $4–5k | 4,000 | 5,000 | 1 |
| $5–6k | 5,000 | 6,000 | 8 |
| $6–7k | 6,000 | 7,000 | 4 |
| $7–8k | 7,000 | 8,000 | 3 |
| $8–9k | 8,000 | 9,000 | 3 |
| $9–10k | 9,000 | 10,000 | 5 |
| $10–12k | 10,000 | 12,000 | 4 |
| $12–15k | 12,000 | 15,000 | 1 |
| $15–20k | 15,000 | 20,000 | 0 |
| $20k+ | 20,000 | — | 0 |
Which countries have the most open .NET Fullstack jobs.
Demand geography
| country | jobs | share |
|---|---|---|
| Poland | 74 | 30.8% |
| United States | 35 | 14.6% |
| India | 22 | 9.2% |
| United Kingdom | 12 | 5% |
| Mexico | 8 | 3.3% |
| France | 8 | 3.3% |
| Australia | 7 | 2.9% |
| Brazil | 7 | 2.9% |
| Russia | 6 | 2.5% |
| Romania | 5 | 2.1% |
| Other countries | 56 | 23.3% |
Leader by .NET Fullstack job count — Poland (74 positions). Demand concentrates in the enterprise segment — banks / fintech, corporate and industrial software, public sector, cybersecurity. In Eastern Europe (Poland and others) the .NET market is traditionally large. International companies hire Russian-speaking Senior .NET Fullstack on full-remote.
⚠ job counts only: salary by country is not published
Chart data
| Country | Jobs |
|---|---|
| PL | 74 |
| US | 35 |
| IN | 22 |
| GB | 12 |
| MX | 8 |
| FR | 8 |
| AU | 7 |
| BR | 7 |
| RU | 6 |
| RO | 5 |
Which technologies are most often required in the same job as .NET Fullstack.
Used together with
Share — how many of the 280 jobs in the .NET Fullstack market mention this technology. Ordered by job count, not by “strength of association”. Umbrella terms like cloud are not a specific cloud (AWS, Azure).
Top .NET Fullstack stack 2026: C# (must — 12 / 13), .NET 8 / 9 (LTS — .NET 8), ASP.NET Core, Entity Framework Core; frontend — Blazor (Server / WebAssembly / unified .NET 8 model) or React / Angular + TypeScript; SignalR (real-time), MS SQL Server or PostgreSQL, Redis, REST / gRPC / GraphQL, xUnit / NUnit, Docker + Kubernetes, CI/CD; cloud — Azure or local clouds and on-prem (import substitution in CIS).
Common combinations: ASP.NET Core + Blazor (everything in C#), ASP.NET Core + React + TypeScript, ASP.NET Core + Angular, C# + EF Core + MS SQL Server, .NET + Docker + Azure DevOps. Learning roadmap: C# as a language → ASP.NET Core → EF Core → databases and SQL → frontend (Blazor or React / Angular + TypeScript) → HTML / CSS → testing → Git / Docker / CI/CD → end-to-end pet project (API + DB + frontend + deploy).
Chart data
| Name | Count |
|---|---|
| c# | 171 |
| react | 130 |
| angular | 110 |
| azure | 106 |
| sql | 97 |
| cloud | 69 |
| javascript | 56 |
| typescript | 44 |
| docker | 37 |
| aws | 31 |
| kubernetes | 25 |
| .net | 21 |
How many .NET Fullstack jobs there are at each level, from junior to principal.
Demand by grade
| grade | jobs |
|---|---|
| senior | 128 |
| middle | 24 |
| lead | 13 |
| principal | 12 |
| junior | 1 |
Career flow: .NET Backend or Frontend → .NET Fullstack Middle → Senior → Tech Lead / Solution Architect. In the .NET world the Senior → architect path is especially developed — see /research/architect.
⚠ demand side only: the grade of the observed pool is unknown for most of it
Chart data
| Level | Count |
|---|---|
| senior | 128 |
| middle | 24 |
| lead | 13 |
| principal | 12 |
| junior | 1 |
Who hires the most for .NET Fullstack and how concentrated demand is among the largest companies.
Employers
Demand is spread across 209 employers. The largest accounts for 2.7%, the top ten for 13.7%; the remaining 86.3% is long tail.
| share | value |
|---|---|
| top-1 | 2.7% |
| top-3 | 5.7% |
| top-10 | 13.7% |
| long tail | 86.3% |
⚠ names are not shown: staffing agencies and end employers are not yet told apart by the classifier
Which company sites and job boards Zorky collects .NET Fullstack jobs from.
Where Zorky sees this market
Observed across 50 sources; the largest accounts for 11.1% — this market does not rest on a single channel.
.NET Fullstack vacancies: hh.ru («.NET developer» / «C# fullstack» / «ASP.NET Core developer» / «Blazor developer»), Habr Career, getmatch, Djinni, LinkedIn (including the large .NET market of Eastern Europe), Telegram (.NET communities and vacancy channels). The real market is wider than precise search — many fullstack roles pass simply as «.NET developer» with frontend responsibilities.
Chart data
| Class | Name | English name | Count | Share |
|---|---|---|---|---|
| ats | ATS и карьерные сайты | ATS & career sites | 147 | 0.525 |
| board | джоб-борды и агрегаторы | job boards & aggregators | 122 | 0.4357 |
| telegram | Telegram | Telegram | 11 | 0.0393 |
The newest .NET Fullstack jobs from company career sites.
Recent openings
- Fullstack .Net/C# · SE
- Senior Full Stack .NET Developer
- Senior .NET Fullstackutvecklare · SE
- Full-stack .NET Developer (Middle+/Senior) · KZ
- Lập trình viên (.NET Full-stack Developer) · PL
- […] - Middle/Senior Full-Stack Developer - .Net/React · IN
- Full Stack Developer – Platform & Framework – .NET / React · PL
- Senior Fullstack .NET/Vuejs Software Engineer
Latest open .NET Fullstack jobs — most recent 10 positions with adequate description quality. NB: part of fullstack roles passes simply as «.NET developer» — full list in our CRM or via the «see all» link below.
Adjacent markets
.NET Fullstack connects backend development (.NET Backend — cross-link to /research/backend/dotnet) and frontend (Blazor or React / Angular — see /research/frontend). Natural progression — into Solution Architect (/research/architect), the Senior → architect path in the .NET world is especially developed. Comparison of fullstack specializations — in the SiblingSubnichesChart above.
⚠ adjacent markets for comparison are not defined yet
How this is measured
- Vacancy
- an open job that cleared the quality gate and lists at least two technologies
- Observed candidate
- a candidate whose stack contains this technology; an aggregate — not a single record leaves the perimeter
- Matchable candidate
- not counted yet
- Window
- jobs open at the moment the snapshot was built
About the data
- Some breakdowns are hidden: their data coverage is not yet sufficient.
- Statistics are shown only where the sample clears a quality gate.
- A missing block does not mean a value of zero.
Breakdowns currently hidden: 8.
Direction: Fullstack
Frequently asked questions
The most common questions about .NET Fullstack: pay, grades, stack, what .NET Fullstack is (Blazor vs React frontend), what Blazor is and whether to learn it, differences from .NET Backend, remote (enterprise + Azure import-substitution nuance), companies, how to start, Senior skills. Answers recompute automatically.
What stack is most often required from .NET Fullstack?
Top 5: sql, react, c#, angular, azure. Backend: C# (must — versions 12 / 13), .NET 8 / 9 (LTS — .NET 8), ASP.NET Core (web APIs and applications), Entity Framework Core (ORM) or Dapper, patterns (DI, middleware, Minimal API or controllers), REST / gRPC / GraphQL, background tasks. Frontend — depends on the variant of vacancy: either Blazor (Server / WebAssembly / unified .NET 8 model), or React / Angular + TypeScript for SPA; HTML / CSS in any case. Real-time: SignalR. DB: MS SQL Server (the classic for .NET) or PostgreSQL (growing, including due to import substitution), Redis. Tests: xUnit / NUnit, for the front — appropriate tools. Infrastructure: Docker + Kubernetes, CI/CD, Git. Cloud: Azure — natural for .NET, but in CIS often replaced with local clouds (Yandex Cloud, VK Cloud) and on-prem due to import substitution. Understanding the architecture of the application as a whole (rather than only your half of the stack) — key for the fullstack role.
What is .NET Fullstack — Blazor or React frontend?
This is the main fork of the specialization, and behind «.NET Fullstack» two different stacks hide in vacancies. Variant 1 — Blazor («pure» .NET Fullstack): both backend and frontend are written in C#. Blazor is Microsoft's component UI framework; the interface is C# components, JavaScript is almost not needed. Plus — one language and one ecosystem for the whole product, you can reuse code and models between back and front, no separate frontend specialist needed. This is the «real» fullstack-in-one-language. Variant 2 — .NET + SPA: backend on ASP.NET Core, and frontend — a separate SPA application on React, Angular or Vue with TypeScript. Here .NET Fullstack is a person who commands both the C# backend and the JavaScript frontend. This is the classic split, very widespread, especially at product companies and where a rich complex UI is needed. What to choose: both variants are in demand. Blazor — if you want to stay in one language and ecosystem (convenient for enterprise and small teams). .NET + React / Angular — gives a more universal frontend skill (React on its own — a huge market). Many strong .NET Fullstack engineers command both approaches. The main thing when applying — read the vacancy: which exact frontend is specified.
What is Blazor and is it worth learning in 2026?
Blazor — Microsoft's framework for building user interfaces in C# instead of JavaScript. Components are written in C# and Razor markup. Blazor has several work models: Blazor Server (UI runs on the server, updates fly to the browser via SignalR — little code in the browser, but a constant connection is needed), Blazor WebAssembly (the application in C# compiles to WebAssembly and works right in the browser, like a full-fledged SPA), and in .NET 8 Microsoft combined the approaches — now you can mix server rendering, interactive server and WebAssembly components in one application and switch rendering modes (this is called «Blazor United»). What for: Blazor allows a .NET developer to do frontend without going into the JavaScript ecosystem — one language, one model, code reuse. Worth learning: yes, if you're in the .NET world — Blazor is mature, actively developed by Microsoft, increasingly occurs in vacancies (especially in enterprise and internal corporate applications), this is a strong competitive advantage for the .NET fullstack role. Important caveat: Blazor hasn't «killed» the JavaScript frontend — React / Angular still dominate the market overall, and for complex public products React/Angular are more often picked. The optimal 2026 strategy for .NET Fullstack — know Blazor AND command one JS framework (React or Angular): this covers both types of vacancies.
How does .NET Fullstack differ from regular .NET Backend?
.NET Backend (see /research/backend/dotnet) — specialization on the server side: C#, ASP.NET Core, EF Core, databases, APIs, business logic, backend performance, service architecture. A backend developer usually doesn't touch the frontend. .NET Fullstack — responsible for the application as a whole: both the server side in C# and the user interface (Blazor or React / Angular). Pros of the fullstack role: you see the product as a whole, can take a feature from the database to the screen yourself, irreplaceable in small teams and startups, wider responsibility. Cons / nuances: harder to hold both sides of the stack equally deeply; on large products with a rich complex UI separate deep frontend specialists are more often needed. .NET Fullstack salary — on par with or slightly above .NET Backend of the same grade (thanks to breadth), but the highest salaries in the .NET world are with Seniors who have deep backend / architectural expertise. What to choose: Fullstack — if you like owning the product as a whole and working in product teams; pure Backend — if you want depth in server development and movement into architecture / high-load. Many start with Backend and pick up the frontend, becoming Fullstack.
What share of jobs are remote?
Among jobs with a stated work format, 33% are remote. Jobs without a stated format are excluded from the denominator; hybrid work is not counted as remote.
How to start a .NET Fullstack career in 2026?
Roadmap: 1) C# as a language — syntax, OOP, async / await, LINQ, generics, exception handling; «C# in Depth» (Jon Skeet), official Microsoft Learn documentation (excellent and free). 2) .NET and ASP.NET Core — platform structure, web APIs, dependency injection, middleware, configuration, authentication. 3) Entity Framework Core — DB work, migrations, LINQ-to-SQL queries, fighting N+1. 4) Databases — MS SQL Server and / or PostgreSQL, SQL thoroughly. 5) Frontend — choose direction: Blazor (stay in C# — Microsoft Learn, official tutorials) or React / Angular + TypeScript (universal JS frontend skill, larger market). Optimally, over time master both Blazor and one JS framework. 6) HTML / CSS — base in any case. 7) Testing — xUnit / NUnit. 8) Infrastructure — Git, Docker, basics of CI/CD. 9) End-to-end pet project: application on ASP.NET Core (API + EF Core + DB) + frontend (Blazor or React) + authentication + Docker + deploy. Advice: start with backend (.NET Backend) and gradually pick up the frontend, moving toward Fullstack.
How many open jobs are in this sample?
The published sample contains 280 open jobs after merging reposts. This is the same count shown in the main indicator. The geography section describes the sample coverage; this is not an estimate of the entire market.
What skills does a Senior .NET Fullstack need?
Senior .NET Fullstack owns the application as a whole — from database to interface. C# and .NET deeply: advanced C# (async / await and its pitfalls, LINQ, generics, span / memory, GC specifics), .NET internals, performance. Backend: ASP.NET Core at expert level (application architecture, DI, middleware, authentication / authorization, API design — REST / gRPC / GraphQL), EF Core (query optimization, migrations, fighting N+1, when Dapper / raw SQL is needed), patterns and clean architecture, organization of business logic. Frontend: confident command of either Blazor (Server / WebAssembly / .NET 8 rendering model, state management, performance), or React / Angular + TypeScript at production level; HTML / CSS, understanding of UX. Databases: MS SQL Server and / or PostgreSQL — advanced SQL, indexes, query plans, schema design. Architecture: design of the application as a whole, conscious choice «monolith vs services», caching (Redis), real-time (SignalR), scaling. Performance: profiling and optimization of both backend and frontend. Testing: mature strategy (xUnit / NUnit, integration tests). Infrastructure and DevOps: Docker, Kubernetes, CI/CD, clouds (Azure and / or local clouds and on-prem — relevant for CIS due to import substitution). Soft: code review, mentoring, communication with product, task estimation. English — for the international market and Microsoft documentation. In the .NET world the Senior → Solution Architect path is especially developed — a Senior .NET Fullstack with architectural skills easily moves into architecture (see /research/architect).
Leave a request
Describe the task and leave a contact — the request goes to our CRM and we reply at the contact you provide.