Design a real-time election results aggregation & verification platform
PremiumBackend systemHard
- Cqrs
- Distributed ledger
- High availability
Quick answer
This backend system interview question asks you to design a real-time election results aggregation & verification 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 Election Results Aggregation & Verification Platform for a large national democracy. The system acts as the central source of truth on election night, collecting ballot counts from distributed polling centers, verifying their cryptographic and logical integrity, and updating national and regional totals.
When polls close, electronic systems at polling centers submit batch results (e.g., "Polling Station #42: Candidate A: 500, Candidate B: 450"). Your platform must securely ingest these results, detect anomalies (e.g., more votes than registered voters, invalid cryptographic signatures), and orchestrate a workflow where valid results immediately update public totals, while suspicious results are quarantined for human audit. Simultaneously, the platform must serve these live aggregates to millions of citizens and media outlets with extreme reliability.
What must a real-time election results aggregation & verification platform do?
- Secure Ingestion: Receive and durably store batch result payloads from polling stations, verifying cryptographic signatures.
- Anomaly Detection & Quarantine: Evaluate incoming results against logical rules. Route valid results to aggregation and quarantine anomalous results for manual review.
What scale should you design for?
Use these numbers in your estimates.
The scale numbers unlock with this questionUnlock
Key concepts
- Cqrs
- Distributed ledger
- High availability
- Stream processing
- Security
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 election results aggregation & verification 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