PracHub
QuestionsPremiumCoachesLearningGuidesInterview Prep
|Home/System Design/eBay

Design an online marketplace for buying and selling

Last updated: Jun 3, 2026

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.

  • hard
  • eBay
  • System Design
  • Software Engineer

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.

Quick Answer: 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.

Related Interview Questions

  • Design an Ad Assignment API - eBay (medium)
  • Design a Relational-to-DynamoDB Migration System - eBay (medium)
  • Design a Top-K trending service - eBay (medium)
  • Handle cache-update conflicts in distributed services - eBay (hard)
eBay logo
eBay
Sep 6, 2025, 12:00 AM
Software Engineer
Onsite
System Design
3
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.

Solution

Show

Submit Your Answer

Sign in to leave a comment

Loading comments...

Browse More Questions

More System Design•More eBay•More Software Engineer•eBay Software Engineer•eBay System Design•Software Engineer System Design
PracHub

Master your tech interviews with 8,500+ real questions from top companies.

Product

  • Questions
  • Learning Tracks
  • Interview Guides
  • Resources
  • Premium
  • For Universities
  • Student Access

Browse

  • By Company
  • By Role
  • By Category
  • Topic Hubs
  • SQL Questions
  • Compare Platforms
  • Discord Community

Support

  • support@prachub.com
  • (916) 541-4762

Legal

  • Privacy Policy
  • Terms of Service
  • About Us

© 2026 PracHub. All rights reserved.