Design an online marketplace for buying and selling

Read the full interview experience this question came from →

Quick Overview

This question evaluates competency in large-scale system design, covering distributed systems, data modeling, scalability, consistency, security, payments and escrow, media handling, and operational concerns for a two-sided online marketplace.

Design an online marketplace for buying and selling

Company: eBay

Role: Software Engineer

Category: System Design

Difficulty: hard

Interview Round: Onsite

Design a backend for an online marketplace where users list items for sale and others purchase them. Cover core APIs, data model, search and filtering, image handling, payments/escrow, inventory and availability, notifications, fraud/abuse prevention, rate limiting, and observability. Discuss scaling strategies (partitioning, indexing, caching, CDN), consistency across orders and listings, and a multi-region deployment plan with disaster recovery.

Overview: This question evaluates competency in large-scale system design, covering distributed systems, data modeling, scalability, consistency, security, payments and escrow, media handling, and operational concerns for a two-sided online marketplace.

Read the full eBay Software Engineer interview experience this question came from

|Home/System Design/eBay
eBay logo
eBay
Sep 6, 2025
hardSoftware EngineerOnsiteSystem Design
8
0

System Design: Online Marketplace Backend

Context

Design the backend for a two-sided online marketplace where sellers list items and buyers purchase them. Assume tens of millions of listings, millions of MAUs, and peak traffic spikes (e.g., flash sales). The system must be secure, scalable, reliable, and support global deployment.

Requirements

  1. Core APIs and Data Model
  2. Search and Filtering
  3. Image Handling
  4. Payments and Escrow
  5. Inventory and Availability
  6. Notifications
  7. Fraud/Abuse Prevention
  8. Rate Limiting
  9. Observability
  10. Scaling Strategies (partitioning, indexing, caching, CDN)
  11. Consistency across Orders and Listings
  12. Multi-Region Deployment and Disaster Recovery

Provide the architecture, key trade-offs, and rationale for each section.

Submit Your Answer to Earn 20XP

Sign in to leave a comment

Loading comments...