Capital One·Software Engineer·Onsite - System Design / Architecture
- Design a cross-region event processing platform that ingests events from producers, stores them durably, and delivers them to multiple consumers across regions.
- How would you design the public API for both producing and consuming events in this system?
- Walk through your storage and partitioning strategy for the event log.
- What cross-region replication strategy would you use, and how do you handle a full region outage?
- How do you handle duplicate events, retries, and backpressure in this platform?
- What operational features would you build in, such as monitoring, event replay, dead-letter queues, and retention policies?
“This is basically 'design Kafka but explain every choice.' I started with the API surface and partitioning scheme, which felt right, but I got tripped up when they pushed on cross-region replication lag versus consistency tradeoffs.”