Loading
Pick a focused question that fits your time, stack, and interview goal.
690 results
Page 10 of 29
Designs user preferences, channel rules, unsubscribe behavior, digest generation, and delivery suppression.
Design list endpoints with pagination, filtering, sorting, limits, and database-aware performance behavior.
Designs layered public API protection with caller identity, quotas, burst limits, abuse signals, and client-friendly responses.
Designs authorization that combines roles, permissions, tenant context, resource ownership, and auditability.
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.
Protects transactional traffic from reporting load through freshness requirements, bounded asynchronous jobs, tuned summaries, workload isolation, replicas or warehouses, and explicit capacity gates.
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.
Explains how to reprocess event streams safely for new projections, bug fixes, and data repair.
Designs saved filters, scheduled matching, alert delivery, and freshness trade-offs for search-driven product workflows.
Designs search and filtering with controlled query contracts, indexing, pagination, ranking, and operational limits.
Designs plan entitlements, provider webhooks, idempotent billing updates, access checks, grace periods, and support overrides.
Designs a controlled support impersonation workflow with scoped access, approvals, visible banners, audit trails, and session boundaries.
Designs membership, role changes, removal, ownership transfer, and permission updates without weakening tenant boundaries.
Uses unique namespaces and correctly scoped fixtures so parallel tests improve speed without creating collisions.
Designs an invitation workflow with token security, expiry, membership creation, email delivery, and replay-safe onboarding.
Designs a settings service with defaults, validation, scoped preferences, caching, and safe rollout of new settings.
Implements correct half-open interval overlap logic for booking validation.
Uses field data, lab evidence, and release correlation to diagnose LCP, INP, and CLS regressions without guessing.