Temporal·Software Engineer·Onsite - System Design / Architecture
- Design a 1-on-1 chat system end to end, covering client connectivity, message ingestion, the message pipeline, persistence, presence, fan-out, ordering, and read receipts.
- How does Kafka differ from Redis as a backing store for a message pipeline, and when would you choose one over the other?
- What delivery semantics would you use in the Kafka-backed message pipeline and why?
- How do you handle ordering guarantees within a single conversation?
- How would you implement online and offline presence, and how does that affect message delivery?
“This was the whole interview basically.”