Design an online polling app
Let anyone create a poll, share the link and watch votes come in live, like Strawpoll.
Functional requirements
- Create a poll with up to 10 options
- Vote once per poll
- See live results
Non-functional requirements
- Votes are counted accurately
- Results update within 2 seconds
- Viral polls stay fast
Scale
- 1M polls created per day
- A viral poll can get 50K votes per second
- Results are read far more than votes are cast
How you’ll be scored
8 checks covering your diagram and your notes, and any valid approach counts. Hints appear for anything you miss. Common mistakes, such as single points of failure or components you never explain, cost points. How grading works
What interviewers look for
- Clarify before you draw. State what is in and out of scope. For “Design an online polling app”, that starts with: Create a poll with up to 10 options; Vote once per poll; See live results. Interviewers notice candidates who pin the requirements down first.
- Turn the scale into numbers. The scale (1M polls created per day; A viral poll can get 50K votes per second; Results are read far more than votes are cast) should become requests per second, storage and bandwidth, and those figures should drive your choices. Estimates with units carry more weight than adjectives.
- Show how each quality is met. Your design should visibly deliver: Votes are counted accurately; Results update within 2 seconds; Viral polls stay fast. Saying that it does isn’t enough; point to the part of the design that makes it true.
- Expect follow-ups on the hard parts. Interviewers usually probe counters, queues and spikes here. This is an easy problem, so interviewers expect the fundamentals done cleanly: a clear request path, the right kind of data store, and a reason for each component.
- Explain failure and trade-offs. Say what happens when a component fails, where a single point of failure would hurt, and what you chose not to build. Naming a trade-off is a stronger answer than claiming there isn’t one.