
Synthesized from 24 candidate submissions for ALL.
The SDE-2 role at Dream11 targets mid-level engineers with 3-5 years of experience, focusing on scalable system design, database internals, and advanced DSA problems. The process is highly structured, with 5-6 rounds covering coding, database, system design, managerial, and HR discussions. Candidates are expected to demonstrate depth in trade-offs (e.g., consistency vs. availability) and practical experience with high-load systems.
Sources: Aggregated from 12 candidate experiences.
The SDE-3 role at Dream11 is for senior engineers (5+ years of experience) with a focus on leading architectural decisions, mentoring, and high-level system design. The process is highly technical, involving machine coding, database deep dives, and cross-functional discussions.
Sources: Aggregated from 2 candidate experiences.
The SDE-1 role at Dream11 is designed for entry-level engineers (0-2 years of experience), with a focus on fundamental DSA, problem-solving, and basic system design. The process is shorter (3-4 rounds) but technically demanding, emphasizing clean code, scalability basics, and cultural fit.
Sources: Aggregated from 7 candidate experiences.
The Data Science/ML role at Dream11 targets candidates with 1-4 years of experience in machine learning, statistical modeling, and system design for ML applications. The process evaluates theoretical knowledge, practical case studies, and ability to design scalable ML systems.
Sources: Aggregated from 3 candidate experiences.
The candidate underwent a thorough five-round interview process for the SDE-2 position at Dream11, including DSA, database, system design, managerial, and HR rounds. The process was well-organized, with the first two rounds conducted virtually and the remaining three in Dream11's Mumbai office. The candidate received an offer, highlighting a positive outcome.
This round focused on Data Structures and Algorithms (DSA), where the candidate was asked to solve 2 problems within 1 hour. The problems involved using maps with string keys and lists, and manipulating a numeric string to remove specific digits to achieve the smallest possible number. The interviewer provided hints and support.
Solve a problem involving maps with string keys and lists, requiring binary search implementation.
Given a numeric string and a number k, remove k digits from the string to make the resulting number the smallest possible.
This round focused on database concepts and a deep dive into the candidate's resume. The interviewer explored past experiences, design choices, tech stack used in previous projects, and asked detailed questions about PostgreSQL (concurrency control, isolation levels, locks, replication, scaling reads and writes), reactive stack (Netty and R2DBC), and system design (e.g., implementing a ticket booking system like BookMyShow).
Describe a project you are currently working on and the design choices made.
Explain PostgreSQL concurrency control, isolation levels, locks, and replication.
How would you scale PostgreSQL reads and writes?
Explain how Netty and R2DBC work in a reactive stack.
How would you implement a ticket booking system like BookMyShow at scale?
How would you ensure that when a person selects a seat, others cannot see it?
This round assessed the candidate's system design skills. The interviewer asked to design an alerting and monitoring system like Prometheus and Grafana. The discussion included defining scope, non-functional and functional requirements, estimating scale, database storage layer, consistency vs. availability trade-offs, timeseries data storage format, and how Prometheus server detects new pods for scraping metrics. The interviewer also asked about maintaining active web connections with many clients.
Design an alerting and monitoring system like Prometheus and Grafana.
Define scope, NFRs, FRs, and estimate scale for the system.
How will timeseries data be stored and in what format?
How will Prometheus server know to start scraping metrics from a new pod?
How will you maintain active web connections with many clients to scrape metrics?
This round was taken by a Vice President of Dream11 with over 8 years of experience. The interviewer focused on the candidate's past work experience and posed scenario-based questions to understand their mindset and problem-solving approach. The discussion was non-technical and revolved around handling challenging situations.
How would you prepare your system for IPL given that it is coming?
Explain the SDLC process you follow to develop a feature.
What is the most challenging problem you have solved in Navi? What was your contribution?
How do you keep yourself updated with new technologies?
What is the procedure you follow to solve any incident/bug in your company?
Questions based on the candidate's resume.
This round was conducted by an experienced HR with over 13 years of experience. The discussion focused on the candidate's personal background, schooling, college experiences, interest in coding, reasons for leaving their current company, and future perspectives.
Discuss childhood, schooling, college experiences, and interest in coding.
Reasons for wanting to leave the current company.
Candidate's future perspectives and goals.
The candidate underwent a multi-round interview process for an SDE-2 role at Dream11, including technical rounds (DSA and database internals), system design, managerial, and HR rounds. The process concluded with an offer, and flights were arranged for in-person rounds in Mumbai.
Two LeetCode medium problems were asked. The first involved connected components and DFS, requiring an optimized solution. The second was related to prefix sums, where a brute-force solution was initially provided, and hints were needed to reach the optimized solution.
Connected components + DFS related question
Prefix sum related question
The round focused on datastores and their internals. Topics included database migration strategies, 2-phase commit and coordinator failure handling, database sharding strategies, replication problems, isolation levels, and scaling strategies for an overloaded Kafka queue.
Challenging project/feature discussion
Database migration from one SQL vendor to another
2-phase commit practicality and coordinator failure handling
Database sharding strategies
Database replication problems and leader failure handling
Preventing duplicate seat selections in a booking system (e.g., BookMyShow)
Scaling an overloaded Kafka queue and rebalancing strategies
Designed a stock broker system, covering functional and non-functional requirements, expected load, concurrency, and resiliency. Every design choice was critically evaluated with questions on reasoning and alternatives.
Resume-based questions and discussion on the SDLC lifecycle, along with scenario-based questions.
General discussions on life and CTC expectations.