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 46 of 52
Separates source state, derived state, and synchronization with external systems to prevent reactive loops.
Connects static ownership to constants and stateless operations while exposing the risks of global mutable state and initialization.
Rejects agent complexity when rules, APIs, search, ordinary automation, or a bounded model call solve the task more safely.
Identifies tasks better served by deterministic code, search, rules, or conventional models because of correctness, latency, cost, or control.
Overrides unstable external boundaries intentionally while keeping the framework behavior and real collaborators the test claims to prove.
Separates declared variable types, unchecked developer assertions, and compatibility checking that preserves useful inferred types.
Chooses Java time types by business meaning and handles time zones, daylight-saving transitions, persistence, and testable clocks.
Distinguishes a typed final answer from a model request for the application to execute an external capability.
Compares eager collections with lazy one-pass generation through memory, timing, reuse, readability, and resource ownership.
Compares Java interfaces and abstract classes through contract, shared state, implementation reuse, and evolution trade-offs.
Compares Java list implementations using actual access patterns, traversal cost, memory locality, and insertion location.
Chooses an explicit lock only when timed, interruptible, conditional, or advanced acquisition behavior justifies manual lifecycle.
Chooses between blocking navigation for essential data and rendering a page-owned loading state.
Connects layouts and templates to navigation, state lifetime, Effects, and deliberate remounting in the App Router.
Chooses between synchronous UI state and asynchronous event streams without treating either model as a replacement for the other.
Uses task bounds and evaluation evidence to choose smaller models for lower latency, cost, capacity, privacy, or local execution.
Chooses among common Java map implementations by lookup behavior, iteration order, sorting, range operations, and key contracts.
Distinguishes one-way data, events, and deliberate two-way component contracts without hiding ownership.
Explains minimal APIs, endpoint groups, dependency injection, typed results, filters, and when they fit real services.
Chooses promise combinators by success criteria, failure semantics, cancellation needs, and the fate of losing operations.
Separates in-process decoupling from durable cross-process delivery and makes timing, failure, and transaction expectations explicit.
Chooses post-paint synchronization by default and reserves layout effects for pre-paint measurement or correction.
Uses examples to clarify ambiguous task behavior while accounting for token cost, bias, maintenance, and evaluation evidence.
Identifies useful memory and GC signals for alerting without overwhelming the team with noisy telemetry.