Academic snapshot
Floor: Often 7.0 / 70%
Degrees: B.Tech/B.E./M.Tech/MCA
Backlogs: None active
Year: Final year / recent grad
Dream11 Placement Papers 2026
Dream11 is India’s largest fantasy sports platform, where millions of users build teams and compete during live cricket and other sports. Founded in 2008, its engineering teams tackle peak concurrency challenges during major tournaments, making it a strong destination for backend and platform roles.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Dream11 fresher eligibility for campus drives
Dream11 does not publish one universal CGPA cutoff for every India SDE drive. Campus JDs and careers posts differ. Treat numbers below as candidate-reported (as of August 2026). Public interview archives are SDE-2 heavy - label that when you copy a HLD prompt into fresher prep.
Who this hub is for
- For: Students targeting SDE-1 / early-career backend or Android roles on contest, leaderboard, wallet, and client teams - mostly Mumbai, some Bengaluru.
- Not the same track: Assuming “I watch IPL, so I am ready.” Dream11 interviews care about concurrency and correctness, not cricket trivia.
- Experienced hires: SDE-2 loops add HackerRank coding, DB schema, onsite HLD (notifications / leaderboard / wallet), and a hiring-manager round. Use fresher sections as a base, then add design depth.
Degree, projects, and “is 7.0 enough?”
Yes - 7.0 / 70% meets the commonly reported floor. It is not a selection guarantee. A 7.1 with two fully passing OA solutions and a clear “what happens at match start” story beats an 8.9 who freezes on heaps.
Projects that help: any high-throughput API, a leaderboard demo, a wallet/ledger, a notification fan-out, Android/Kotlin client work, or a stream-processing toy. A ML certificate stack with zero systems talk rarely survives HLD.
On-campus vs off-campus vs lateral
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus (limited) | Batch OA, PPT, printed CGPA | Coding bar |
| Careers / referral | Resume volume; recruiter screen | Still expect coding OA |
| SDE-2 lateral | HLD + Mumbai onsite + HM | DSA still required |
Off-campus does not mean easier DSA. It often means more applicants on the same HackerRank filter. If your CGPA sits near 7.0, spend energy on mocks, not on hunting a mythical lower cutoff.
Documents and portal hygiene
- Keep marks consistent with the form - BV catches typos.
- Screenshot invite duration and language list. “My senior’s OA was two questions” is useless without your mailer.
- Ask the recruiter fresher vs SDE-2 before you over-prep Kafka internals. A campus OA will not look like a Mumbai onsite HLD; a lateral loop will. Mixing those calendars wastes weeks.
- For referrals, still treat OA as the exam.
- If you cannot relocate to Mumbai, say so early. Match-day on-call is not a rumour - IPL weekends are when the product actually earns. Ask HM what “on-call” meant on their last team before you sign.
Detailed eligibility criteria breakdown
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 7.0+ CGPA / ~70% | Verify every drive |
| Degree | B.Tech / B.E. / M.Tech / MCA | Maths/Stats sometimes listed |
| Branch | CS, IT, ECE (and related) | Strong DSA can help adjacent branches |
| Year | Final year + recent grads | Limited campus seats |
| Backlogs | No active backlogs | Clear before offer |
| Coding languages | Java, Kotlin, Python (C++ on HR) | Stick to one |
| On-call / peaks | Comfort with match-day load | Not a 9-to-5 product |
Skills & focus
Primary: Medium-hard DSA
Secondary: Scale design (leaderboard, notify, wallet)
First filter: HackerRank-style OA
Differentiator: Peak-concurrency vocabulary
Selection feel by CGPA band
| CGPA range | Rough chances | Reality check |
|---|---|---|
| Below 7.0 | Often filtered on-campus | Exceptional off-campus profile only |
| 7.0-7.4 | Meets many reported floors | Need strong OA + scale talk |
| 7.5-8.5 | Common in shortlisted chatter | Helps resume; OA still decides |
| 8.5+ | Strong for tiny campus pools | CGPA alone never clears HLD |
Dream11 placement papers - last few years
Download 2026 Dream11 placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What Dream11 previous year papers actually train
Dream11 does not publish one permanent official paper set. “Previous year papers” on this site are pattern trainers for OA and technical rounds - not leaked live tests.
| Round (typical) | What to practice |
|---|---|
| Online assessment | Timed accuracy on medium DSA (HackerRank-style) |
| Technical 1 | Live coding: heaps, graphs, streams, intervals |
| HLD / design (esp. SDE-2) | Notifications, leaderboard, wallet, contest join |
| HR / HM | Why Dream11, Mumbai, match-day ownership |
Themes that keep repeating (2024-2026)
- 2024 cycles: Public GFG SDE-2 loops: HackerRank coding → DB/projects → onsite Mumbai HLD (lineup notifications 30 minutes before a match; others got leaderboard or wallet) → hiring manager. Redis + Spark showed up in one design discussion. Campus fresher OA detail stayed sparse - do not pretend every college got the same paper.
- 2025 loops: Engineering blogs and talks emphasise IPL-scale Kafka consumers, 10M+ concurrent users, and hockey-stick traffic before match start. Interviewers still want DSA correctness first. Students who only memorised “we will use Kafka” without a bottleneck story failed HM.
- 2026 prep expectation: Keep medium DSA warm. Add one fresher-depth design: what happens when contest join + lineup push collide. Treat PDF packs as pattern catalogs. Own the stack template, not the exact “next smaller element” story.
How to use one paper set in a single sitting
- Timed: 60-90 minutes, 2 coding prompts in your OA language.
- Untimed review: rewrite the cleaner solution; list three match-day edge cases (empty contest, last-second join, duplicate notification).
- Map each miss to a theme (heap / graph / interval / stream) and pull two cousins from coding questions.
- Spend 15 minutes explaining a leaderboard happy path + one failure out loud.
- Log one STAR story (on-call style: you owned a broken demo at a deadline).
Related problems to practice
| Theme you saw in a set | What to drill next | Why Dream11 asks it |
|---|---|---|
| Top-K / frequent | Heap + bucket | Leaderboard ranks |
| Merge intervals | Sort + merge | Contest/match windows |
| Next smaller / stack | Monotonic stack | Stream updates |
| Grid unique paths | DP / BFS | Path counting under constraints |
| LRU cache | Hash + DLL | Hot contest state |
| Running median | Two heaps | Stream statistics |
2025 PDFs often drill “top K scores in a window.” Own the heap template, then drill a related problem for a live leaderboard. That transfers; memorising the cricket story does not.
Dream11 placement process, round by round
Dream11 hires through limited campus drives, careers.dream11.com, referrals, and experienced SDE-2 pipelines. After resume screen, the shape is product-company: timed coding, DSA, sometimes HLD, then HR/HM.
Application methods
Campus recruitment
Selected colleges - PPT, then OA and interviews. Confirm whether your batch is actually on the list this year.
Online applications
Apply on Dream11 careers. Follow the invite for HackerRank duration and languages.
Referrals / Linkedin
Many SDE-2 stories start with a recruiter ping. You still need passing tests and a design round.
1. Resume / eligibility screen
Degree, 7.0+ / 70% when printed, backlogs, year of passing. Projects that mention scale, Android, or backend ownership help. This is a gate - coding is the filter.
2. Online Assessment - Dream11 Online Assessment
Candidate reports (especially laterals) describe HackerRank coding. Fresher campus sectional dumps are thinner - treat the table as a working map.
| Section (typical) | Questions (reported) | Time feel | Focus |
|---|---|---|---|
| Coding | 2-3 mediums (varies) | 60-90 min common | Arrays, graphs, heaps, DP |
| Aptitude / MCQ | Sometimes absent | - | Confirm invite |
Languages: Java, Kotlin, Python; C++ often allowed. Platform: HackerRank appears in write-ups.
Pass bar: Fully passing tests beat a clever incomplete hard. Do not spend 50 minutes on problem 3 while problem 1 is red.
Student tip: Skim all prompts in 4 minutes. Bank the solvable medium. Write two edge cases (empty contest list, single player) before submit.
Example timing for a 90-minute OA
| Minute | Move |
|---|---|
| 0-5 | Read all problems; pick order |
| 5-40 | Problem 1 to full AC |
| 40-75 | Problem 2; brute + note if needed |
| 75-90 | Edge cases; do not start a new hard from scratch |
Deeper OA notes: Dream11 Online Assessment.
Public HackerRank themes from older SDE-II notes (use as cousins, not as tomorrow’s paper): unique paths in a grid with obstacles, next smaller element, running median of a stream, tree top-view, search in a rotated sorted array, LRU cache. If you can narrate those six templates, you are in better shape than a student who only grinded random Easy tags.
3. Technical - DSA + projects / db (~45-60 min)
Shared editor. Expect 1-2 DSA problems plus project or schema talk. Patterns from public loops: unique paths with obstacles, next smaller element, running median, top view of tree, search in rotated array, LRU cache, ACID and isolation levels.
You should:
- Clarify constraints (n, duplicates, live updates)
- Narrate brute → target complexity
- Code and dry-run
- Connect one resume project to a scale constraint if asked
Example narration (running median): “I’ll keep a max-heap for the lower half and a min-heap for the upper half so insert is log n and median is O(1).” Empty stream - I’ll define the return.”
4. HLD / System Design
Fresher depth if you are campus; deeper if you are SDE-2. Typical prompts from GFG 2024:
- Lineup notifications 30 minutes before match start - elastic from 1,000 to millions of users; two Kafka streams (joins + lineup)
- Real-time leaderboard during a live match
- Digital wallet / contest entry money
Start with users → data → APIs → what breaks at 7:30 pm IST on an IPL Sunday. Plain language beats “Aerospike + Spark” with no requirements. Dream11 has publicly talked about Aerospike + Kafka for peak load - name-dropping without a failure mode still fails.
Worked mini-outline - lineup notify:
- Actors: user, contest service, lineup service, notification service, device push.
- Happy path: user joins → stored in contest set → 30 min before start, lineup event → fan-out to joined users.
- Burst: millions of joins in a short window - queue the work, do not do sync HTTP fan-out.
- Failure: push provider down → retry with idempotency so users do not get 12 copies.
- Scale later: cache hot contest IDs; only after the above is clear.
5. HR / hiring manager (~20-40 min)
Why Dream11 (peak scale, not “I love cricket”), Mumbai relocation, on-call during matches, conflict, a time you were wrong. SDE-2 HM rounds have rejected people who cleared HLD but lacked depth or self-awareness. Know the ₹15-30 LPA fresher band.
| # | Round | Duration | What they check |
|---|---|---|---|
| 1 | OA (coding) | ~60-90 min | Timed correctness |
| 2 | Technical (DSA / DB) | 45-60 min | Code + narration |
| 3 | HLD (track-dependent) | 45-60 min | Scale reasoning |
| 4 | HR / HM | 20-40 min | Fit, Mumbai, ownership |
Timeline from application to offer
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | Limited campus windows |
| OA → shortlist | Days to a week | HackerRank often first |
| Interview loop | ~1-3 weeks | SDE-2 can span a month |
| Offer / paperwork | Days after final round | Written offer wins |
| End to end | ~2-4 weeks common | Laterals sometimes longer |
OA pattern cheat-sheet
| Component | Focus | Prep move this week |
|---|---|---|
| Coding Q1-Q2 | Heaps, graphs, streams | Two timed mediums back-to-back |
| Design follow-ups | Leaderboard, notify, wallet | 3-minute aloud sketch |
| DB | Indexes, ACID, isolation | One schema for contests/users |
| HR/HM | Why Dream11, Mumbai | Two STAR stories |
Practice map for Dream11 placements
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
How to train for Dream11 this season
If a Dream11 invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Dream11 sits around ₹15-30 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Dream11 eligibility for freshers 2026 is candidate-reported: often 7.0+ CGPA / 70% across academics; B.Tech/B.E./M.Tech/MCA in CS, IT, ECE, Maths or related fields; final-year students and recent graduates; no active backlogs. Strong DSA and scale thinking matter more than a marginal CGPA difference once you clear screening. Always verify the campus JD or Dream11 careers post.
What you are training for: Fresher SDE loops commonly run: Application → Online Assessment (HackerRank-style coding) → Technical (DSA + projects/DB) → system design / HLD on some drives → HR or hiring manager. Experienced SDE-2 loops are longer (coding → DB/projects → onsite HLD in Mumbai → HM). Confirm your invite; public write-ups skew experienced-hire.
Short version of the prep split: Split time roughly: 50% DSA (heaps, graphs, streams, intervals), 20% timed OA mocks, 20% scale design (leaderboard, notifications, wallet, contest join), 10% behavioral. Languages: Java, Kotlin, Python. Public detailed loops are SDE-2 heavy - ask the recruiter if your drive is fresher campus.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Timed aptitude + one easy coding problem a day, plus a one-page cs fundamentals sheet. Open the Dream11 previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Dream11 drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Dream11 usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Dream11?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Two full mocks, then only error-log topics - no new patterns. If you still have energy, redo only the questions you failed in week 2.
Where the hours should go
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Dream11-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Practice pages to open this week
- OA / assessment notes
- aptitude mock quiz
- coding question bank
- interview experiences
- HR question bank
- week-by-week guide
- previous year papers
- 2026 paper page
Use this hub for the Dream11 story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 Dream11 PDFs and never sitting one under a timer.
- Switching languages every weekend because a senior used a different one.
- Memorising HR answers before they can finish the OA.
- Ignoring the company-specific quirk on this page (unique round, exam name, or role band) and preparing like a generic service-company drive.
If you do one thing after reading this: schedule three timed Dream11 papers on three different days, then interview prep on the leftovers.
If you are starting from a service-company prep base
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Dream11 papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Dream11-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
10-day crash version
Days 1-3: one timed Dream11 paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why Dream11. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
What to carry into the interview room
Know your project at the level of what broke and what you changed, not only the tech list on the resume. For Dream11, interviewers often poke the same hole the OA already tested - be ready to re-solve a warm question on a shared editor or whiteboard. If you used AI to draft code while practising, you still need to type it yourself on the day.
Tracking that does not become a second job
A single note with date, paper name, score/time, and three misses is enough. If you cannot name your last three Dream11 mistakes, you are collecting content, not preparing.
Dream11 compensation & benefits
Figures are candidate-reported India bands (as of August 2026). Actual offers depend on level, Mumbai vs Bengaluru, and written base / bonus / ESOP split.
| Band | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| SDE-1 / fresher SWE | ₹15-30 LPA | Primary band for this hub |
| AmbitionBox fresher chatter | Often ~₹20-32 LPA by role | Aggregator, not an offer letter |
| Some SDE-1 write-ups | Toward ₹28-38 LPA cited in places | Year and college dependent |
| SDE-2 | Higher (₹40 LPA+ chatter common) | Not the campus default |
Confirm joining bonus and equity on the written offer. Do not treat blog midpoints as guarantees.
Benefits students actually care about
- Health insurance
- ESOPs / bonus split - ask HR to explain vesting
- Hybrid vs office for Mumbai teams
- Relocation support - ask, do not assume
- Match-day on-call expectations
How to talk CTC in HR
Know the ₹15-30 LPA fresher context, ask fixed vs variable vs stock, and clarify joining vs exams. One calm question beats aggressive negotiation with no anchor.
Recent Dream11 placement trends
- Campus hiring stays limited; laterals and referrals remain a large share of public stories.
- HackerRank-style coding is still the first technical filter.
- Peak-scale vocabulary (IPL concurrency, notify fan-out, leaderboards) shows up more in interviews than 2018-style pure DSA.
- SDE-2 onsite HLD in Mumbai is a real pattern in 2024 GFG notes - do not confuse it with every fresher drive.
- Treat ₹15-30 LPA as a reported fresher band, not a promise.
- Engineering talks about Kafka consumers at 300M+ RPM are useful background - they are not your OA syllabus.
FAQs students ask about Dream11 placements
Process & papers
What is the Dream11 placement process for freshers?
Typical product path: coding OA → technical DSA (sometimes DB/projects) → HR. Some tracks add HLD. SDE-2 laterals often run HackerRank → DSA/DB → Mumbai HLD → HM. Confirm your invite. Campus batches may compress; laterals can take weeks.
How many interview rounds does Dream11 usually have?
Freshers often see 3-4 stages. SDE-2 write-ups commonly list 4. Count the mailer.
Can I download Dream11 placement papers PDF for free?
Yes. Free 2024-2026 style practice is on this site - pattern trainers, not leaked live papers. Start with the 2026 PDF or the archive.
What does the Dream11 OA look like?
Candidate reports point to HackerRank-style coding (often 2-3 mediums). Exact duration varies. Languages: Java, Kotlin, Python, often C++. Verify yours.
Eligibility & offer
What eligibility / CGPA do fresher SDE drives usually expect?
Commonly reported: 7.0+ CGPA / 70%, CS/IT/ECE-related degrees, no active backlogs. Dream11 does not publish one universal cutoff.
What is Dream11 fresher salary in India?
Candidate-reported SDE-1 CTC often lands around ₹15-30 LPA (as of August 2026), mainly Mumbai. Some aggregators cite higher. The written offer is the only number that matters.
Do I have to relocate to Mumbai?
Mumbai is HQ. Bengaluru also appears. HR/HM will ask. Be honest about constraints and match-day on-call.
Prep & Dream11-specific
How should I prepare?
Split roughly 50% DSA, 20% OA mocks, 20% scale design, 10% behavioral. Confirm fresher vs SDE-2. Details: preparation guide.
Which programming languages are allowed?
Java, Kotlin, and Python are the usual set; C++ often works on HackerRank. Do not switch the week of the drive.
Is campus hiring the same as SDE-2 HLD loops?
No. Many GFG posts are experienced SDE-2 with onsite Mumbai design. Freshers should still know leaderboard/notify vocabulary but must not skip timed coding.
What design topics should I revise?
Lineup notifications, real-time leaderboards, wallets, contest join, burst traffic. Fresher depth: actors, APIs, bottlenecks, retries. Practice sketches beat memorised Kafka diagrams.
Dream11 vs Swiggy vs CRED?
All three pay product-company bands and care about DSA. Dream11 is peak sports concurrency. Swiggy is logistics. CRED is fintech. Compare written offers and the domain you can talk about for 45 minutes.
Any pro tip that actually changes outcomes?
Fully passing OA tests first. Then one IPL-scale story: what breaks 30 minutes before a match. Keep an error log. Do not use cricket fandom as your only Why Dream11.
Where can I read real interview experiences?
Dream11 interview experience plus GFG SDE-2 notes (label them as laterals). Patterns shift - maps, not scripts.
What recent candidates reported
Fresher / early-career colour
Campus volume is smaller than TCS-style drives. Students who cleared product OAs elsewhere still needed medium DSA under a clock. Project stories that mentioned throughput, mobile clients, or money movement landed better than generic CRUD.
SDE-2 loop (gfg, 2024) - use as a map, not a fresher script
A Bengaluru-based engineer with ~3 years was contacted on LinkedIn. Round 1: HackerRank coding. Round 2: DB schema and projects. Round 3 (27 April 2024, onsite Mumbai): HLD - design lineup notifications 30 minutes before match start, elastic from thousands to millions of users, two Kafka input streams. The candidate proposed Redis + Spark and cleared the round. Other candidates that day got leaderboard or wallet. Hiring manager round: philosophy, failures, conflicts - rejected after clearing HLD. Takeaway: design is not the last filter; HM still decides.
An older GFG SDE-II note listed HackerRank unique-paths-with-obstacles and next-smaller-element, then onsite DSA (running median, tree top view, rotated search), DBMS (ACID, indexing, isolation), LRU, and a system-design round on caching, load balancers, CAP, sharding.
What hurt people: coding before constraints; Kafka name-drops without idempotent notify; “I love cricket” with zero scale talk; treating HM as HR small talk.
More notes: Dream11 interview experience.
Sample technical follow-ups you should rehearse
- How would you store a live leaderboard for 10 million users updating every ball?
- What happens if a user taps “join contest” twice in 200 ms?
- Kafka vs a simple DB poll for lineup notifications - when is each wrong?
- LRU vs write-through cache for hot contest metadata.
- Isolation level if two users grab the last contest seat.
- Your OA is O(n log n) - is that enough at match start?
Answer out loud. Staff-level diagrams without a bottleneck sentence still fail.
Offer-stage discipline
If you clear HM/HR:
- Read ESOP vesting, joining bonus clawback, and Mumbai posting
- Ask about on-call during IPL weekends before you sign
- Do not resign until the written letter lands
- Background verification expects consistent employment dates
Peak-scale companies still run boring HR process. Keep the email thread.
One more mock template (90 minutes)
| Minute | Action |
|---|---|
| 0-5 | Skim all problems; pick order |
| 5-40 | Problem 1 to full AC with edges |
| 40-75 | Problem 2; brute force + note if needed |
| 75-90 | Re-read submissions; fix silly bugs |
Then spend 15 minutes on a leaderboard sketch. That combo matches how Dream11 actually filters.
Why “i like cricket” fails
Interviewers have heard it all week. A better 40-second Why Dream11: you want to work on burst traffic - a system that is quiet on Tuesday and violent on an IPL Sunday - and you have practised leaderboard/notify failure modes, not just watched matches. If you cannot say that without jargon, you are not ready for HM.