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.
40 results across 1 active filter
Page 2 of 2
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.
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.
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.
Maps an HTTP ETag precondition to EF Core rowversion and returns 412 when the representation is stale.
Frames a vague system-design problem with explicit flows, constraints, scale estimates, and measurable quality targets before selecting components.
Validates a bounded command set completely before applying all updates in one SaveChanges transaction.
Stores an idempotency key, request hash, and response in the same transaction as the created resource.
Chooses between a modular monolith and microservices using domain boundaries, team ownership, scaling, deployment, data consistency, and operational cost.
Selects synchronous calls, asynchronous messaging, or a deliberate combination based on user feedback, coupling, latency, durability, and failure behavior.