The hiring process
| Round | Format | What's tested |
|---|---|---|
| Online Assessment | ~60–90 min | DSA under time pressure |
| DSA / Problem-Solving Interview | ~60 min | Live coding and reasoning |
| System / High-Level Design | ~60–75 min | Designing for flash-crowd scale |
| Project / Tech Deep-Dive (Onsite) | ~45–60 min | Depth on what you have actually built |
| Hiring Manager / Culture Fit | ~30–45 min | Motivation and collaboration |
Process and cutoffs vary by drive/team and change over time — confirm on the official careers page.
Round-by-round: exactly what's asked & how to prepare
Online Assessment
~60–90 minTwo problems on a timed coding platform, usually medium-to-hard. You are judged on a correct, efficient solution and clean handling of edge cases, not just passing the visible tests. Time management across both problems matters.
- Sliding window / two-pointer on arrays and strings
- Graph traversal with a scheduling twist (BFS/DFS/topological order)
- Interval merging or heap-based selection
- Hashing to trade memory for time on large inputs
- Grind medium problems on LeetCode by pattern, not by count
- Rehearse writing bug-free code without an IDE's autocomplete
- Practice stating time/space complexity aloud before coding
- Use NeetCode's free roadmap to cover core patterns
- Brute-forcing the first problem and running out of time for the second
- Ignoring overflow, empty, and single-element edge cases
- Not testing mentally before submitting
- Optimal complexity reached without heavy hinting
- Clean, readable code with sensible variable names
- Proactively naming edge cases
DSA / Problem-Solving Interview
~60 minA live coding round where you narrate your approach, refine with the interviewer, and code the chosen solution. They probe why you picked a structure and what breaks at scale. Communication is scored alongside correctness.
- Rate limiting or leaderboard ranking as a coding problem
- LRU/LFU-style cache design in code
- Concurrency-safe counter or queue logic
- String/array manipulation with follow-up optimizations
- Practice thinking out loud on a whiteboard or plain doc
- Solve then optimize: always ask 'can this be faster or use less memory?'
- Review core structures (heaps, tries, union-find) from GeeksforGeeks
- Do 2–3 timed mock interviews with a peer
- Coding silently, leaving the interviewer guessing
- Rejecting hints instead of building on them
- Skipping a dry run of the final code
- Clear translation of idea to working code
- Receptive to feedback and iterates
- Justifies data-structure choices
System / High-Level Design
~60–75 minYou scope a system, state functional and non-functional requirements, estimate scale, and design the data and service layers. Given Dream11's traffic profile, expect deep questions on handling sudden spikes, hot keys, and consistency-versus-availability trade-offs. An alerting/monitoring or leaderboard-style prompt is common.
- Real-time leaderboard for millions of concurrent users
- Idempotent wallet/transaction service under retries
- Notification fan-out at match events
- Read-heavy caching with cache stampede protection
- Learn the estimation flow: users → QPS → storage → bandwidth
- Study caching, sharding, and message queues (Kafka) fundamentals
- Watch a few 'design a leaderboard / news feed' walkthroughs
- Read the free 'System Design Primer' on GitHub
- Jumping to a design before clarifying scope and NFRs
- Ignoring the flash-crowd / thundering-herd problem
- Hand-waving the database and consistency model
- Quantified capacity estimates
- Explicit trade-off discussion (CAP, consistency vs latency)
- Awareness of failure modes and degradation
Project / Tech Deep-Dive (Onsite)
~45–60 minAn engineer digs into a project from your resume: architecture, scale you handled, monitoring, on-call, and hard decisions you made. They test whether you truly owned the work versus rode along. Be ready to defend design choices.
- How your system was monitored and alerted
- A production incident and how you debugged it
- A trade-off you made and would revisit
- Scaling bottleneck you hit and resolved
- Write a one-page architecture summary for your top 2 projects
- Prepare metrics: latency, throughput, scale, uptime
- Rehearse one incident story using a structured format
- List trade-offs and what you would change now
- Vague answers that hide your actual contribution
- Claiming ownership you cannot defend under follow-ups
- No numbers to describe scale or performance
- Genuine ownership and depth
- Comfort discussing failures honestly
- Sound engineering judgment
Hiring Manager / Culture Fit
~30–45 minA conversation on why Dream11, how you handle failure and disagreement, and how you work in a team. It is a genuine filter, not a formality. Situational questions are common.
- Handling a project that failed or slipped
- Disagreeing with a teammate or lead
- Why Dream11 and fantasy sports specifically
- Working under high-stakes, high-traffic pressure
- Prepare 3–4 STAR stories (conflict, failure, ownership, impact)
- Research Dream11's scale and engineering blog
- Have a genuine reason for wanting this role
- Prepare thoughtful questions for the manager
- Generic 'I want to grow' answers
- Blaming others in failure stories
- No questions for the interviewer
- Self-awareness and accountability
- Authentic interest in the domain
- Team-first mindset
What to master
- Data structures & algorithms
- Distributed systems & scaling
- Caching and CDNs
- Message queues (Kafka)
- Databases: SQL, NoSQL, sharding
- Concurrency & idempotency
- Monitoring & observability
- System design trade-offs
Eligibility
open — role-based (SDE-1 through SDE-3; scale expectations rise with level)
Dream11 salary & compensation (2026)
Top-paying Indian consumer-tech (Dream Sports); strong cash + ESOPs, benchmarks near the best Indian product firms.
| Role / Level | Experience | India — total CTC | US — total comp | What to know |
|---|---|---|---|---|
| SDE 1 (new grad) | 0–2 yrs | ₹22–34 LPA | — | base + ESOPs |
| SDE 2 | 2–4 yrs | ₹34–55 LPA | — | ESOP grants grow |
| SDE 3 / Senior | 4–8 yrs | ₹55–90 LPA | — | large ESOP component |
| Staff / Lead SDE | 8–12 yrs | ₹90 LPA–1.5 Cr | — | scope-driven |
| Principal / EM | 12+ yrs | ₹1.5–2.5 Cr | — | rare senior band |
How the package is structured
- Cash comp is high for the Indian market and ESOPs add meaningful upside given profitability.
- Handling extreme scale (peak IPL traffic) is valued and speeds promotion.
- Level jumps (SDE2→SDE3→Staff) are the main comp accelerators.
- Negotiate ESOP grant size and understand the liquidity/buyback program.
Indicative 2026 market ranges aggregated from public sources (levels.fyi, Glassdoor, AmbitionBox, candidate reports). Compensation varies widely by location, team, level calibration, and negotiation — use these as directional benchmarks, not guarantees.
Your prep plan
- Week 1: drill DSA by pattern (arrays, graphs, heaps, DP) with daily timed sets
- Week 1: write architecture one-pagers for your two strongest projects
- Week 2: do 3 system-design mocks focused on high-concurrency systems
- Week 2: study caching, sharding, and Kafka basics deeply
- Prepare 4 STAR stories covering failure, conflict, ownership, impact
- Read Dream11's engineering blog to speak to their real scale challenges
Want this plan dated to your interview?
Upload your resume and tell Whis your interview date — get a personalized, day-by-day plan built around your gaps, then run Whis live in the interview.
Get my personalized planFrequently asked questions
Is Dream11 mostly a DSA company or a design company?
Both, but for SDE-2 and above the system design and project deep-dive rounds carry decisive weight because the platform's flash-crowd traffic is its defining engineering problem.
Do I need to know their exact tech stack (Java, Go, Kafka, Kubernetes)?
Not exact syntax, but you should be able to reason about queues, caching, and container orchestration conceptually. Familiarity helps in the deep-dive round.
How hard is the coding bar?
Medium-to-hard. Optimal solutions with clean edge-case handling are expected, and slow brute-force answers rarely pass the online round.