Interviewers test a mix of fundamentals and real-project knowledge. A one-week plan:
C# and .NET basics: value vs reference types, string immutability, collections, generics, LINQ, async/await, delegates and events, exception handling, garbage collection and IDisposable.
ASP.NET Core: request pipeline and middleware, dependency injection and lifetimes, routing, model binding and validation, authentication vs authorization, configuration, logging.
Data: Entity Framework Core (tracking, Include, migrations, N+1), SQL joins, indexes, transactions and writing a few queries by hand.
Design basics: SOLID, common patterns (repository, factory, dependency injection), REST principles, status codes.
Your own project: be ready to explain your last project, your role, a hard bug you solved and why you made certain choices. This is where many people win or lose.
Practise answering aloud. If you do not know something, say how you would find out, rather than guessing. And prepare two questions to ask them about the team and the codebase.
Markdown for AI
A clean, structured version of this page for AI assistants and LLMs.
We use cookies to ensure you have the best browsing experience on our website. By using our site, you
acknowledge that you have read and understood our
Cookie Policy &
Privacy Policy.
Interviewers test a mix of fundamentals and real-project knowledge. A one-week plan:
C# and .NET basics: value vs reference types, string immutability, collections, generics, LINQ, async/await, delegates and events, exception handling, garbage collection and IDisposable.
ASP.NET Core: request pipeline and middleware, dependency injection and lifetimes, routing, model binding and validation, authentication vs authorization, configuration, logging.
Data: Entity Framework Core (tracking, Include, migrations, N+1), SQL joins, indexes, transactions and writing a few queries by hand.
Design basics: SOLID, common patterns (repository, factory, dependency injection), REST principles, status codes.
Your own project: be ready to explain your last project, your role, a hard bug you solved and why you made certain choices. This is where many people win or lose.
Practise answering aloud. If you do not know something, say how you would find out, rather than guessing. And prepare two questions to ask them about the team and the codebase.