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.
1225 drills fit a 20-minute session. Closest fits first.
Page 15 of 52
Applies parsing, schema and domain validation, authorization, confirmation, idempotency, limits, and audit before execution.
Explains Next.js 16 explicit caching, static shells, dynamic islands, cache keys, and adoption boundaries.
Practices incident response after an OOM: restore service, collect evidence, identify trigger, and prevent recurrence.
Connects application, model, retrieval, tools, validation, retries, and outcomes while controlling sensitive telemetry.
Renders a measured window while preserving identity, scrolling, accessibility, dynamic sizes, and interaction state.
Treats memoization as measured performance work and accounts for prop identity, context, readability, and React Compiler.
Prefers typed APIs for reliable actions and reserves UI automation for constrained cases with stronger observation, approval, and recovery.
Evaluates edge execution and gateway features against model capability, data path, limits, observability, caching safety, and platform ownership.
Centralizes cross-cutting model access concerns when multiple applications or providers justify the added hop and operational ownership.
Layers optimistic routing checks with secure data-layer authorization across components, actions, and handlers.
Reviews a captive scoped dependency as both a lifetime and concurrency bug, then replaces it with explicit per-operation scopes and minimal immutable work data.
Debugs matched rules, cascade origin, importance, layers, specificity, source order, inheritance, and computed values.
Diagnoses forced synchronous layout from interleaved geometry reads and style writes, then batches work and reduces its scope.
Traces synchronous throws and promise rejections through chains, awaits, missing returns, and detached work.
Explains audit fields and data change tracking with practical .NET data-access examples and production trade-offs.
Separates optional, undefined, null, and invalid external data, then narrows values at the correct boundary.
Shows how task interleaving across await points can violate a multi-step invariant.
Maps creation, updates, asynchronous work, validation, authorization, conflicts, and failures to useful HTTP outcomes.
Places state according to who owns it, how long it must live, and whether the URL or server is the source of truth.
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.
Explains what a lambda captures, how captured state is shared, and why a long-lived callback can retain more memory than expected.
Review async .NET code that does not accept or propagate CancellationToken and explain the practical production risk.
Designs controlled diagnostic access, collection triggers, container permissions, artifact egress, privacy, retention, and post-capture verification.