Hot Agent Startup·Software Engineer·Onsite - System Design / Architecture
Apr 2026
Two-part system design session at a hot agent startup. Part A was a classic flight booking backend problem, Part B threw a high-QPS real-time voting scenario at me that I was not fully ready for. Solid questions, genuinely challenging if you haven't thought about concurrency and streaming in depth.
- Design the backend for a flight ticket booking system, including data models for flights, passengers, and bookings, relevant indexes, and how to handle concurrent booking without overselling.
- Walk through the end-to-end user flow for booking a flight and the backend queries involved at each step.
- Design a real-time voting system that can handle millions of votes per second during a short live event burst, with low-latency vote submission and a near-real-time results board.
- How would you deploy this voting system on Kubernetes or a managed container platform, including autoscaling under sudden traffic spikes?
“I started with the data model which felt safe, got through Flight, Passenger, and Booking tables pretty cleanly.” The rest of the author's notes on Software Engineer interview at Hot Agent Startup, 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