A plain-English explainer for every Microsoft technology, language, and tool that appears on a .NET full-stack developer's résumé — written for recruiters, not engineers.
The big picture before diving into individual technologies
Every Microsoft full-stack app flows through these four layers. Each tab explores one area in depth.
The core of the Microsoft Stack is C# (the primary programming language), .NET (the framework that runs C# code), ASP.NET Core (for web APIs and websites), and Microsoft Azure (for cloud hosting). These tools are enterprise-grade, backed by Microsoft's full support, and used by hundreds of Fortune 500 companies. The Microsoft Stack was historically Windows-only but is now fully cross-platform — it runs on Windows, Mac, and Linux servers alike.
What users see and interact with — Microsoft's web UI toolkit
C# was created by Microsoft in 2000 and has evolved dramatically. C# 12 / .NET 8+ is the current standard. It is strongly typed (catches errors early), object-oriented, and backed by the entire .NET ecosystem. Seeing "C#" on a résumé is the Microsoft equivalent of seeing "Java" — it's the bedrock skill on which everything else is built.
Blazor comes in two flavors: Blazor Server (logic runs on the server, updates pushed to the browser) and Blazor WebAssembly (C# code runs directly in the browser, no server needed for UI). .NET 8 unified these as Blazor United. Blazor is increasingly common in enterprise .NET shops and signals a Microsoft-first team. A candidate listing "Blazor" is rare and very valuable for Microsoft-stack roles.
Razor is the template language mixing C# and HTML. MVC (Model-View-Controller) is an organizing pattern: Model=data, View=what the user sees, Controller=logic connecting them. Most legacy and enterprise .NET web apps use MVC. A candidate listing "ASP.NET MVC" likely has experience with large, established enterprise systems. Razor Pages is a simpler, more modern alternative for smaller apps.
TypeScript is the standard for professional JavaScript development and is required for React and Angular front-ends. Many .NET teams build the back-end in C#/ASP.NET Core and the front-end in React/TypeScript. Angular (Google's framework, but extremely popular in enterprise .NET shops) is entirely TypeScript-based. A full-stack .NET developer who also knows TypeScript + React or Angular is the most versatile hire.
SignalR is a Microsoft library built on top of WebSockets. It's used for chat apps, real-time dashboards, live notifications, and multiplayer features. Seeing "SignalR" on a résumé indicates experience with real-time, event-driven application features — a meaningful specialization that signals experience with complex, interactive .NET web apps.
The server-side Microsoft tools that process requests, enforce business rules, and serve data
There is important version history here: the old .NET Framework (Windows-only, versions 1–4.8) vs. the modern .NET (cross-platform, versions 5, 6, 7, 8, 9+). .NET 8 is the current Long-Term Support (LTS) version and what most teams target today. If a résumé says ".NET Framework 4.x," the candidate may only have legacy experience. ".NET 6+", ".NET 8", or ".NET Core" signals current, modern expertise.
ASP.NET Core is the #1 most important back-end skill to identify on a Microsoft-stack résumé. It powers REST APIs, web pages (via MVC/Razor), and real-time features (via SignalR). "Minimal APIs" is a newer, lightweight way to build APIs with ASP.NET Core — seeing it on a résumé signals familiarity with modern .NET development patterns. ASP.NET Core is consistently ranked among the fastest web frameworks in the world.
Web API development is the most common use of ASP.NET Core in enterprise settings. Candidates should understand REST conventions, HTTP verbs (GET/POST/PUT/DELETE), JSON data formats, and proper response codes. Also look for Swagger/OpenAPI (auto-generates API documentation), JWT authentication, and versioning strategies. "Minimal APIs" (introduced in .NET 6) is a lighter-weight style growing in popularity.
Security is non-negotiable in enterprise applications. Look for: ASP.NET Core Identity (user management), JWT tokens (secure API authentication), OAuth2/OpenID Connect (single sign-on standards), and Azure AD / Microsoft Entra ID (enterprise identity). Role-based access control (RBAC) — restricting who can access what — is a critical enterprise security concept. A developer who can't implement authentication is not production-ready.
NuGet is used in every single .NET project — its absence from a résumé is not unusual (it's assumed), but a candidate who doesn't know what it is raises concern. Popular NuGet packages include Newtonsoft.Json (JSON processing), Serilog (logging), AutoMapper (object mapping), and MediatR (messaging pattern). NuGet.org is the central package repository with over 300,000 packages.
LINQ is a core C# skill that every competent .NET developer must know. It's used constantly when working with data — filtering lists, sorting results, transforming collections. When integrated with Entity Framework Core, LINQ queries are automatically translated to SQL. Inability to write basic LINQ queries is a significant gap in any mid-to-senior .NET candidate.
How Microsoft-stack applications store, retrieve, and manage data
SQL Server is the most common database in the Microsoft stack. The query language is T-SQL (Transact-SQL) — a Microsoft extension of standard SQL with extra features. SQL Server comes in free (Express, Developer) and paid (Standard, Enterprise) editions. "Azure SQL Database" is the cloud-hosted version. Key skills: writing T-SQL queries, stored procedures, indexing, and performance tuning. SQL Server Management Studio (SSMS) is the tool for managing it.
Entity Framework Core is the standard data access technology in the .NET ecosystem. "Code-First" approach (the most common): developers define data models in C#, and EF Core generates the database tables. "Database-First": existing database generates the C# models. Migrations are versioned database schema changes — critical for safe production deployments. Dapper is a lighter-weight alternative used when maximum SQL performance is needed.
Azure SQL Database is the most common choice for cloud-hosted Microsoft applications. Cosmos DB is chosen when data is global, unstructured, or requires extreme speed at massive scale. "Managed database" means Microsoft handles patching, backups, and high availability — developers just use the database. Azure SQL skills are increasingly expected alongside on-premises SQL Server knowledge for mid/senior candidates.
SSMS is Windows-only and has been the standard database tool for SQL Server for 20+ years. Azure Data Studio is newer, runs on all platforms, and is increasingly preferred. Both are free. A candidate claiming SQL Server expertise should be completely fluent in at least one of these tools.
How Microsoft-stack applications are built, tested, deployed, and hosted in the cloud
Visual Studio is available in three tiers: Community (free for individuals), Professional (paid), and Enterprise (paid, adds team tools). VS 2022 is the current version. VS Code has become the world's most popular code editor (used by 73%+ of developers). It's highly extensible with thousands of plugins. A .NET developer should know Visual Studio; knowing VS Code is a bonus showing cross-language versatility.
Key Azure DevOps components: Repos (Git code hosting), Boards (Agile sprint planning), Pipelines (automated build + deploy), Artifacts (package hosting), and Test Plans (QA management). Pipelines is the most critical skill — it automates the process of building, testing, and deploying code. A candidate listing "Azure DevOps Pipelines" demonstrates professional-grade CI/CD experience in the Microsoft ecosystem.
Key Azure services for .NET developers: App Service (hosts web apps — the most common), Azure Functions (runs small code snippets on-demand — serverless), Azure SQL Database (managed SQL Server), Azure Blob Storage (file/image storage), Azure Service Bus (messaging), and Azure Container Instances/AKS (Docker/Kubernetes hosting). Microsoft certifications (AZ-900, AZ-204) on a résumé are strong positive signals.
Docker is becoming standard at mid/senior level in Microsoft-stack roles. AKS is an advanced skill for DevOps-oriented roles or microservices architectures. Azure has excellent built-in tooling for containerized .NET apps, including Azure Container Registry (storing Docker images) and Azure Container Apps (a simpler alternative to AKS for smaller deployments). Container experience signals modern, cloud-native development practices.
Professional .NET development teams test rigorously. xUnit is the most popular for modern .NET projects. Moq is a companion library for creating "mock" (fake) objects to simulate external dependencies in tests. A candidate who mentions test-driven development (TDD), code coverage metrics, or integration testing signals engineering maturity. The absence of any testing knowledge is a red flag for mid/senior roles.
Git and GitHub are non-negotiable skills at every level. GitHub Actions is the modern CI/CD choice for teams that prefer GitHub over Azure DevOps Pipelines. Both GitHub Actions and Azure DevOps Pipelines accomplish the same goal (automated deployment); knowing one makes learning the other easy. GitHub Copilot (AI code assistant) is increasingly mentioned on résumés and signals AI-augmented productivity.
Microsoft technologies for desktop, mobile, games, services, and enterprise integration
WPF and WinForms are the two main frameworks for Windows-only desktop applications. WPF uses XAML (a layout language, similar to HTML but for desktop UIs) and supports animations, data binding, and complex visuals. WinForms is simpler and faster to build. Many internal enterprise tools, point-of-sale systems, and industrial applications are built with these. They will not be replaced anytime soon in corporate environments.
.NET MAUI replaced Xamarin Forms in 2022. It's the modern choice for cross-platform mobile/desktop development in the Microsoft ecosystem. Seeing ".NET MAUI" on a résumé signals up-to-date knowledge; "Xamarin" indicates experience with the predecessor (still valuable but being phased out). MAUI apps can also use Blazor for the UI layer, creating "Blazor Hybrid" apps that share web code with mobile apps.
Azure Functions are ideal for background jobs, scheduled tasks, event processing, and lightweight APIs. They're a cost-effective way to run periodic or triggered work. Seeing "Azure Functions" or "serverless" on a résumé indicates experience with event-driven architecture, cloud-native thinking, and Microsoft's serverless platform. Common triggers: HTTP, Timer, Queue, Blob Storage, and Service Bus.
Worker Services and Windows Services are common in enterprise .NET environments for integration jobs, data pipelines, scheduled tasks, and monitoring agents. They're often paired with message queues (Azure Service Bus, RabbitMQ) to process work items asynchronously. A candidate listing "Windows Services" likely has enterprise integration experience; ".NET Worker Services" signals more modern cloud-native knowledge.
Power Platform skills are distinct from traditional software development. Power Apps/Power Automate developers are often non-programmers (business analysts, operations staff). Power BI analysts focus on data visualization, not application development. These are important to distinguish from C#/.NET developers — they're complementary, not interchangeable. A traditional developer listing Power BI skills indicates data reporting experience on top of their coding background.
Jargon you'll encounter on résumés and job descriptions — decoded
| Term / Acronym | Plain-English Meaning | When You See It |
|---|---|---|
| .NET / dotnet | Microsoft's developer platform — the engine that runs C# code on any OS | Every Microsoft-stack résumé |
| CLR | Common Language Runtime — the part of .NET that actually executes your code | Deep .NET internals discussions |
| ASP.NET Core | Microsoft's web framework for building websites, APIs, and web services | Every .NET web developer résumé |
| MVC | Model-View-Controller — an organizing pattern for web app code (separate data, display, and logic) | ASP.NET web app experience |
| ORM | Object-Relational Mapper — auto-translation between C# code and database tables (Entity Framework) | Data layer experience |
| EF Core | Entity Framework Core — Microsoft's official ORM for database access in .NET | Database + .NET experience |
| LINQ | Language Integrated Query — C#'s built-in syntax for querying and filtering data collections | Core C# proficiency |
| T-SQL | Transact-SQL — Microsoft's version of the SQL database language with extra features | SQL Server experience |
| Blazor | Microsoft's web UI framework — builds interactive web pages using C# instead of JavaScript | Modern Microsoft front-end |
| XAML | XML-based layout language for WPF/MAUI desktop and mobile UIs — like HTML for desktop apps | Desktop or mobile .NET apps |
| NuGet | Microsoft's package manager — downloads and installs pre-built .NET libraries | Assumed in all .NET projects |
| IIS | Internet Information Services — Microsoft's built-in Windows web server (hosts ASP.NET apps) | On-premises Windows hosting |
| Azure AD / Entra ID | Microsoft's enterprise identity service — manages employee logins across company apps | Enterprise security experience |
| JWT | JSON Web Token — a secure digital "badge" used for API authentication without re-sending passwords | API security / ASP.NET Identity |
| SignalR | Microsoft's real-time communications library — server pushes live updates to the browser | Chat, live dashboards, notifications |
| Dependency Injection | A design pattern built into ASP.NET Core — components receive their dependencies automatically rather than creating them manually | ASP.NET Core experience |
| Middleware | Code that runs on every web request in sequence — handles logging, authentication, compression, etc. | ASP.NET Core architecture |
| gRPC | A high-performance alternative to REST APIs for service-to-service communication — faster than JSON over HTTP | Microservices, high-performance back-ends |
| Dapper | A lightweight data access library — like EF Core but you write the SQL yourself, for maximum speed | Performance-critical database work |
| Serilog | A popular logging library for .NET — records app events, errors, and diagnostics in structured formats | Production-ready .NET applications |
45+ qualifying questions organized by domain — for both web and non-web Microsoft roles
📌 How to use this section
You don't need to understand the technology to evaluate answers. Listen for specificity (real tool names and versions), tradeoff thinking (they know pros and cons), and depth under follow-up (the story holds up). Each question shows Strong ✓, Average ≈, and Weak ✗ answer patterns.
🚩 Universal Red Flags — Microsoft Stack