.NET Junior Technical Screen

What they ask

Junior .NET hiring runs HR first, then a technical interview. The technical questions start at fundamentals and move to framework specifics:

• OOP: the four pillars with examples, interface vs abstract class, SOLID in one sentence each.
• Software life cycle: what happens between a ticket and production; where testing sits; what a code review is for.
• .NET basics: value vs reference types, async/await, garbage collection, dependency injection lifetimes (transient, scoped, singleton).
• Middleware and filters: how the ASP.NET Core request pipeline works, the order of middleware, when to use an action filter instead of middleware, how to write a global exception handler.
• Entity Framework and LINQ: IQueryable vs IEnumerable, deferred execution, N+1 and Include, tracking vs no-tracking queries.
• SQL: joins, indexes, a query with GROUP BY and HAVING; for a lending product, "customers with more than two active loans and their total outstanding".

Some rounds also include a problem-solving question at an easy online-judge level.

What they look for

• Clear explanations with a small example each; they move to the next topic once you show understanding.
• Practical knowledge of the request pipeline, since that is where juniors usually struggle.
• Honest "I have not used that" instead of guessing; the interviewers are senior engineers.