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 15 of 37
Explains transaction isolation levels with practical .NET data-access examples and production trade-offs.
Balances declarative transformations with explicit control flow when allocation, early exit, mutation, diagnostics, or complex state matters.
Explains offset versus cursor pagination with practical .NET data-access examples and production trade-offs.
Designs an EF Core optimistic-concurrency contract around tokens, conflict policy, HTTP semantics, merge behavior, and real relational tests.
Explains expand-and-contract migrations, backwards-compatible schema changes, backfills, rollout order, and rollback thinking.
Explains stale closures in callbacks, effects, timers, subscriptions, and how to fix them cleanly.
Compares rollback and roll-forward decisions after a failed production deployment.
Uses async streams for incremental asynchronous production while preserving cancellation, disposal, backpressure expectations, and API boundaries.
Moves invariant-sensitive decisions toward the owning object while keeping orchestration, queries, and cross-boundary work appropriately explicit.
Explains tracing one user action across browser, frontend server, API, dependencies, logs, metrics, and safe diagnostics.
Explains when a Next.js route layer helps with cookies, tokens, aggregation, and UI-specific API adaptation.
Explains saturation signals and how systems shed, queue, throttle, or degrade before cascading failure.
Explains the risks of Redis-based distributed locks and when database constraints, queues, or idempotency are safer.
Explains event schema evolution, backward compatibility, additive changes, consumer rollout, and contract ownership.
Evaluates whether read-heavy access justifies a reader/writer lock instead of a simpler lock or immutable snapshot.
Introduces lower-level allocation tools while emphasizing measurement, ownership, and safe usage.
Separates memory visibility and ordering from atomic multi-step updates, avoiding volatile as a substitute for real synchronization.
Builds a story about protecting quality while still making practical delivery decisions.
Demonstrates technical humility by changing direction when measurements invalidate an earlier decision.
Shows how customer evidence changes scope or design without turning one request into an unvalidated roadmap.
Builds a story about resisting unnecessary complexity and choosing maintainable design.
Chooses heap-focused GC evidence or complete process state based on memory growth, roots, hangs, crashes, locks, and collection risk.
Builds a story about explaining engineering risk in business terms without hiding uncertainty.
Designs useful local database and cache resources without confusing container lifetime, durable data, bind mounts, parameters, and production secrets.