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 9 of 37
Investigate and fix a race condition caused by shared mutable state in a .NET service.
Explains when production approvals are useful and how to avoid turning them into empty bureaucracy.
Shows how to unblock delivery across team boundaries without hiding risk, blaming another team, or creating an unsafe shortcut.
Explains how multiple worker instances share queue work and what limits safe scaling.
Builds dependency-specific timeout budgets that contain slow SQL, HTTP, and cache calls without creating unsafe retries or ambiguous writes.
Builds a story about taking responsibility for a production bug, mitigating impact, and preventing recurrence.
Shows honest ownership of a project that missed its goal, including evidence, recovery, and changed judgment.
Designs integration tests for authentication, capabilities, ownership, account status, and cross-tenant isolation without bypassing the real authorization pipeline.
Tests durable background processing across duplicate delivery, retries, acknowledgement timing, crashes, poison messages, and observable completion.
Explains how to diagnose and mitigate a downstream dependency slowing the API through timeouts, retries, and degraded behavior.
Explains how to investigate queue age, backlog, worker health, poison messages, dependency failures, and safe catch-up.
Diagnoses aliasing and shallow-copy mistakes, then restores explicit state ownership and immutable update boundaries.
Use correlation IDs, structured logs, and logging scopes to make API failures traceable in production.
Explains how query tags, request correlation, and telemetry help connect slow SQL back to code paths.
Redesigns read-heavy shared state so readers observe a complete version without coordinating every access through a lock.
Use OpenAPI for API design, client integration, testing, and contract review in ASP.NET Core services.
Separates product policy, orchestration, model access, data and tools, validation, state, and operations into explicit application-owned boundaries.
Separates SQLAlchemy connectivity, checked-out database resources, ORM state, and transaction ownership.
Balances faster startup and unused-bean avoidance against delayed failures, first-request latency, memory growth, and readiness semantics.
Uses lifespan to acquire and release process-level resources while making readiness, workers, failures, and tests explicit.
Handles expected failures at their callsite and reserves ErrorHandler for reporting unexpected framework or global failures with useful context.
Uses functional interceptors for cross-cutting transport concerns without hiding domain behavior or unsafe retries.
Keeps representation validation at the API boundary and moves changing workflows to explicit application owners.
Keeps Next.js 16 Proxy focused on request routing and optimistic checks rather than data access or final authorization.