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 Technical Screen 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 image upload end-to-end | Coinbase Interview Question

Quick Overview

This interview question evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer for Design image upload end-to-end states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

Design image upload end-to-end

System Design: End-to-End Image Upload Pipeline

Context

Design an end-to-end system that handles user picture uploads from web or mobile clients through the backend and storage/CDN layers. Assume an object store (e.g., S3/GCS), a CDN, an API service, a background processing tier, and a relational database. Images are typically user-generated (e.g., profile or listing pictures), with typical sizes up to 20 MB, and must be delivered globally.

Requirements

Describe, in detail, how the system handles:

Request flow from browser/app through backend and storage/CDN.
Authentication and authorization.
Upload strategies: direct-to-object-store vs. server-proxied.
Chunked uploads and resume support.
Client- and server-side validation (file type/size, checksums, virus scanning).
Metadata extraction (e.g., EXIF) and sanitization.
Asynchronous processing pipelines/queues.
Image processing (resize/thumbnailing, formats, orientation).
Storage strategy and versioning, including deduplication and lifecycle.
Database writes and idempotency.
CDN caching and invalidation strategies.
Error handling and retries across components.
Observability and alerting.
Performance and cost considerations.
Horizontal scaling and multi-region considerations.

Clearly explain trade-offs and provide guardrails for safe operation. Use small numeric examples where helpful.

Constraints & Assumptions

Preserve the scope, facts, inputs, and requested outputs from the prompt above.
If the prompt leaves a detail unspecified, state a reasonable assumption before relying on it.
Keep the answer interview-ready: concise enough to present, but concrete enough to implement or evaluate.

Clarifying Questions to Ask

Clarify users, core use cases, read/write patterns, scale, latency, availability, and data retention.
State explicit assumptions before making sizing or architecture decisions.
Prioritize the functional path first, then address reliability, security, observability, and rollout.

What a Strong Answer Covers

A scoped requirements summary with concrete non-goals and success metrics.
API, data model, architecture, consistency, capacity, and operations.
Reasoned trade-offs among simple and scalable designs, including bottlenecks and failure modes.
A validation, monitoring, migration, and launch plan appropriate for the risk level.

Follow-up Questions

What breaks first at 10x traffic or data volume?
How would you degrade gracefully during dependency failures?
What metrics and alerts would prove the design is healthy after launch?

Quick Overview

Context

Requirements

Describe, in detail, how the system handles:

Request flow from browser/app through backend and storage/CDN.

Authentication and authorization.

Upload strategies: direct-to-object-store vs. server-proxied.

Chunked uploads and resume support.

Client- and server-side validation (file type/size, checksums, virus scanning).

Metadata extraction (e.g., EXIF) and sanitization.

Asynchronous processing pipelines/queues.

Image processing (resize/thumbnailing, formats, orientation).

Storage strategy and versioning, including deduplication and lifecycle.

Database writes and idempotency.

CDN caching and invalidation strategies.

Error handling and retries across components.

Observability and alerting.

Performance and cost considerations.

Horizontal scaling and multi-region considerations.

Clearly explain trade-offs and provide guardrails for safe operation. Use small numeric examples where helpful.

Constraints & Assumptions

Preserve the scope, facts, inputs, and requested outputs from the prompt above.

If the prompt leaves a detail unspecified, state a reasonable assumption before relying on it.

Keep the answer interview-ready: concise enough to present, but concrete enough to implement or evaluate.

Clarifying Questions to Ask

Clarify users, core use cases, read/write patterns, scale, latency, availability, and data retention.

State explicit assumptions before making sizing or architecture decisions.

Prioritize the functional path first, then address reliability, security, observability, and rollout.

What a Strong Answer Covers

A scoped requirements summary with concrete non-goals and success metrics.

API, data model, architecture, consistency, capacity, and operations.

Reasoned trade-offs among simple and scalable designs, including bottlenecks and failure modes.

A validation, monitoring, migration, and launch plan appropriate for the risk level.

Follow-up Questions

What breaks first at 10x traffic or data volume?

How would you degrade gracefully during dependency failures?

What metrics and alerts would prove the design is healthy after launch?

Design image upload end-to-end

Quick Overview

Design image upload end-to-end

Design image upload end-to-end

System Design: End-to-End Image Upload Pipeline

Context

Requirements

Constraints & Assumptions

Clarifying Questions to Ask

What a Strong Answer Covers

Follow-up Questions

Submit Your Answer to Earn 20XP

Design image upload end-to-end

Quick Overview

Design image upload end-to-end

Design image upload end-to-end

System Design: End-to-End Image Upload Pipeline

Context

Requirements

Constraints & Assumptions

Clarifying Questions to Ask

What a Strong Answer Covers

Follow-up Questions

Submit Your Answer to Earn 20XP