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.
176 results across 1 active filter
Page 7 of 8
Tests rendered behavior, user interaction, outputs, and visible failure states without coupling to private implementation details.
Renders a measured window while preserving identity, scrolling, accessibility, dynamic sizes, and interaction state.
Uses harnesses for reusable or complex widgets where a stable user-oriented test API is more valuable than direct DOM coupling.
Treats memoization as measured performance work and accounts for prop identity, context, readability, and React Compiler.
Uses derived types for genuine relationships while preserving explicit boundaries for domain and transport models.
Uses runtime tokens for configuration and abstractions while distinguishing provider recipes and instance identity.
Separates reactive synchronization inputs from non-reactive logic that still needs the latest props or state.
Separates missing resources, canonical navigation, authorization outcomes, expected failures, and unexpected exceptions.
Separates source state, derived state, and synchronization with external systems to prevent reactive loops.
Exposes a small focus, scroll, or media API while keeping component internals private and preferring declarative props.
Defers non-critical UI with deliberate triggers, placeholders, prefetching, and hydration behavior while protecting core interactions.
Separates declared variable types, unchecked developer assertions, and compatibility checking that preserves useful inferred types.
Keeps input and direct feedback urgent while rendering expensive navigation or result updates as interruptible work.
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.
Distinguishes render-driving state from instance-local mutable values and DOM references.
Chooses between UI-coupled mutations and explicit HTTP contracts without treating either as a hidden trust boundary.
Distinguishes one-way data, events, and deliberate two-way component contracts without hiding ownership.
Chooses promise combinators by success criteria, failure semantics, cancellation needs, and the fate of losing operations.
Chooses post-paint synchronization by default and reserves layout effects for pre-paint measurement or correction.
Layers optimistic routing checks with secure data-layer authorization across components, actions, and handlers.
Prioritizes explicit normalization, strict equality, object identity, nullish handling, and NaN over coercion puzzles.
Finds missing render notifications that forced test change detection can hide and uses production-like stability checks.