Design a Real-Time Auction Platform

Read the full interview experience this question came from →

Quick Overview

This question evaluates a candidate's ability to design a real-time, high-throughput distributed system focusing on API design, concurrency control, ordering guarantees, idempotency, persistence of bid history and state transitions, and real-time push/update mechanisms.

Design a Real-Time Auction Platform

Company: ByteDance

Role: Software Engineer

Category: System Design

Difficulty: medium

Interview Round: Onsite

Design a real-time online auction platform. Users can browse an auction, submit bids, and see the current highest bid and bid history update live. Traffic can be very high, especially for popular auctions and during the final 30 seconds. The system must preserve bid ordering per auction, reject invalid or stale bids, persist all bids and auction state transitions, and finalize the winning bid when the auction ends. Discuss: - User-facing APIs for reading auctions, submitting bids, and subscribing to live updates. - The write path for bids under high contention. - The real-time push mechanism, such as SSE or WebSocket. - Storage choices for auction metadata, bid history, current highest bid, and event delivery. - Consistency, idempotency, ordering, failure handling, and scalability for hot auctions.

Overview: This question evaluates a candidate's ability to design a real-time, high-throughput distributed system focusing on API design, concurrency control, ordering guarantees, idempotency, persistence of bid history and state transitions, and real-time push/update mechanisms.

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

|Home/System Design/ByteDance
ByteDance logo
ByteDance
Apr 14, 2026
mediumSoftware EngineerOnsiteSystem Design
2
0

Design a real-time online auction platform.

Users can browse an auction, submit bids, and see the current highest bid and bid history update live. Traffic can be very high, especially for popular auctions and during the final 30 seconds. The system must preserve bid ordering per auction, reject invalid or stale bids, persist all bids and auction state transitions, and finalize the winning bid when the auction ends.

Discuss:

  • User-facing APIs for reading auctions, submitting bids, and subscribing to live updates.
  • The write path for bids under high contention.
  • The real-time push mechanism, such as SSE or WebSocket.
  • Storage choices for auction metadata, bid history, current highest bid, and event delivery.
  • Consistency, idempotency, ordering, failure handling, and scalability for hot auctions.

Submit Your Answer to Earn 20XP

Sign in to leave a comment

Loading comments...