Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
618 drills fit a 20-minute session. Closest fits first.
Page 25 of 26
Explains how hash-based collections use hash codes and equality, then chooses Dictionary or HashSet from the value the program needs to store.
Uses controlled state transitions and intention-revealing APIs to keep objects valid rather than treating encapsulation as private fields alone.
Explain async/await as C# syntax over Task-based asynchronous work, with attention to non-blocking I/O and request throughput.
Explains join behavior using API-shaped data, missing related rows, and result-cardinality trade-offs.
Explains how React components render from props and state, and how updates flow through a component tree.
Explains how an HTTP request flows through ASP.NET Core middleware, routing, endpoint execution, and response generation.
Explains what CORS controls, what it does not protect, and why APIs still need authentication and authorization.
Explains staging slots, validation before swap, warm-up, traffic continuity, and safer production releases for App Service APIs.
Explains controller actions, result types, status codes, thin controllers, and HTTP response generation.
Introduces managed heap cleanup, generational collection, object lifetime, and why allocation behavior affects .NET services.
Explains release notes and changelog thinking for engineering, QA, support, and product communication.
Explains semantic versioning for .NET applications and how it communicates release impact.
Covers App Service app settings, environment-specific configuration, restarts, slot settings, and avoiding hard-coded production values.
Explains DbContext lifetime and unit-of-work boundaries with practical .NET data-access examples and production trade-offs.
Explains a practical Git workflow for a .NET team using branches, pull requests, code review, and protected main branches.
Designs consumer-focused contracts that reduce accidental authority and coupling without producing meaningless one-method wrappers.
Explains cache observability across hit rate, latency, source load, memory, evictions, stale data, and fallback behavior.
Starts object-oriented design from cohesive state and behavior instead of creating classes for every noun in a requirement.
Explains when backend work belongs in a queue instead of slow or unreliable inline request handling.
Explains correlation IDs across request logs, dependency calls, queues, workers, and support investigations.
Separates dependency registration from per-request middleware and endpoint composition in modern ASP.NET Core startup.
Explains safe error responses for auth failures, validation failures, server errors, and sensitive resource access.
Explains identity versus permission checks in API request handling and why both boundaries need server-side enforcement.
Uses static members for type-wide stateless behavior and constants while avoiding hidden global mutable state and lifetime problems.