Design a Crypto Exchange Explore Page for Browsing Assets With Live Prices
Company: Coinbase
Role: Software Engineer
Category: System Design
Difficulty: medium
Interview Round: Onsite
Design the Explore page of a large cryptocurrency exchange: the public page where visitors browse and discover the crypto assets the exchange tracks. The report gives only the name of the page, so assume a market overview that lists many assets with their current price and recent price change, lets visitors sort, filter and search the list, and links each asset to its own detail page. Confirm the scope, the scale and how fresh the prices must be with the interviewer before designing.
```hint Sort the data by how fast it changes
Separate the data on the page into what changes many times a second, what changes a few times a day, and what is identical for every visitor.
```
```hint Many viewers, one answer
Ask how many different versions of a sorted asset list exist at any moment, and whether each request needs to compute its own.
```
### Clarifying Questions
- How many assets are listed, and how many concurrent viewers are expected at peak, for example during a market-wide price swing?
- Which columns and sort orders are required: price, 24-hour change, market capitalization, volume, a small price chart, top movers, newly listed assets?
- How fresh must prices be: ticking live on the page, or refreshed every few seconds?
- Is the page identical for every visitor, or are parts personalized, such as watchlists, regional availability, language or display currency?
- Where do prices come from: the exchange's own markets, external market-data providers, or both?
### What a Strong Answer Covers
- Requirements and scale estimates that separate the shared, cacheable list from personalized parts
- A market-data pipeline that turns trades and quotes into per-asset figures such as price, 24-hour change, volume and a sparkline
- Precomputed sorted and filtered views served from memory and cache, with pagination that stays consistent while prices move
- A real-time update path to many viewers with conflation and throttling
- Asset catalog management, search, and regional availability rules
- Behavior under traffic spikes and stale or faulty price feeds, plus monitoring
### Follow-up Questions
- During a sharp market move, traffic jumps tenfold and prices change many times a second. What breaks first, and how do you protect it?
- A visitor pages through the list while the sort order shifts with live prices. How do you avoid duplicates and missing assets between pages?
- One price source starts sending wrong prices for an asset. How do you detect it and keep the wrong number off the page?
- How would you add a personalized section without losing the cacheability of the rest of the page?
Overview: Design the Explore page of a cryptocurrency exchange, where visitors browse many crypto assets with current prices and recent price changes, sort and search the list, and open asset details. Tests market-data pipelines, caching of shared views, real-time price fan-out and behavior during traffic spikes.
Read the full Coinbase Software Engineer interview experience this question came from