Design a real-time global crisis response coordination platform
PremiumBackend systemHard
- Geospatial routing
- Real time processing
- Pub sub
Quick answer
This backend system interview question asks you to design a real-time global crisis response coordination 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 Real-Time Global Crisis Response Coordination Platform. During natural disasters and large-scale emergencies, multiple disparate organizations (hospitals, FEMA, NGOs, military logistics) must coordinate life-saving operations in a shared operational environment.
The platform tracks the live geospatial locations of field assets (ambulances, supply trucks, helicopters, search-and-rescue teams). Command center dispatchers use live maps to monitor these assets and issue critical resource allocations (e.g., "Dispatch Medical Team A to Incident B" or "Claim Supply Pallet C"). The system must ingest massive telemetry streams, prevent multiple agencies from claiming the same exclusive resource, and fan out live map updates to thousands of operational dashboards simultaneously without delay.
What must a real-time global crisis response coordination platform do?
- Asset Tracking: Ingest continuous geospatial heartbeat telemetry from active field resources globally.
- Situation Awareness: Serve live map dashboards to command centers, automatically updating asset locations within their current viewport (bounding box).
What scale should you design for?
Use these numbers in your estimates.
The scale numbers unlock with this questionUnlock
Key concepts
- Geospatial routing
- Real time processing
- Pub sub
- Concurrency control
- High availability
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 global crisis response coordination 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