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 26 of 52
Chooses credential transport and server state from client shape, revocation, browser threats, scaling, and operational requirements.
Chooses hooks by application readiness phase and keeps migrations, warm-up, listeners, and background resources owned and observable.
Chooses visibility, mutual exclusion, or atomic read-modify-write based on the invariant instead of treating the tools as interchangeable.
Chooses the smallest execution model that satisfies the task while recognizing when explicit multi-step coordination adds real value.
Bases CSRF policy on whether browsers automatically attach credentials and keeps unsafe requests protected without disabling security globally.
Distinguishes small in-process post-response work from durable, retryable, independently operated jobs.
Uses generated examples to test stable invariants while preserving readable examples and reproducible failures.
Explains per-thread state, pooled-thread leakage, context cleanup, hidden dependencies, and virtual-thread scaling concerns.
Separates reactive synchronization inputs from non-reactive logic that still needs the latest props or state.
Chooses a Django user model early and preserves swappable references without turning it into a profile dumping ground.
Chooses request-response, streaming, or durable background execution based on duration, user interaction, reliability, and side effects.
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.