Discord·Backend Engineer·Onsite - System Design / Architecture
Jun 2026
Discord system design round, deep dive into distributed replication. They wanted a real implementation-level discussion, not just hand-waving at Raft. Harder than I expected and I definitely left some things on the table around split-brain prevention.
- Design a leader-follower replication system similar to what etcd or Redis uses. Cover leader election, log replication, consistency semantics, failure detection, follower catch-up, split-brain prevention, and read paths. Show enough of the data plane to demonstrate writes propagating from leader to follower and surviving a leader failover.
“I went with Redis-style async replication because I could actually defend it, and pivoted to Raft semantics when they pushed on consistency guarantees.”