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.
460 drills fit a 10-minute session. Closest fits first.
Page 7 of 20
Collects a bounded EventPipe CPU trace and reads stack evidence without confusing hot methods, blocked time, native work, or sampling artifacts.
Builds a story about resolving technical disagreement in review without ego or passive approval.
Builds a story about turning an incident into regression guards, observability, and process improvement.
Builds a story about making competing work visible and helping the team choose intentionally.
Builds a story about turning unclear requirements into a scoped, testable plan without overbuilding.
Builds a story about improving team workflow with lightweight, useful process changes.
Builds a story about learning a new technology in a structured way and applying it safely.
Builds a story about choosing a pragmatic technical path under time pressure while preserving future safety.
Builds a story about helping a teammate grow while still moving the work forward.
Builds a story about handling a missed estimate transparently and recovering with a realistic plan.
Builds a story about taking feedback seriously and changing behavior in a visible way.
Explains how Aspire references inject resource configuration, how logical service names resolve, and why dependency wiring differs from startup readiness.
Builds a concrete story about owning a feature from requirements through release, verification, and follow-up.
Explains labels, keyboard behavior, focus, semantic HTML, errors, color contrast, and accessible custom controls.
Compare controller ActionResult patterns with minimal API typed results and explicit HTTP outcomes.
Explains physical connection reuse, pool partitioning, short ownership, exhaustion causes, diagnostics, and why increasing the pool is not the first fix.
Separates deployable artifact identity from client-facing contract compatibility, allowing frequent releases without unnecessary API-version churn.
Separates application composition in AppHost from reusable in-process defaults for telemetry, health, resilience, and service discovery.
Explains rate-limit identity, endpoint cost, login and suggestion throttles, Redis counters, user experience, and observability.
Explains how ASP.NET Core schemes select handlers and why authenticate, challenge, and forbid produce different security behavior.
Compares server-controlled output caching with HTTP cache semantics and defines safe keys, variation, invalidation, identity, and multi-instance behavior.
Explains when cleanup needs asynchronous I/O, how await using guarantees disposal, and how ownership, exceptions, DI lifetimes, and shutdown affect the design.
Explains why sensitive admin actions need authorization, reason capture, before/after context, and tamper-resistant audit records.
Explains API keys, client credentials, managed identity, mTLS, scopes, rotation, and per-client observability.