Coinbase·Software Engineer·Onsite - System Design / Architecture
May 2026
System design round at Coinbase for a software engineer role, focused entirely on building a real-time crypto price feed at scale. Pretty deep technically, they wanted specifics on every layer from exchange ingestion all the way to what the browser does when it loses connection.
- Design the Coinbase home page with real-time cryptocurrency price updates. Walk through the full pipeline from exchange data feeds to what the client renders.
- Compare WebSocket, Server-Sent Events, and long-polling for streaming price updates to the client. What are the tradeoffs and when would you fall back?
- How would you handle throttling and coalescing high-frequency price updates so the UI doesn't become unusable?
- Describe a viewport-driven subscription model where clients only receive updates for the symbols currently visible on screen.
- How do you scale the fan-out layer to support millions of concurrent connected clients?
- What are your reconnect and replay semantics when a client drops and reconnects?
- How does the client degrade gracefully when the streaming connection fails or the data becomes stale?
“This is the whole question, basically.” The rest of the author's notes on Software Engineer interview at Coinbase, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.
View Post