How do I approach System Design interview questions?

System Design questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master system design interviews.

What difficulty level is this interview question?

This is a hard difficulty System Design question, commonly asked during Onsite rounds at Coinbase.

What role is this question designed for?

This question is commonly asked for Software Engineer candidates at Coinbase during technical interviews.

Design cryptocurrency trading platform | Coinbase Interview Question

Quick Overview

This question evaluates proficiency in distributed system design, integration with external APIs, fault tolerance and reliability, state-machine modeling for order lifecycles, rate-limiting and reconciliation strategies, and scalability within the System Design domain.

System Design: Crypto Trading via Third‑Party Exchanges

Context

You are designing a trading service that accepts client orders (e.g., market and limit) and routes them to third‑party cryptocurrency exchanges. Third‑party exchanges expose nominally synchronous REST/RPC APIs, but may be slow or unreliable. The service must reliably track order state, handle partial fills, and scale under spiky traffic.

Assume:

Users trade using balances held in your system; you must reserve funds before routing orders.
Multiple exchanges may be integrated; each has different authentication, rate limits, and semantics.
The client expects a quick acknowledgement and eventual, accurate execution status.

Tasks

Propose a high‑level architecture that integrates with multiple third‑party exchanges exposing synchronous APIs, while providing a responsive interface to clients.
Define the life‑cycle and state transitions of an order (including partial fills, cancels, and failure/unknown states).
Explain how to handle third‑party exchange timeouts, retries, and failures (including idempotency and reconciliation).
Describe strategies to cope with spiky traffic loads while respecting third‑party rate limits and preserving system stability.

Quick Overview

Context

Assume:

Users trade using balances held in your system; you must reserve funds before routing orders.

Multiple exchanges may be integrated; each has different authentication, rate limits, and semantics.

The client expects a quick acknowledgement and eventual, accurate execution status.

Tasks

Propose a high‑level architecture that integrates with multiple third‑party exchanges exposing synchronous APIs, while providing a responsive interface to clients.

Define the life‑cycle and state transitions of an order (including partial fills, cancels, and failure/unknown states).

Explain how to handle third‑party exchange timeouts, retries, and failures (including idempotency and reconciliation).

Describe strategies to cope with spiky traffic loads while respecting third‑party rate limits and preserving system stability.

Design cryptocurrency trading platform

Quick Overview

System Design: Crypto Trading via Third‑Party Exchanges

Context

Tasks

Solution

Comments (0)

Design cryptocurrency trading platform

Quick Overview

System Design: Crypto Trading via Third‑Party Exchanges

Context

Tasks

Solution

Comments (0)