Flipster·Software Engineer·Onsite - System Design / Architecture
Apr 2026
Flipster system design round, focused entirely on a parking lot OOP problem that went way deeper than I expected. Thought it'd be a quick class diagram exercise but they kept pushing on concurrency, EVs, and reservations.
- Design a parking lot system: walk through the class hierarchy (ParkingLot, Level, Spot, Vehicle types, Ticket), how spot types are assigned, and the full entry and exit flow including payment.
- How would you handle concurrency when multiple entry and exit gates are operating simultaneously on the same parking lot?
- How would you extend the design to support electric vehicle charging spots, and what changes would that require to your existing class structure?
- How would you add a reservation system to the parking lot, where users can book a spot in advance?
“I jumped straight into the class diagram which felt right, but I fumbled the spot assignment policy for a few minutes.” The rest of the author's notes on Software Engineer interview at Flipster, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.
View Post