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.
15 results across 1 active filter
Page 1 of 1
Designs an async export flow for large reports without blocking API requests or exhausting database and memory resources.
Designs explicit workflow states, allowed transitions, guard rules, audit history, idempotency, and operational repair paths.
Designs a checkout or order creation flow that survives client retries without duplicate orders, payments, or messages.
Designs email, in-app, and push-style notification delivery with preferences, retries, and idempotent side effects.
Designs synchronization with an external system using cursors, retries, idempotency, rate limits, and reconciliation.
Designs a multi-service business workflow using local transactions, durable progress, idempotency, retries, and domain-specific compensation.
Designs authenticated, replay-resistant webhook intake with durable acknowledgement, idempotent asynchronous processing, ordering policy, and reconciliation.
Designs a safe admin import flow with upload staging, validation, preview, confirmation, idempotency, and rollback strategy.
Designs user preferences, channel rules, unsubscribe behavior, digest generation, and delivery suppression.
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.
Separates caller cancellation from a dependency timeout and maps expected downstream outcomes safely.
Repairs a workflow when a remote operation may have succeeded but local state, messages, and callbacks disagree.
Persists a job and outbox command before returning a status URL for long-running work.
Selects synchronous calls, asynchronous messaging, or a deliberate combination based on user feedback, coupling, latency, durability, and failure behavior.