3. Project explanation that impresses

Structure (3–5 minutes):

1. Business context — client/domain, users, problem solved.
2. Architecture — frontend → API → services → database → integrations; hosting (Azure/on-prem); draw it.
3. Your role — modules you owned, decisions you made.
4. Tech stack — and why (e.g. "Dapper for reporting queries because EF generated inefficient SQL").
5. A challenge — problem → investigation → solution → measurable result.
6. Process — Agile/Scrum, CI/CD, code reviews, testing.
7. What you'd improve.

Expect drill-down questions on anything you mention — only mention what you can explain deeply.