Historical academic snapshot
Marks: 70% or 7.0+ CGPA throughout (candidate-reported, when hiring)
Degree: B.Tech / B.E. / M.Tech in CS, IT, related
Backlogs: None active
Year: Final-year and recent grads
Dunzo Placement Papers 2026
Dunzo was a Bengaluru-based hyperlocal delivery startup, founded in 2014, that offered quick commerce and courier services across Indian cities. Backed at various points by Google and Reliance, its hiring activity has been uncertain following restructuring, so candidates should verify current openings.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Who can apply to Dunzo in 2026?
Nobody should plan a Dunzo offer in 2026. There is no campus season to clear. Eligibility below is what students reported when Dunzo still hired, so old PDFs and GFG posts make sense.
Who this hub is for
- For: Students using historical Dunzo papers to train logistics-flavoured DSA and fresher system design, then applying to active quick-commerce / delivery product companies.
- Not for: Waiting on a Dunzo careers portal refresh, or treating 2024 salary blogs as a 2026 letter.
- Intern write-ups: 2023 GFG intern loops are still useful timed drills. They are not a conversion path now.
On-campus vs off-campus (historical)
| Route (when active) | What usually changed | What stayed the same |
|---|---|---|
| Campus | Batch OA window, PPT | 90-minute coding bar |
| Careers / referral | Resume volume | Same DSA + design depth |
| Intern → FTE | Sometimes fewer stages | You still defended projects |
Off-campus never meant easier graphs. It meant more applicants fighting the same ~90-minute filter.
Degree, 7.0, and “was 7.0 enough?”
Was 7.0 CGPA enough? It matched the commonly reported floor across 10th, 12th, and graduation. Selection still hinged on OA correctness and a coherent route/tracking story. A 7.2 with clean timed coding beat an 8.8 that froze on edge cases.
Branches: CS/IT dominated. Related streams showed up with solid DSA.
Gaps and backlogs: Active backlogs were a usual blocker. Short gaps needed a skills story.
What used to help the resume screen: One project with ownership, any logistics/e-commerce internship, contest signal when real. Certificates were optional. See certifications only as career context, not as a Dunzo application checklist.
Skills the old filter used
OA: 2-3 medium-hard coding problems
Languages: Python, Java, JavaScript
Design: Routes, time windows, live tracking
Focus: Correctness under 90 minutes
Historical academic floor
| Item | Typical expectation (when hiring) | Reality check now |
|---|---|---|
| Graduation | 70% or 7.0+ | Archival only |
| 10th & 12th | Often same throughout rule | Ignore for Dunzo 2026 |
| Branches | CS/IT and related | Reuse for other product drives |
| Backlogs | None active | Same advice elsewhere |
| Coding languages | Python, Java, JavaScript | Keep one for live companies |
Who this practice still fits
Good fit for the papers: You like medium DSA, you can talk about graphs and time windows without a buzzword salad, and you will retarget Swiggy/Blinkit/Zepto this month.
Bad fit: You want a 2026 Dunzo joining date. That date does not exist. Close the tab if that was the only goal. Keep the tab if you need logistics DSA reps.
Intern vs FTE write-ups: The 2023 GFG intern loop is still the best public problem list. FTE notes were thinner and more design-heavy. Use intern DSA for OA stamina and FTE-style sketches for Tech 2 at live companies. Do not mix them into a fake “Dunzo 2026 FTE pattern” blog in your head.
Referral nostalgia: A friend who “used to work at Dunzo” cannot refer you into a shutdown. They can refer you into their current company. Ask for that instead.
Dunzo placement papers - last few years
Download 2026 Dunzo placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What Dunzo previous year papers actually train
Dunzo never published one permanent official paper set. Packs on this site are pattern trainers for historical OAs and early technicals. In 2026 they are also transfer trainers for other logistics product loops.
| Round (historical) | What to practice |
|---|---|
| Online assessment | Timed 90 min, 2-3 coding problems |
| Technical 1 | Live DSA narration |
| Technical 2 | Logistics design: routes, tracking, scale |
| Managerial / HR | Impact, ambiguity, why delivery tech |
Themes that keep repeating (2023-2025 write-ups)
- 2023 intern (GFG, on-campus): 90-minute OA (13 advanced). Google Meet DSA on Stone Game V, LIS variants, Longest Valid Parentheses, first missing positive. Round 3 interviewer said if you explain the approach they would still be happy. Two students reached cultural fitment. Same-day select mail after a senior-manager resume walk.
- 2024-2025 style practice sets: Route optimisation with time constraints, maximum deliveries in a window, graph shortest paths, DP on sequences. Design prompts around multi-partner routing and live location.
- 2026 use: Keep the same templates. Sit a company that still exists.
How to use one paper set in a single sitting
- Timed: 90 minutes, 2-3 problems, one language.
- Untimed: rewrite the cleaner solution; list three edge cases (empty, one node, two partners at the same lat-long).
- Map misses to themes (graph / DP / window / heap) and pull cousins from coding questions.
- Spend 15 minutes on a route optimiser or live tracking sketch out loud.
- Log one STAR story about messy real-world constraints (late partner, bad GPS, peak dinner).
Related problems to practice
| Theme you saw | Drill next | Why it showed up |
|---|---|---|
| Time-window deliveries | Interval scheduling, greedy + sort | Partner capacity |
| Route / graph | Dijkstra, BFS layers | City graph intuition |
| DP on sequences | LIS, stone-game family | OA favourites in 2023 notes |
| Parentheses / stack | Valid strings, histogram | Classic OA companions |
| Live tracking | WebSocket vs poll, geo index lite | Tech 2 design |
Using Dunzo papers to train logistics loops
Week calendars live on the preparation guide. This H2 is the transfer plan: Dunzo papers in, live applications out.
Time split
| Bucket | Share | What “done” looks like |
|---|---|---|
| Medium-hard DSA | ~50% | 90-minute 2-3 problem mocks |
| Logistics design lite | ~25% | One route + one tracking sketch you can say in 90 seconds |
| Project + behavioral | ~15% | Metrics, messy constraints, learning a stack |
| Live-company applications | ~10% | Swiggy / Blinkit / Zepto / Flipkart Minutes this month |
If you only solve Dunzo PDFs and never open another careers page, you are collecting nostalgia.
This week
- One 90-minute mock from coding questions or the 2026 pack.
- Re-solve one 2023 GFG-style problem (parentheses or first missing positive) cold.
- Draw the dinner-peak assignment sketch on paper.
- Apply to two active companies with similar DSA bars.
- Error log: graph miss vs DP miss vs “I never read constraints.”
What not to waste time on
- Refreshing dunzo.com for openings
- Quoting ₹12-18 LPA as if it were a 2026 letter
- Staff-level distributed-systems courses for a fresher logistics chat
- A second coding language “because Dunzo liked Python”
- Building a week plan that assumes a Dunzo PPT
A 10-day transfer sprint (not a Dunzo campus calendar)
Days 1-2: two 90-minute mocks; error log only.
Days 3-4: graphs + time windows; one interval problem daily.
Days 5-6: the two design sketches until you can say them without notes.
Days 7-8: apply to three live companies; tailor one project bullet to delivery/scale.
Days 9-10: one more mock + behavioral stories; stop reading Dunzo news.
If you need a longer calendar, use the preparation guide and still put live applications on the same weeks. Papers without applications are a hobby.
OA clock that still works
Minute 0-3: read all prompts; pick the one you can finish.
Minute 3-35: full passing solution + 3 tests.
Minute 35-80: second problem; leave a brute if the optimal is not landing.
Minute 80-90: third problem only if two are already submitted. Partial credit is a rumour; a blank third is better than three halves if the platform needs full tests.
What “logistics flavour” actually means on a coding prompt
A Dunzo-style wrapper is usually a normal DSA problem with delivery nouns:
- “Partners” = nodes or agents
- “Orders” = tasks with timestamps
- “ETA” = weights on edges
- “Time window” = intervals
- “Capacity” = knapsack / greedy bound
If you panic at the story and never name the pattern, you lose 10 minutes. Read the constraints. If n is 1e5, it is not DFS on every pair. If n is 20, DP or backtracking is legal. Say the pattern out loud in a mock so you still can in a live Swiggy OA.
Behavioral stories that transfer
Keep three STAR stories with numbers:
- A late constraint (exam, fest, internship) and what you cut
- A teammate conflict on a project and the outcome
- A time you learned a stack in days because production (or a deadline) required it
The 2023 manager round asked how you learn new stacks. That question still appears at other startups. “I watched a 12-hour course” is weak. “I shipped X in Y days and the metric was Z” is the answer.
Honest shutdown FAQ you should not argue with
Dunzo lost to unit economics and quick-commerce capital. That is not a puzzle for your resume. If an interviewer at another company asks “why did Dunzo fail,” one sentence is enough: cash burn and competition, then pivot to what you learned from the papers (routing, tracking). Do not perform a case on a dead company unless they ask you to.
Night-before checklist for a live company mock
Treat tomorrow’s Swiggy/Blinkit OA like the Dunzo paper you just timed:
- One language chosen; IDE login works
- Last two mocks reviewed, not a new topic
- Dinner-peak sketch on one page
- Resume PDF with one metric bullet
- Sleep. A 9 a.m. OA after a 3 a.m. “one more graph” is how easy array items fail
What not to tell HR at the next company
Do not say you “were about to join Dunzo.” You were not. Do not say you are only practising dead papers. Say you practised logistics DSA and design and you want to ship at a company that still has customers. That sentence is adult. The other one is a meme.
Dunzo hiring rounds in 2026
This is the historical loop. There is no 2026 application window to join.
When Dunzo hired, freshers came through campus cells, a careers portal, and referrals. After resume screen, the shape was product-startup style: timed coding OA, two technicals, managerial, HR.
Application methods (archived)
Campus recruitment
College placement cells, typically late summer / monsoon for final years when the company still ran drives.
Online applications
dunzo.com careers. The site is not a 2026 hiring channel.
Referrals
Helped visibility. The OA bar stayed the same. Referrals cannot create a shutdown company.
1. Resume screen (historical)
7.0 / 70% throughout when printed, CS/IT-heavy, projects with some systems flavour.
2. Online Assessment (~90 min)
Usually 2-3 coding problems, medium-hard, HackerRank or similar. Arrays, strings, DP, graphs, sometimes a delivery-flavoured wrapper. No negative marking in most notes. Partial solutions sometimes counted. Student rumours put OA pass around 30-40% of a batch. Ignore that number for 2026 planning.
Pass habit that still matters elsewhere: skim all prompts, bank a full passing solution, then chase the harder one. Optimisation talk without a working answer lost the room.
3. Technical 1 (~45 min)
Live DSA. Graph/DP/optimisation. Python, Java, or JavaScript. Interviewers wanted the approach spoken before code.
4. Technical 2 (~45 min)
System design for logistics: multi-partner routes, live tracking, geo, scale, failure when GPS drops. Fresher depth: actors, APIs, bottlenecks. Not staff-level Kafka sermons.
5. Managerial (~45 min)
Impact, conflict, how you handle messy constraints, project ownership.
6. HR (~30 min)
Why Dunzo, Bengaluru/Mumbai, joining date. Historical only.
Historical timeline
| Phase | Typical duration then | Notes now |
|---|---|---|
| Apply / screen | ~1 week | Do not apply |
| OA | 1 sitting | Reuse as a mock |
| Tech 1 + 2 | 1-2 weeks | Reuse as mock interviews |
| Managerial + HR | A few days | Transfer stories to live firms |
| Offer | 3-5 days after last round | None in 2026 |
| End to end | ~3-4 weeks then | Use the clock for Swiggy-like loops |
Mini design sketch students should still rehearse
Assign 50 partners to 400 orders in a 90-minute dinner peak:
- Actors: customer, partner app, assignment service, map/ETA.
- Constraint: time windows + capacity + distance, not “shortest path only.”
- Naive: greedy nearest partner. Say what breaks (starvation, stacking).
- Better: batch window (30-60s), score distance + SLA risk, cap per partner.
- Failure: GPS stale → widen radius or human dispatch. Do not lead with Kubernetes.
That 90-second sketch beats a memorised microservices diagram in any remaining quick-commerce loop.
Intern loop variant (GFG 2023)
OA → two DSA Meets → cultural fitment → senior manager (resume + why Dunzo + how you learn stacks). Same-day evening select mail. Two students in fitment. Steal the problem list. Do not wait for a 2026 intern poster.
Documents you still need for the next company
Dunzo will not verify your 12th marksheet. Swiggy might. Keep 10th, 12th, degree, ID, and a one-page resume in one folder while you use these papers. The throughout-70% habit from old Dunzo JDs is still the habit other product firms use. Do not wait until a live OA invite to hunt PDFs.
Community write-ups worth a skim
The 2023 GFG intern thread is the main public primary source on this hub. Cross-check dates. Anything promising a “Dunzo 2026 off-campus drive” after the insolvency news is noise. Skim, then return to timed mocks.
Dunzo aptitude, coding & interview practice
Online assessment
Historical 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 aimed at transferring this pattern to live companies.
A practical Dunzo prep plan
If a Dunzo 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 Dunzo sits around ₹12-18 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, Python, C, Go. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Historical candidate reports commonly cited 70% or 7.0+ CGPA across 10th, 12th, and graduation; B.Tech/B.E./M.Tech in CS, IT, or related fields; final-year or recent grads; no active backlogs; strong Python, Java, or JavaScript. Those bars are archival. Do not wait for a 2026 Dunzo mailer.
What you are training for: Historical fresher loops commonly ran: Online Assessment (~90 min, 2-3 medium coding problems) → Technical 1 (~45 min, DSA) → Technical 2 (~45 min, logistics system design) → Managerial (~45 min) → HR (~30 min). Campus-to-offer often took about 3-4 weeks when the company was active.
Short version of the prep split: Use Dunzo sets to train medium-hard DSA (arrays, graphs, DP, optimisation) and logistics system design (routes, time windows, live tracking). Then sit real drives at Swiggy, Blinkit, Zepto, or Flipkart Minutes. Languages: Python, Java, JavaScript. Full plan: /dunzo/preparation-guide/.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Oa pattern first: sit one untimed paper, then redo it under the real clock. Open the Dunzo 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 Dunzo 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 Dunzo 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 Dunzo?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Star stories + one project walkthrough recorded on your phone. 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 Dunzo-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 Dunzo story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 Dunzo 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 Dunzo 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 Dunzo papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Dunzo-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 Dunzo 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 Dunzo. 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.
Dunzo compensation & benefits
Figures below are historical, candidate-reported (pre-shutdown). They are not 2026 offers.
| Track (historical) | Typical CTC then | Notes |
|---|---|---|
| Software Engineer (fresher) | ₹12-18 LPA | Bengaluru/Mumbai context in blogs |
| Senior SWE (1-2 years) | ₹20-25 LPA | Not a campus default |
| Tech lead (indicative) | ₹28-35 LPA | Experience band |
ESOPs, hybrid, and meal vouchers appeared in old perk lists. None of that is joinable in 2026. Compare current letters from companies that still exist.
How to talk historical CTC without lying to yourself
Use the band only to sanity-check other product offers. If a live quick-commerce letter is ₹12-20 LPA, Dunzo blogs are in the same neighbourhood. If someone sells you a “Dunzo 2026 18 LPA drive,” they are selling a ghost.
Dunzo hiring updates for 2026
- 2025: App/site defunct around January; insolvency followed. Engineering hiring stopped.
- 2026: No campus season. This page stays up because students still search “Dunzo placement papers” and because the DSA + logistics design pattern is reusable.
- What replaced the dream: Quick-commerce and food-delivery product loops (Swiggy, Blinkit, Zepto, Flipkart Minutes) plus other Bengaluru product companies with 90-minute OAs.
- What did not change: Medium-hard DSA still filters those loops. Route and tracking sketches still impress more than empty “I love startups” lines.
Net: do not prepare for Dunzo. Prepare with Dunzo papers for someone who can still sign an offer.
If you find a 2024 resume that still says “incoming Dunzo SDE,” that person is not a 2026 data point. Quick-commerce teams that absorbed talent are the live network. Ask those people for referrals, not for a Dunzo comeback rumour. A dead brand is still useful as a pattern library. It is useless as a calendar. Close the rumour tabs.
Common questions about Dunzo hiring
Status & papers
Is Dunzo hiring freshers in 2026?
No. Shutdown / insolvency after early 2025. Do not wait for a campus mailer. Use papers as trainers and apply to live companies.
Can I download Dunzo placement papers PDF for free?
Yes. Free Dunzo-style PDFs and 2024-2026 practice sets are on this site. Start with the 2026 PDF or the archive. They are not live exam papers.
Are old Dunzo interview experiences still useful?
Yes, as DSA and logistics-design practice. See interview experience and the 2023 GFG intern notes. They do not predict a Dunzo offer.
Historical process
What was the Dunzo placement process?
Historical SWE: OA (~90 min, 2-3 coding) → Technical 1 → Technical 2 (design) → Managerial → HR. About 3-4 weeks when active.
How many rounds did Dunzo usually have?
Most full-time notes said five. Some intern loops used OA + two DSA + fitment + manager. Archival only.
What did the Dunzo OA look like?
Often ~90 minutes, 2-3 medium-hard coding problems on HackerRank-style platforms. Details: online assessment.
Eligibility & pay (historical)
What eligibility / CGPA did fresher drives usually expect?
Commonly reported floor when hiring: 7.0+ CGPA / 70% throughout; CS/IT-related degrees; no active backlogs. Irrelevant for a 2026 Dunzo application because there is none.
What was Dunzo fresher salary in India?
Candidate-reported SWE often ₹12-18 LPA pre-shutdown. Not a 2026 letter.
Prep & retarget
How should I use Dunzo papers in 2026?
50% timed DSA, 25% logistics design sketches, 15% stories, 10% live applications. Guide: preparation guide.
Which programming languages did Dunzo allow?
Python, Java, JavaScript in most notes. Keep one for Swiggy/Blinkit-style OAs.
Dunzo vs Swiggy vs Blinkit for freshers in 2026?
Dunzo is not hiring. Swiggy and Blinkit (plus Zepto / Flipkart Minutes) are the live comparisons. Reuse Dunzo DSA and route sketches there. Compare current CTC, not Dunzo blogs.
Any pro tip if I am using these papers anyway?
One time-window coding problem + one live-tracking sketch, then apply somewhere that still sends PDFs. Do not build a calendar around Dunzo season.
Should I still list Dunzo prep on my resume?
No. List skills (DSA, routing, tracking). Listing “preparing for Dunzo 2026” looks uninformed.
Where can I practise similar live loops?
Start with Swiggy, Zomato, and other product hubs on this site. Transfer the 90-minute mock habit.
Real Dunzo interview notes from candidates
These notes are historical. Nobody is repeating this loop for a 2026 Dunzo FTE.
SDE intern, on-campus 2023 (GFG)
Cleared a 90-minute OA (13 advanced). Two Google Meet DSA rounds: Stone Game V, LIS variants, Longest Valid Parentheses, first missing positive. Round 3: interviewer said explaining the approach would still make them happy. Two students reached cultural fitment. Round 4 with a senior manager (10+ years): resume walkthrough of project code, why Dunzo, how they learn new stacks. After ~30-35 minutes, same-day evening select mail. Source: GeeksforGeeks Dunzo intern 2023.
Steal: approach-first DSA; same-day energy after OA; project code you can open without searching.
Ignore: any implication that a 2026 intern poster is coming.
Composite SWE notes (pre-shutdown)
Students who got selected usually shipped fully passing OA code, could talk graphs and time windows, and had one project with a metric. Students who failed often coded before constraints, designed “Uber for everything” with six microservices, or treated managerial as HR small talk.
After you finish a Dunzo mock
- Re-solve every miss cold.
- Redraw the dinner-peak assignment sketch from memory.
- Open two live company portals the same day.
- Warm one medium graph and one DP.
- Stop refreshing Dunzo news for a “comeback drive.”
Steal the 2023 problem list without worshipping it
Stone Game V, LIS, Longest Valid Parentheses, and first missing positive are not “Dunzo secrets.” They are standard mediums. If you can narrate all four in 45 minutes, you are ready for a live product OA. If you can only recognise the names from a GFG title, you are not.
Stone Game / interval DP: say the recurrence in one sentence before code. LIS: n log n if you have it, n² if you do not; say which and why. Parentheses: stack or two-pass; mention the empty-string case. First missing positive: the in-place index trick or a set; mention the 1..n constraint.
Second design sketch: live tracking without a buzzword pile
- Actors: partner app, location ingest, map tile / ETA, customer ping.
- Write path: partner pings every 5-15s; drop obvious GPS jumps.
- Read path: customer poll every few seconds or a websocket if the invite used that word; either is fine if you name the trade-off.
- Failure: stale ping → show “last seen 2 min ago,” do not invent a location.
- Scale later: geo index and hot city partitions only after the above is clear.
Say that in 90 seconds at Swiggy or Blinkit and you will sound more prepared than a six-box microservices slide.
Transfer table (Dunzo paper → live company)
| Muscle from Dunzo papers | Where it still pays |
|---|---|
| 90-minute 2-3 problem OA | Swiggy, Blinkit, Zepto, Flipkart, Amazon |
| Time-window / graph | Any delivery or mobility loop |
| Live tracking sketch | Quick-commerce and food delivery |
| Ambiguity STAR stories | Any startup HR |
| ₹12-18 LPA blog memory | Only as a sanity check on current letters |
If a live letter is ₹8 LPA with a brutal bond, Dunzo nostalgia is not a reason to reject it or accept it. Compare the live PDF.
More narratives: Dunzo interview experience.