Design a multi-level parking system that tracks floors, parking spots, and vehicle types. Some vehicles may occupy multiple adjacent spots. Define core data models and APIs to handle vehicle entry and exit, spot allocation and release, and queries such as available spots by type and by floor.

This question evaluates system design skills including hierarchical data modeling, API design, stateful resource allocation, and concurrency control for a backend that manages multi-level parking resources.

How do I approach System Design interview questions?

System Design questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master system design interviews.

What difficulty level is this interview question?

This is a medium difficulty System Design question, commonly asked during Onsite rounds at DocuSign.

What role is this question designed for?

This question is commonly asked for Software Engineer candidates at DocuSign during technical interviews.

Design a multi-level parking system | DocuSign Interview Question

System Design: Multi‑Level Parking System

Context

Design the backend for a multi‑level parking facility. The system must track floors, rows, parking spots, and vehicle types. Some vehicles require multiple adjacent spots. The service should allocate and release spots on vehicle entry/exit and support queries for availability by vehicle/spot type and by floor.

Assume:

Vehicles: motorcycle, car, van/SUV, bus/truck (some may require k adjacent standard spots).
Spots: motorcycle, compact, regular, large, EV (flag for charging capability), each on a specific floor and row, with a sequential index for adjacency.
Adjacency means contiguous indexes within the same row.

Requirements

Define core data models (entities, relationships, key fields).
Define APIs for:
- Vehicle entry (allocate spot(s) and issue a ticket/allocation).
- Vehicle exit (release spot(s)).
- Queries: available spots by type and by floor; availability for a given vehicle type.
Address allocation for vehicles that need multiple adjacent spots.
Note key constraints, concurrency handling, and performance considerations.

Context

Assume:

Vehicles: motorcycle, car, van/SUV, bus/truck (some may require k adjacent standard spots).

Spots: motorcycle, compact, regular, large, EV (flag for charging capability), each on a specific floor and row, with a sequential index for adjacency.

Adjacency means contiguous indexes within the same row.

Requirements

Define core data models (entities, relationships, key fields).

Define APIs for:

Vehicle entry (allocate spot(s) and issue a ticket/allocation).
Vehicle exit (release spot(s)).
Queries: available spots by type and by floor; availability for a given vehicle type.

Address allocation for vehicles that need multiple adjacent spots.

Note key constraints, concurrency handling, and performance considerations.

Design a multi-level parking system

Quick Overview

System Design: Multi‑Level Parking System

Context

Requirements

Solution

Submit Your Answer to Earn 20XP

Design a multi-level parking system

Quick Overview

System Design: Multi‑Level Parking System

Context

Requirements

Solution

Submit Your Answer to Earn 20XP