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.
878 drills fit a 10-minute session. Closest fits first.
Page 8 of 37
Builds a readable request with stable instructions and clearly delimited, provenance-aware untrusted inputs.
Sizes per-instance database concurrency from workload and database capacity instead of equating more connections with more throughput.
Designs explicit ESM boundaries with focused exports, controlled side effects, and dependency direction that supports safe bundling.
Combines semantic queries, keyboard interaction, focus assertions, and automated checks while retaining manual assistive-technology review.
Uses thread dumps, heap dumps, logger changes, mappings, and configuration evidence through a tightly controlled operator path.
Checks model, feature, API, region, quota, commercial access, lifecycle, and dependent-service compatibility before rollout.
Builds a story about improving code quality incrementally while still delivering product value.
Builds a concrete story about earning alignment through evidence, listening, and a low-risk path rather than positional power.
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.