Autocoder

Dream11 Interview Questions and Answers

Last updated 2026-11-19

Dream11 is a fantasy sports platform, and a platform of that kind has an unusual load pattern: very quiet for hours, then millions of users arriving in the minutes before a match starts and all watching points change at once. Engineering interview questions around it therefore tend to focus on spikes, real-time updates, leaderboards and wallet correctness. This page gives practice questions with worked answers on those themes, plus HR.

These are practice questions on topics typical of high-concurrency consumer backends, not a record of what anyone was asked. For code see Dream11 coding round questions. General preparation is in how to crack a technical interview.

ProcessNot published; confirm with the recruiter
ThemesSpikes, real-time updates, leaderboards, wallets

What we can say about the process

Dream11 does not publish its interview rounds and we have no sourced description of them, so this page does not claim a specific round structure. Product companies of this kind commonly combine data structures, design and behavioural conversations, but confirm the actual steps with the recruiter who contacts you.

Hiring status

We have no sourced hiring statements for Dream11 to quote, and this site has no Dream11 page under /hiring. Check the careers page on the company's official website for current roles, and treat any date or number you see on third-party sites as unconfirmed until it appears there.

How to prepare

Practise reasoning about peaks. For every design answer, say what the peak load is, which component saturates first, and what you do when it does: queue, cache, shed or scale. Interviewers for spike-heavy systems listen for that.

Dream11 Interview Questions and Answers: questions with worked answers

  1. 1

    How would you design a live leaderboard for a contest with millions of participants?

    hard

    Keep scores in a sorted structure such as a Redis sorted set per contest, updated as points change, which gives rank lookup and top-N in logarithmic time. For millions of entries shard by contest and by score range, and compute a user's rank on demand from the shard counts. Update in batches every few seconds rather than per event, since users cannot see millisecond changes, and serve the top ranks from a cache.

  2. 2

    Live match events change every player's points. How do you recompute team scores efficiently?

    hard

    Process events through a stream, and compute player points once per event with the scoring rules. Each user team is a set of players, so team score is the sum of its players' points. Instead of rescoring every team on each event, store per-player points and update team totals by the delta for teams that include that player, using an inverted index from player to teams, in parallel batches.

  3. 3

    How do you handle a traffic spike just before a match deadline?

    hard

    Pre-scale before known matches, since the schedule is known. Put a queue in front of team creation, cache static data, make writes cheap and idempotent, and degrade non-essential features. Load test at the expected peak and above, and rate limit per user. Use backpressure, returning a friendly retry rather than letting databases saturate.

  4. 4

    Design wallet debits for contest entry so no one enters twice or goes negative.

    medium

    A conditional update on the wallet row (balance >= fee) in the same transaction that records the contest entry under a unique key of user and contest. If the entry insert fails because it already exists, the whole transaction rolls back. Use a ledger of immutable entries for audit and refunds, and an idempotency key for the client retry.

  5. 5

    How would you design the contest join flow to prevent oversubscription?

    medium

    A contest has a capacity. Use an atomic counter in a fast store with a conditional increment, or a database conditional update, so the last seat goes to exactly one user. If the contest fills, create or route to a similar contest. Release seats if payment fails, with a short reservation expiry.

  6. 6

    Explain how you would cache match data.

    medium

    Match fixtures, squads and static player info change rarely, so cache them with long TTLs and event-based invalidation. Live data such as scores should be updated by a producer into the cache, so readers never hit the database. Add request coalescing so many misses collapse into one recompute and avoid a stampede.

  7. 7

    Which delivery mechanism would you use to push live points: polling, WebSocket or server-sent events?

    medium

    Points flow one way from server to client, so server-sent events are simple and efficient and work well over HTTP infrastructure. WebSockets are justified for two-way interaction. Polling is the fallback when connections are blocked, and with a short cache in front it scales acceptably. Whatever you choose, send deltas and let clients resync on reconnect.

  8. 8

    What are the trade-offs of Kafka versus a simple queue for score events?

    medium

    A log-based system such as Kafka keeps ordered, replayable events per partition, lets multiple consumers read independently, and handles very high throughput, at the cost of operational complexity and partition-level ordering only. A simple queue is easier and good for task distribution, but replay and multiple independent consumers are harder. For match events, order per match matters, so partition by match id.

  9. 9

    How do you design for fairness and fraud, such as one person with many accounts?

    hard

    Combine signals: device and payment instrument linkage, behaviour patterns, and rule-based and model-based risk scores, applied at signup, deposit and withdrawal. Hold suspicious withdrawals for review, keep an audit trail, and give users a clear appeal route. Do not rely on a single signal because each has false positives.

  10. 10

    Tell me about a time something broke at the worst moment.

    easy

    Use STAR. Describe the incident and its stakes, how you contained it first, how you communicated, the root cause and the specific change that prevents recurrence. Calm, accountability and learning matter more than the size of the failure.

  11. 11

    Why this company, and are you comfortable with on-call and peak-time pressure?

    easy

    Be honest. Connect your interest to real-time systems and scale. On pressure, give an example of working through a high-stakes release or an on-call incident, and what habits kept you effective, such as runbooks and clear handoffs.

Frequently asked questions

What rounds does Dream11 have?

We have no sourced description of its rounds. Ask your recruiter and prepare for data structures, design and behavioural conversations.

Which topics fit a fantasy platform best?

Leaderboards, stream processing, caching, wallet consistency and handling peak traffic.

Where can I find Dream11 openings?

On the careers page of the company's official website. This site has no sourced Dream11 hiring statements.

Do I need sports knowledge?

Not for engineering roles, but understanding how a contest and scoring work helps you reason about design questions.

Related guides

More in Company Interview Questions

See all in this section