Loading
Pick a focused question that fits your time, stack, and interview goal.
584 results across 1 active filter
Page 8 of 25
Explains cache-key scope for tenant, user, role, locale, filters, response version, and security-sensitive reads.
Designs a sharding strategy with a stable key, balanced load, routing, resharding, cross-shard limits, and operational ownership.
Explains why message handlers must tolerate duplicate delivery and how idempotency protects side effects.
Explains how systems behave when the broker is down or slow and how backpressure protects callers and dependencies.
Explains how client-side validation, server-side validation, DTOs, domain rules, and user feedback work together.
Explains health checks that prove an API can serve traffic without becoming fragile dependency probes.
Chooses safe cached, partial, pending, read-only, or unavailable behavior and makes degraded state explicit to clients and operators.
Explains practical UI states for data fetching, empty results, partial failure, retry, and accessible recovery.
Explains list/detail API boundaries, route state, prefetching, selected item behavior, and avoiding over-fetching.
Design list endpoints with pagination, filtering, sorting, limits, and database-aware performance behavior.
Explains how to split components around ownership, reuse, readability, state, and API-like prop contracts.
Uses read replicas selectively while accounting for stale reads, read-after-write behavior, routing, failover, query cost, and replication health.
Designs live updates with polling, server-sent events, or WebSockets while preserving authorization, ordering, scale, and fallback behavior.
Designs scheduled jobs with locking, idempotency, observability, retries, and safe operations across multiple instances.
Builds request and response contracts that tolerate independently deployed clients through explicit ownership, additive evolution, stable semantics, and measured deprecation.
Design request DTOs that protect API contracts from domain and persistence models.
Explains retry strategy for transient failures and poison-message handling for permanent failures.
Explains how custom hooks share stateful behavior while preserving ownership, lifecycle, and a focused contract.
Designs search and filtering with controlled query contracts, indexing, pagination, ranking, and operational limits.
Uses unique namespaces and correctly scoped fixtures so parallel tests improve speed without creating collisions.
Implements correct half-open interval overlap logic for booking validation.
Explains hot-key behavior, traffic concentration, partition pressure, payload size, and mitigation options.
Treats flakiness as an observable defect in timing, state, order, infrastructure, or product behavior.
Diagnoses hidden per-row EF Core queries and replaces them with a bounded query shape without creating an oversized join.