Mock Interviewer

Ask Coach

Ask Coach
Clarify requirements before you design — kept separate from your stage notes.

Tap a question to start, or type your own below.

Parking Lot System Design

Visual Problem Diagram

Parking Lot System Design architecture diagram

Scenario

Saturday mall rush: entry gates disagree with payment kiosks on whether level 3 is full because spot counts updated eventually. The OOD parking lot interview still needs concurrency on spots, ticket state, and payment—at scale add multi-entry coordination.

Design a parking lot system managing entry, spot assignment, hourly pricing, and exit payment. At interview scope start with clear entities and state machines; if scaled, atomic spot assignment prevents double booking.

You should support vehicle entry, spot types, ticketing, payment, and availability display. Be ready to explain concurrency control on spots and fee calculation.

Constraints

Functional

Enter/exit, assign spot by type, hourly/dynamic pricing, payment, availability display

Non-functional

No double booking spots, < 2s entry gate response, payment idempotent

Scale

Single lot thousands spots; multi-lot city scale shards by lot_id

Stages ahead

1Requirement Analysis
2API Design
3High-Level Design
4HLD Extensions
5Trade-offs

Log in to start practicing

Preview the problem below. Sign in to start your timed session, save progress, and use the AI coach.