Design a global volunteer coordination platform
PremiumBackend systemMedium
- Geospatial routing
- Resource allocation
- Notification fan out
Quick answer
This backend system interview question asks you to design a global volunteer 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 Global Volunteer Coordination Platform used by international NGOs and humanitarian organizations. The platform manages a global pool of volunteers, tracking their skills (e.g., medical, logistics, translation) and their last known locations.
During steady-state operations, the system handles routine community event sign-ups. However, during a crisis (e.g., a natural disaster), coordinators must instantly query the system to find eligible volunteers within a specific radius of the incident who possess necessary skills. The system must immediately broadcast emergency notifications to these matched volunteers. As volunteers receive the alert, they surge into the system to claim specific, capacity-limited shifts (e.g., "Medical Tent A - Needs 50 Doctors").
What must a global volunteer coordination platform do?
- Volunteer Profiles: Store and update volunteer attributes, including certified skills and last-known GPS location.
- Geospatial Skill Matching: Allow coordinators to query for volunteers by combining a geographical radius (e.g., 50km from an epicenter) and a list of required skills.
What scale should you design for?
Use these numbers in your estimates.
The scale numbers unlock with this questionUnlock
Key concepts
- Geospatial routing
- Resource allocation
- Notification fan out
- Concurrency control
- Event driven
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 global volunteer coordination platform and explain your choices the way you would in an interview.
- Is this question asked at entry level?
- It is marked Medium. Entry-level engineers can practise it, but it expects you to reason about requirements and trade-offs, not only list components.
- 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