Design a pickup-area driver queue

Read the full interview experience this question came from →

Quick Overview

This question evaluates a candidate's ability to design real-time, stateful distributed systems with emphasis on API design, data modeling, event ingestion, queue ordering rules, consistency models, scalability, fault tolerance, and observability in the System Design domain.

Design a pickup-area driver queue

Company: Uber

Role: Software Engineer

Category: System Design

Difficulty: medium

Interview Round: Onsite

Design an internal service for a ride-hailing company that maintains a driver queue for each pickup area, such as an airport pickup zone or staging lot. When a driver enters the area, the driver should be added to that area's queue. When the driver leaves the area, goes offline, or becomes ineligible, the driver should be removed. Internal consumers should be able to query the current queue for a given pickup area and see the ordering of drivers. Discuss the API design, data model, event ingestion, queue ordering rules, consistency model, scalability, fault tolerance, and observability.

Overview: This question evaluates a candidate's ability to design real-time, stateful distributed systems with emphasis on API design, data modeling, event ingestion, queue ordering rules, consistency models, scalability, fault tolerance, and observability in the System Design domain.

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

|Home/System Design/Uber
Uber logo
Uber
Feb 22, 2026
mediumSoftware EngineerOnsiteSystem Design
27
0

Design an internal service for a ride-hailing company that maintains a driver queue for each pickup area, such as an airport pickup zone or staging lot. When a driver enters the area, the driver should be added to that area's queue. When the driver leaves the area, goes offline, or becomes ineligible, the driver should be removed. Internal consumers should be able to query the current queue for a given pickup area and see the ordering of drivers. Discuss the API design, data model, event ingestion, queue ordering rules, consistency model, scalability, fault tolerance, and observability.

Submit Your Answer to Earn 20XP

Sign in to leave a comment

Loading comments...