What Is the Dream11 Interview Process Like? (Round by Round)

Candidates report five rounds for experienced engineering roles at Dream11. The first two rounds are held online. The remaining rounds are held at the Mumbai office, and candidates report that flights and cabs are arranged for them.

The reported order is a coding round, a database and project round, a high level design round, a hiring manager round, and an HR round. Candidates describe every round as an elimination round. Reported end to end time runs from about two weeks to about five weeks.

Quick Overview

Stage 1: The Coding Round

This round is a data structures and algorithms test. Candidates report two problems in some loops and three in others. Reported problems include Minimum Path Sum and First Missing Positive, which are both standard grid and array questions. Some reports name HackerRank as the platform, some say the problems were served through LeetCode, and other reports name no platform at all.

Interviewers ask for the time and space cost of each solution. Candidates also report being asked to dry run the code on a test case while explaining the logic aloud. For the general shape of a screening test, see what an online technical assessment is.

Stage 2: Database and Project Round

This round is a detailed examination of work you have already done. Candidates report explaining the full architecture of a past project, then drawing its database schema in a shared drawing tool. Reported follow up topics include MySQL isolation levels, pessimistic and optimistic locking, indexing, content delivery networks, and load balancers.

An isolation level is the rule that decides how much of one running transaction another transaction can see. Choose a project where you made the schema decisions yourself, because the questions are asked at that level of detail.

Stage 3: High Level Design Round

Candidates report this round is held in person, and several describe it as a discussion rather than a test. The most specific reported question asks you to design the system that sends lineup notifications to users about thirty minutes before a match starts. The reported constraints matter more than the diagram. The same system must work when a thousand users have joined a contest and when millions have.

Input arrives from two Kafka streams, one for users joining a contest and one for lineup information. Kafka is a system that stores ordered streams of events for other services to read. Other candidates report being asked to design the Dream11 leaderboard and the Dream11 wallet. The full topic list is in what to expect in the Dream11 system design interview.

Stage 4: Hiring Manager Round

Candidates report situational questions, a detailed review of the resume, and further questions about past projects. Reported topics include how you monitor a service, which metrics you watch, and how you think about payment flows. Several candidates report that this round is where they were rejected, so prepare it as a technical round and not only as a conversation.

Stage 5: HR Round

The final reported round covers motivation, culture fit, willingness to relocate to Mumbai, and notice period. Dream11 publishes five values: Data Obsessed, Ownership, Performance, User First, and Transparency. Prepare the motivation question with how to answer why Dream11.

How the Frontend Loop Differs

Candidates on the frontend track report a different second round. They report a machine coding round combined with JavaScript questions. A machine coding round is a timed session where you build small working code instead of discussing a design.

One reported task was writing a polyfill of Promise. Reported discussion topics include closures, call, apply, bind, and async and await. A later reported round covered React and React Native performance.

How the Campus Path Differs

Freshers hired through campus placement report a shorter loop. Reports describe an online coding test, then technical rounds, then an HR conversation. Round names and eligibility rules vary by campus, so confirm your own schedule with the placement cell.

Timeline and Decision

Reported timelines vary widely. One candidate reports about ten days between the coding round and the database round, then about three weeks before the onsite in Mumbai. Another reports the whole process in about two weeks.

Candidates for junior roles report one to two days between rounds in some loops. Because three rounds are held in Mumbai, arranging travel adds time for candidates in other cities. More detail is in how long it takes to hear back after a Dream11 interview.

Questions to Ask Them

Every round ends with time for your questions, so prepare three. Good questions here concern traffic peaks around match start, how on call works during a tournament, and how a team measures whether a feature succeeded. Ask how much of the system one engineer owns, because reports describe wide ownership. A specific question also shows that you studied the product.

How to Prepare

• Drill the patterns, not single problems. Grokking the Coding Interview covers the grid, array, and graph patterns behind the reported questions.
• Rehearse one project in full depth. Write out its schema, its failure cases, and the decisions you made alone.
• Study real time systems. Grokking the System Design Interview covers the queues, caches, and databases the design round uses.
• Prepare the behavioral answers early. The hiring manager round rejects candidates, so treat it as seriously as the coding round.