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.
1345 results
Page 5 of 57
Explains when optimistic UI is worth it, when to wait for server confirmation, and how to recover from rejected mutations.
Places state according to who owns it, how long it must live, and whether the URL or server is the source of truth.
Compares rollback, roll-forward, feature kill switches, scaling, and degraded mode as incident mitigations.
Chooses a deployment strategy from capacity, compatibility, risk, observability, and rollback needs, then defines progressive promotion and abort signals.
Selects small structural and behavioral patterns from the problem being solved instead of pattern-name recognition.
Separates ordinal identity comparison from culture-aware display ordering and keeps hash-based collection semantics consistent.
Chooses database test infrastructure by the provider behavior a test must prove.
Builds a proportionate test plan from blast radius, failure probability, detectability, and reversibility.
Chooses between sequence, counted, indexed, set, and dictionary contracts based on required operations and complexity.
Chooses counters, traces, stack snapshots, GC dumps, full dumps, or a profiler from the production symptom and investigation cost.
Explains how unit, integration, contract, component, and end-to-end tests cover different failure boundaries.
Implements chunking for batch processing without dropping final partial batches.
Explains the difference between a class and an object, then connects type definitions, instances, identity, and shared behavior to practical C# code.
Explains inward dependency flow, stable business policy, adapters, and when a smaller project structure is enough.
Explains cleanup for subscriptions, timers, event listeners, and aborting stale fetches.
Explains what a lambda captures, how captured state is shared, and why a long-lived callback can retain more memory than expected.
Implements single-flight request coalescing so one load runs per key while unrelated keys remain concurrent.
Review async .NET code that does not accept or propagate CancellationToken and explain the practical production risk.
Uses complexity as a first filter while accounting for constants, locality, allocations, data size, and the complete operation sequence.
Designs controlled diagnostic access, collection triggers, container permissions, artifact egress, privacy, retention, and post-capture verification.
Builds a story about explaining engineering risk in business terms without hiding uncertainty.
Explains short-lived access tokens, refresh-token rotation, revocation, storage choices, and replay detection.
Compares managed model APIs with operating open-weight models across control, expertise, privacy, scale, latency, cost, and portability.
Chooses between managed ingestion and retrieval convenience and custom control over indexing, ranking, security, evaluation, and operations.