Design a Cab-Sharing System for Daily Commute - System Design | WinJob

Problem Statement: Daily Cab-Sharing for Commuters

Design a cab-sharing commute platform like BlaBlaCar Daily, Waze Carpool, or Scoop at metro scale: recurring corridors, seat inventory, employer subsidies, and fair cost splits—not on-demand empty-car dispatch. This section covers problem statement: daily cab-sharing for commuters in the understanding phase.

Operational detail

Quantify detour minutes, batch coverage, and escrow timing before naming cloud SKUs. State AP for search ranking and CP for booking/seat holds with explicit failure stories (Treating commute search like nearest-driver GPS causes wrong architecture.).

Failure and edge cases

Treating commute search like nearest-driver GPS causes wrong architecture.

Interview checkpoints

javaOne Dark Pro

1 public record CommuteOffer(String offerId, String corridorId, int seatsLeft, Instant departUtc) {}

pythonOne Dark Pro

1 @dataclass(frozen=True)
2 class CommuteOffer:
3     offer_id: str
4     corridor_id: str
5     seats_left: int
6     depart_utc: str

typescriptOne Dark Pro

1 export interface CommuteOffer {
2   offerId: string;
3   corridorId: string;
4   seatsLeft: number;
5   departUtc: string;
6 }

Why interviewers care

a Cab-Sharing System for Daily Commute interviews reward crisp scope, explicit trade-offs, and failure stories—not generic microservice diagrams.

Interview checkpoint

Name one failure story for Problem Statement: Daily Cab-Sharing for Commuters that proves you understand real outages, not happy-path diagrams.

Key Highlights

•Unique angle for sec-01: Drivers publish fixed Mon–Fri home↔office corridors with seat caps
•Phase understanding: Riders join overlapping segments within a 8–12 minute detour budget
•Watch failure mode: Treating commute search like nearest-driver GPS causes wrong architecture

1	@dataclass(frozen=True)
2	class CommuteOffer:
3	offer_id: str
4	corridor_id: str
5	seats_left: int
6	depart_utc: str

1	export interface CommuteOffer {
2	offerId: string;
3	corridorId: string;
4	seatsLeft: number;
5	departUtc: string;
6	}