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 12 of 37
Separates missing resources, canonical navigation, authorization outcomes, expected failures, and unexpected exceptions.
Uses fixture factories and test-data builders to keep setup flexible, readable, and owned by each test.
Exposes a small focus, scroll, or media API while keeping component internals private and preferring declarative props.
Aligns selected database data with an API read model and avoids unnecessary ORM state.
Uses pre-filtering for authorization and hard constraints while recognizing engine-specific recall and performance behavior.
Uses task-aware context for tracing while keeping business inputs explicit and correctly reset.
Uses cryptographically secure token generation and timing-resistant comparison at credential boundaries.
Balances one-call simplicity against explicit multi-step workflows with intermediate validation and failure handling.
Defers non-critical UI with deliberate triggers, placeholders, prefetching, and hydration behavior while protecting core interactions.
Evaluates parallel streams through workload size, splittability, CPU cost, ordering, common-pool contention, state, and measurement.
Chooses concurrent collections by required atomic operations and iteration semantics rather than treating them as synchronized replacements.
Distinguishes unavailable conditions, known defects, and unstable tests while keeping lost coverage visible.
Explains monitor wait sets and guarded loops while preferring queues, latches, semaphores, futures, and conditions for standard coordination.
Keeps input and direct feedback urgent while rendering expensive navigation or result updates as interruptible work.
Uses a more precise second-stage ranker on a bounded candidate set while accounting for latency, cost, and authorization.
Covers large exports, uploads, and API responses where bounded memory matters more than convenience.
Chooses Django view style by clarity, reuse, and lifecycle needs rather than hierarchy preference.
Chooses structural or nominal contracts based on ownership, runtime identity, shared behavior, and third-party integration.
Chooses between UI-coupled mutations and explicit HTTP contracts without treating either as a hidden trust boundary.
Chooses task synchronization by protected state, notification predicates, and limited capacity.
Matches exact checks, model judgment, and human expertise to the behavior being measured instead of treating graders as interchangeable.
Chooses Django relationship loading from relationship shape, result cardinality, and measured query behavior.
Chooses synchronous or asynchronous FastAPI test clients from the boundary exercised and resources involved.
Uses pairwise judgments for relative change and absolute criteria for release obligations while controlling order and verbosity bias.