Katkat

Discuss productionizing event-timeout detector

Applied IntuitionSoftware Engineer · Technical Screen

Last updated

Discuss productionizing event-timeout detector evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

Define and evaluate a production-ready architecture for the event-timeout detector. Specify the external API and data model (schemas, idempotency keys), time semantics (processing vs event time), and handling of clock skew. Describe sharding strategy by event_id, state storage choice, consistency model for reads, and failure recovery. Discuss performance optimizations (e.g., timer wheels vs heaps/LRU, batching), backpressure, and memory limits. Enumerate production edge cases (late/dropped/duplicated/reordered messages, very large timeouts, long silences, restarts) and how you would test, monitor, and alert.