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.
298 results across 1 active filter
Page 5 of 13
Explains cache-key scope for tenant, user, role, locale, filters, response version, and security-sensitive reads.
Designs comments with permissions, threading, mentions, notifications, editing history, and moderation concerns.
Designs draft, review, publish, rollback, and audit behavior for content managed by editors and admins.
Designs a sharding strategy with a stable key, balanced load, routing, resharding, cross-shard limits, and operational ownership.
Designs deletion, retention, soft delete, hard delete, backups, audit records, and asynchronous cleanup across related data.
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 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.
Designs user reports, moderation queues, actions, audit history, abuse controls, and appeal-friendly decisions.
Designs user preferences, channel rules, unsubscribe behavior, digest generation, and delivery suppression.
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.
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.
Explains retry strategy for transient failures and poison-message handling for permanent failures.
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.