ASP.NET vs ASP.NET Core
Link Development interview question (Egypt) · stage: Technical Interview · domain: OOP Design and CS Fundamentals · role: Backend Engineer · difficulty: Medium · asked twice, last in March 2026
What they ask
The technical interview is held online over Teams with a team lead. It covers OOP, .NET, database relationships and a few problem-solving scenarios, and one question that several candidates mention by name: what is the difference between ASP.NET and ASP.NET Core? Questions in this area, for example:
The headline question. Be ready to cover: cross-platform hosting and Kestrel, the middleware pipeline vs the old HttpModule and HttpHandler model, built-in dependency injection, the unified MVC and Web API stack, configuration and environments, performance, and the practical migration pain points (System.Web, session state, third-party libraries).
OOP and .NET. Interface vs abstract class in C#, when to use virtual and override, IEnumerable vs IQueryable, what async and await actually do to a request thread, how dependency injection lifetimes (transient, scoped, singleton) behave in a web app.
Database relationships. One-to-many and many-to-many in a relational schema, how you model them in Entity Framework, and what a navigation property costs you if you are careless with lazy loading.
Scenarios. An endpoint is slow only under load; a nightly job double-charges a customer; a client asks for a report that joins five tables. What do you do first?
What they look for
Practical .NET knowledge tied to real projects, and the ability to explain a concept in plain English (they care about English and personality fit as much as technical depth).