Loading
Pick a focused question that fits your time, stack, and interview goal.
108 results across 1 active filter
Page 2 of 5
Applies CQRS proportionally, separating model responsibilities without assuming separate databases, messaging, or event sourcing.
Builds a story about collaborating during an incident without chaos or duplicated work.
Explains a constraint-first approach to responsive layout, intrinsic sizing, overflow, and content resilience.
Turns business recovery targets into right-sized backup, restore, standby, failover, validation, ownership, and rehearsal plans.
Distinguishes explicit dependency injection from runtime service lookup and identifies the narrow framework boundaries where scoped resolution is legitimate.
Keeps business policy independent from infrastructure while centralizing concrete dependency assembly at the application edge.
Designs realistic load, stress, spike, and soak tests from workload assumptions and SLOs while correlating client results with server bottlenecks.
Builds a risk-based frontend test strategy across unit, component, integration, contract, and end-to-end boundaries.
Designs a multi-service business workflow using local transactions, durable progress, idempotency, retries, and domain-specific compensation.
Designs a sharding strategy with a stable key, balanced load, routing, resharding, cross-shard limits, and operational ownership.
Chooses safe cached, partial, pending, read-only, or unavailable behavior and makes degraded state explicit to clients and operators.
Uses read replicas selectively while accounting for stale reads, read-after-write behavior, routing, failover, query cost, and replication health.
Explains how custom hooks share stateful behavior while preserving ownership, lifecycle, and a focused contract.
Uses unique namespaces and correctly scoped fixtures so parallel tests improve speed without creating collisions.
Uses field data, lab evidence, and release correlation to diagnose LCP, INP, and CLS regressions without guessing.
Treats flakiness as an observable defect in timing, state, order, infrastructure, or product behavior.
Explains how hash-based collections use hash codes and equality, then chooses Dictionary or HashSet from the value the program needs to store.
Builds a story about resolving technical disagreement in review without ego or passive approval.
Uses controlled state transitions and intention-revealing APIs to keep objects valid rather than treating encapsulation as private fields alone.
Turns a modular-monolith choice into enforceable code and data ownership rather than relying on folders and team discipline alone.
Connects equality semantics to hash-based collections and chooses identity or value equality deliberately.
Improves architecture through protected behavior, incremental boundaries, and measurable delivery instead of a risky all-at-once rewrite.
Connects JavaScript tasks and microtasks to rendering, responsiveness, and practical performance fixes.
Builds a story about turning an incident into regression guards, observability, and process improvement.