← BlackRock Interview Insights

BlackRock·Software Engineer·Onsite - System Design / Architecture·Intermediate

IntermediatePrefer not to say
Jun 2026

Summary

BlackRock system design round for a software engineering role. One meaty OOP question that branched out pretty far once they started asking about extensions.

Questions Asked (1)

Q1

Design a parking lot system that handles multiple vehicle types (motorcycle, car, truck) with appropriately sized spots, multiple floors, ticket generation on entry, fee calculation on exit, and logic for finding available spots. Walk through the class hierarchy, key APIs, and how you'd extend it to support reservations or real-time availability.

System DesignData ModelingTechnical Trade-offs
Author's notes

Spent the first few minutes just laying out the class structure: Vehicle as a base with subtypes, ParkingSpot sized accordingly, ParkingLot holding multiple Levels.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements and constraints, then design a clean class hierarchy with core entities like Vehicle, ParkingSpot, Level, and Ticket. Walk through key APIs for entry, exit, and spot finding, and discuss extensibility for reservations and real-time availability using appropriate data structures and design patterns.

Pro tip: Emphasize separation of concerns and extensibility: use interfaces and the Strategy pattern for fee calculation and spot allocation, and mention how you'd handle concurrency and persistence for real-time availability.

1. Clarify Requirements and Scope

Ask about expected scale, vehicle types, spot sizes, pricing models, and whether reservations or real-time updates are needed. Confirm assumptions before diving into design.

2. Define Core Entities and Class Hierarchy

Outline classes like Vehicle (with subclasses Motorcycle, Car, Truck), ParkingSpot (with size and type), Level, ParkingLot, Ticket, and Payment. Use inheritance and composition appropriately.

3. Design Key APIs and Spot Allocation Logic

Specify methods for entry (issue ticket, assign spot), exit (calculate fee, free spot), and finding available spots (by type and level). Discuss data structures like maps or lists for efficient lookup.

4. Address Fee Calculation and Payment

Explain how fees are computed based on duration and vehicle type, possibly using a Strategy pattern. Mention integration with payment systems and ticket validation.

5. Discuss Extensibility and Trade-offs

Describe how to extend for reservations (e.g., Reservation class, booking API) and real-time availability (e.g., observer pattern, caching, concurrency control). Highlight trade-offs in consistency, latency, and complexity.

Key Points to Mention

  • Class hierarchy with inheritance for vehicles and spots, and composition for levels and tickets
  • Use of design patterns: Strategy for fee calculation, Factory for spot creation, Observer for real-time updates
  • Efficient spot finding using data structures like hash maps or priority queues, and handling concurrency with locks or optimistic locking
  • Ticket generation with unique IDs and timestamps, and fee calculation based on duration and vehicle type
  • Extensibility for reservations: adding Reservation entity, booking API, and handling overbooking
  • Real-time availability: push notifications, caching, and consistency trade-offs (e.g., eventual vs strong consistency)

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.