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 3 of 20
Focuses on ToList chains, collection capacity, repeated enumeration, and memory-aware data shaping.
Explains a practical approach to diagnosing failed builds, tests, package restore, environment issues, or flaky checks.
Explains transient database errors, retry strategy, EF Core execution strategy, idempotency, timeouts, and avoiding retry storms.
Covers deployment logs, startup failures, runtime stack, app settings, missing files, Key Vault references, and post-deployment diagnosis.
Frames allocation reduction as measurement-driven API work rather than premature micro-optimization.
Builds a story about improving code quality incrementally while still delivering product value.
Explains how to triage post-release 500 errors using deployment correlation, logs, traces, feature flags, and rollback safety.
Explains how to diagnose 401/403 spikes across token validation, identity provider issues, clock skew, deployment changes, and abuse.
Explains when to store large payloads outside the broker and pass references through messages.
Design a bounded-concurrency approach for calling an external API safely from .NET code.
Predicts when an in-memory LINQ pipeline runs and prevents repeated work, changed results, and hidden side effects.
Uses declarative infrastructure, reviewed plans, environment parameters, protected deployment identities, state management, and drift control without hiding operational risk.
Explains when filters, sorting, pagination, and selection belong in search parameters and how to keep navigation predictable.
Explains operational signals for queue-backed systems and how to respond when consumers fall behind.
Turns a useful Aspire development model into explicit production infrastructure without treating the local AppHost as the runtime platform.
Predicts how the built-in container resolves repeated service registrations and chooses explicit selection without service-location logic.
Uses nullable annotations as a compile-time contract while still validating untrusted and legacy runtime inputs.
Uses type, property, relational, and list patterns to express decisions while keeping null and unhandled cases explicit.
Explain why request cancellation should flow into EF Core queries and where it does or does not help.
Combines ThreadPool counters, repeated stack snapshots, and wait-event traces to distinguish blocked workers from CPU or dependency pressure.
Compare public and internal APIs in terms of compatibility, documentation, security, support, and evolution speed.
Builds a story about challenging a risky requirement while staying constructive and product-oriented.
Investigate and fix a race condition caused by shared mutable state in a .NET service.
Explains when production approvals are useful and how to avoid turning them into empty bureaucracy.