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 5 of 20
Explains a practical debugging path across browser, Next.js layer, API, logs, database, and deployment changes.
Explains why server HTML and client render can disagree, how to debug it, and how to avoid mismatch-prone code.
Builds a race-safe upsert around database-enforced identity, explicit conflict semantics, retries, ordering, and side-effect boundaries.
Explains why message handlers must tolerate duplicate delivery and how idempotency protects side effects.
Protects transactional traffic from reporting load through freshness requirements, bounded asynchronous jobs, tuned summaries, workload isolation, replicas or warehouses, and explicit capacity gates.
Explains hot-key behavior, traffic concentration, partition pressure, payload size, and mitigation options.
Separates a live blocking chain from a deadlock victim, gathers the right database evidence, stabilizes the incident, and fixes lock duration or access order.
Explains split queries versus single joined queries with practical .NET data-access examples and production trade-offs.
Implements representation-aware ETags and conditional GETs correctly, including validators, 304 metadata, authorization, cache variation, generation cost, and tests.
Explains how consumer groups share event-stream work and how offset commits affect duplicate or lost processing.
Explains parameter sniffing, data skew, cached plans, symptoms, and cautious mitigation options in SQL Server.
Explains how statistics and cardinality estimates affect plan choice, joins, memory grants, and slow queries.
Explains why exactly-once claims do not remove the need for idempotent side effects and consistency boundaries.
Explains static extension binding, instance-member precedence, namespace ambiguity, null receivers, and compatibility when APIs evolve.
Explains why cached authorization decisions are risky and how to bound or invalidate permission-related cache safely.
Explains practical frontend performance work: measuring, render cost, memoization, bundle splitting, images, and hydration.
Uses constraints to express required operations and explains safe assignment direction for generic producers and consumers.
Makes EF Core transient retries safe across transactions, uncertain commits, generated keys, and external side effects.
Keeps long-running queue work safe when message ownership expires, renewal fails, settlement is uncertain, or another worker receives the same job.
Explains stale edit detection, row versioning, conflict UI, refresh behavior, and safe update contracts.
Explains what happens when roles or tenant membership change while access tokens still contain old claims.
Explains upload UX, API boundaries, validation, progress, storage, scanning, failure handling, and safe download behavior.
Compares rollback, reset, schema, database, and tenant isolation without hiding transaction or parallelism limits.
Uses per-dependency concurrency limits, queues, pools, and workload partitions to stop one failing path from exhausting the whole API.