Real, anonymous reports from people who interviewed for Software Engineer at Dream11, newest first and distilled into what to expect across the loop.
After a recruiter call, about a week later I went through a fairly structured set of rounds that felt medium-to-hard overall. The loop ran four rounds total, and it was split between two technical rounds, one techno-managerial round, and an HR round. The technical side leaned into both designing features and the fundamentals—things like OS, OOPS concepts, and database topics (DBMS, SQL, and even NoSQL).
My process started with a DSA round that immediately set the pace—focused purely on problem-solving with typical array-based and combinational patterns. I remember being asked to find the least difference in occurrence of two numbers x and y in an array, with the assumption that both appear at least once. Then I had to tackle a subset-sum style problem where the task was to determine subset combinations that hit a target sum k. There was also a third DSA prompt in the same round that asked about whether an a could satisfy a condition in a string/number context.
The interview process typically consists of multiple rounds, including a coding assessment, technical interviews focused on algorithms and design, a hiring manager round, and an HR discussion. Expect a structured flow that assesses both technical skills and cultural fit.
Candidates should prepare for a strong emphasis on data structures and algorithms (DSA), with questions often drawn from common patterns and LeetCode-style problems. Expect to demonstrate problem-solving skills under time pressure.
Interviews will also include low-level design and system design components, where candidates must articulate their design choices and reasoning for scalable architectures and implementation strategies. Be ready to discuss design patterns and trade-offs.
Some rounds will assess how candidates align their engineering decisions with product and leadership expectations, focusing on past experiences and how they relate to the role. Prepare to discuss your resume and decision-making processes.
Candidates have reported mixed experiences with communication post-interview, with some feeling a lack of follow-up or clarity regarding outcomes. It's advisable to manage expectations around feedback and timelines.
The overall difficulty of the interviews is generally medium to hard, with a clear expectation for consistency across technical evaluations. Candidates should prepare thoroughly across all technical areas to avoid gaps in knowledge.