Design a real-time airport gate & runway allocation platform
PremiumBackend systemHard
- Event driven
- Workflow orchestration
- Concurrency control
Quick answer
This backend system interview question asks you to design a real-time airport gate & runway allocation platform. Aim for a design that meets its requirements at the stated scale, then explain its main components, data flow and trade-offs. Interviewers want to see how you scope the problem, size it and defend each choice.
The problem
Design a multi-tenant SaaS platform used by major global airports to dynamically allocate and monitor gates, runways, and ground resources.
The system continuously ingests real-time flight telemetry (e.g., ETA updates, landed, departed). When a flight is delayed, it often creates a cascading resource conflict (e.g., two aircraft needing the same gate). The platform must detect these conflicts and automatically trigger a constraint-optimization engine to calculate a new gate and runway assignment plan. Simultaneously, Airport Operations Center (AOC) dispatchers use the platform to manually override assignments for emergencies. All schedule changes must be strictly consistent and instantly broadcast to ground crews.
What must a real-time airport gate & runway allocation platform do?
- Telemetry Ingestion: Continuously accept structured flight status events (ETA changes, location pings, phase updates).
- Conflict Resolution: If an event causes a resource conflict, asynchronously orchestrate the solver library to compute a new allocation graph for that airport.
What scale should you design for?
Use these numbers in your estimates.
The scale numbers unlock with this questionUnlock
Key concepts
- Event driven
- Workflow orchestration
- Concurrency control
- Pub sub
- Real time processing
How you’ll practise
- Requirements
- Estimate
- API and data
- High-level design
- Deep dives
- Wrap-up
Lala, personalized to you, gives a hint when you ask and reviews your design when you are ready.
What do interviewers look for?
In any backend system design round.
- Clarifies the requirements before drawing anything
- Uses a few numbers that actually change the design
- Draws a clear path from the client to storage
- Picks storage and caching with reasons, not by habit
- Explains what breaks first under load and how to fix it
- States trade-offs openly instead of claiming a perfect design
Questions people ask about this interview question
- Which design type is this question?
- It is a backend system question. You design a real-time airport gate & runway allocation platform and explain your choices the way you would in an interview.
- Is this question asked at entry level?
- It is marked Hard. It suits engineers preparing for senior interviews, where you are expected to drive the discussion and go deep on trade-offs.
- What should I cover first?
- Start with the requirements: what the system must do, how well it must do it and which numbers change the design. Agree on scope with the interviewer before you design anything.
- Can I practise it for free?
- It is a premium question. Sign up and unlock it once for 10 credits; it then stays unlocked. When you finish, Lala, your personalized AI mentor, can review your design for 30 credits.
Related questions
Updated · Written by the SevyDevy team