Design a blood bank & emergency donor matching platform
PremiumBackend systemMedium
- Geospatial routing
- Inventory management
- Notification fan out
Quick answer
This backend system interview question asks you to design a blood bank & emergency donor matching 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 Blood Bank & Emergency Donor Matching Platform used by regional hospital networks and blood donation centers. The platform manages a registry of 2 million voluntary donors (tracking their blood type, last donation date, and home/work GPS location) alongside real-time inventory across 500 hospital blood banks.
When a hospital submits an urgent emergency request for a rare blood type (e.g., O-negative), the system must instantly query for eligible donors within a specified geographic radius (e.g., 10km) who are medically eligible to donate. Simultaneously, the system must check if any nearby blood bank has unallocated inventory approaching its expiration date. The system must fan out emergency push notifications to matched donors while updating the emergency request dashboard.
What must a blood bank & emergency donor matching platform do?
- Donor Registry: Store donor profiles, medical eligibility status, blood type, and last known locations.
- Inventory Tracking: Record blood bag stock levels, blood types, collection timestamps, and 35-day expiration dates across all participating blood banks.
What scale should you design for?
Use these numbers in your estimates.
The scale numbers unlock with this questionUnlock
Key concepts
- Geospatial routing
- Inventory management
- Notification fan out
- Event driven
- 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 blood bank & emergency donor matching 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