2. "Explain your project architecture" — the end-to-end answer

This is asked in almost every round. Prepare a 2-minute answer using this skeleton:

1. Business — "An order-management portal for distributors; ~300 internal users, ~20k orders/day."
2. Frontend — "Angular 17 SPA with standalone components, reactive forms, an HTTP interceptor that adds the JWT and handles 401."
3. API — "ASP.NET Core 8 Web API, layered: Controllers → Services → Repositories (EF Core). FluentValidation for input, global exception middleware returning ProblemDetails, Serilog to Application Insights."
4. Database — "SQL Server 2019; ~60 tables; stored procedures for heavy reports; indexes tuned using execution plans."
5. Security — "Azure AD (Entra ID) login; API validates JWT bearer tokens; role-based policies."
6. Delivery — "Git with feature branches and PRs; Azure DevOps pipelines build, test and deploy to Azure App Service; separate dev/QA/prod."
7. Your part — "I owned the orders module end to end: API, EF queries, the Angular screens, and I cut the order search from 6 s to 300 ms by adding a covering index and paging."

Draw it as you talk:

[Angular SPA] --HTTPS + JWT--> [ASP.NET Core API] --EF Core--> [SQL Server]
      |                              |                              
  Entra ID login            Serilog -> App Insights          Nightly SSIS/ETL

Interview tip: Always end with your contribution and one measurable result. Interviewers remember numbers.