Roadmap › 7. Interview Questions & Career › Step 57

.NET Full Stack Developer Interview — End to End

How .NET full stack interviews run, the end-to-end request flow (Angular/React → ASP.NET Core → EF Core → SQL Server), authentication, a feature built across every layer, performance, deployment, architecture and system design — with the questions interviewers ask most.

What it is & where it is used

A .NET full stack developer builds a feature through every layer: the UI (Angular or React with TypeScript), the API (ASP.NET Core Web API in C#), data access (EF Core or Dapper), the database (SQL Server), and usually the delivery path (Git, CI/CD, Docker, Azure).

Interviewers for this role do not want five separate specialists. They test whether you can connect the layers:

Layer	Typical stack	What they check
UI	Angular / React, TypeScript, HTML, CSS	Components, state, forms, calling APIs, routing, auth guards
API	ASP.NET Core Web API, C#	REST design, DI, middleware, validation, error handling, auth
Data access	EF Core, Dapper, ADO.NET	LINQ, tracking, migrations, N+1, transactions
Database	SQL Server	Joins, indexes, stored procedures, execution plans, deadlocks
Delivery	Git, Azure DevOps / GitHub Actions, Docker, Azure	Branching, pipelines, config, secrets, monitoring
Design	SOLID, patterns, clean architecture	Layering, testability, trade-offs

This course is the glue: each lesson follows one concern across the whole stack. The deep dives live in the individual courses (C#, Web API, EF Core, SQL Server, Angular, React …). Use the .NET Full Stack Developer question bank (Interview Questions menu) to drill every question from all of those courses in one place.

Versions & history

The stack most job descriptions ask for in 2026:

Part	Current version	Notes
.NET	.NET 10 (LTS, Nov 2025)	.NET 8 (LTS) still very common in production; .NET 9 is STS
C#	C# 14 (with .NET 10)	Extension members, `field` keyword, null-conditional assignment
ASP.NET Core	10	Minimal APIs and controllers; built-in OpenAPI document generation
EF Core	10	LeftJoin/RightJoin LINQ operators, named query filters, complex types
SQL Server	2022 / 2025	2025 adds vector data type, JSON type and regex functions
Angular	20 / 21	Standalone components, signals, new control flow (`@if`, `@for`), zoneless
React	19.x	Actions, `use`, Server Components (via frameworks such as Next.js)
TypeScript	5.x	TypeScript 7 (native Go compiler) in preview
Node.js (tooling)	22 / 24 LTS	Needed for Angular CLI, Vite, npm

Interview tip: say which version you used in your last project and one feature from it you actually used ("we moved to .NET 8 and used IExceptionHandler for global errors").

Lifecycle

How a full stack feature moves from ticket to production:

Requirement — user story with acceptance criteria (Jira / Azure Boards).
Design — API contract (endpoint, request/response DTOs, status codes), DB change (table, index, migration), UI screens.
Database — migration script or EF Core migration; seed data; indexes for the new queries.
API — DTOs, validation, service/business logic, repository or DbContext query, controller/endpoint, unit tests.
UI — service that calls the API, component, form with validation, routing, error and loading states.
Integration — CORS, auth token flow, end-to-end test (Playwright/Cypress).
Review & CI — pull request, code review, pipeline runs build + tests + static analysis.
Deploy — CD pipeline to dev → QA → UAT → production; config per environment; feature flags if needed.
Operate — logs (Serilog / Application Insights), metrics, alerts; fix and iterate.

Tools used to develop

IDE: Visual Studio 2022/2026, VS Code, JetBrains Rider.
API testing: Swagger UI / Scalar, Postman, .http files in Visual Studio, curl.
Database: SQL Server Management Studio (SSMS), Azure Data Studio (retired 2026 — use VS Code MSSQL extension), SQL Profiler / Extended Events.
Frontend: Angular CLI, Vite, Chrome DevTools, Redux DevTools, Angular DevTools, React DevTools.
Testing: xUnit / NUnit, Moq / NSubstitute, FluentAssertions, Jasmine/Karma or Jest/Vitest, Playwright.
Delivery: Git, GitHub / Azure Repos, Azure DevOps Pipelines / GitHub Actions, Docker Desktop, Azure Portal, Azure CLI.
Monitoring: Application Insights, Serilog + Seq, Grafana.