Skip to content
Placement Papers - Free Placement Papers for Top CompaniesPlacement Papers - Free Placement Papers for Top CompaniesPlacement Papers

How to Prepare for Dunzo

Treat Dunzo prep like a startup product loop: coding + ownership. Domain is hyperlocal logistics - use it only with real reasoning.

What Dunzo actually tests

First round: Dunzo-style coding + culture interviews

Time split that matches how candidates report outcomes (not a marketing pie chart):

  • DSA 45%
  • Projects 25%
  • Culture 20%
  • Mocks 10%

Patterns are from student reports and vary by role and drive. Trust your college placement email over blog folklore.

Hiring flow you should prep for

Stage Time What they check
Coding screen timed DSA
Interviews multiple Tech + culture

Time allocation

  • Data Structures & Algorithms (40% time) - Focus on arrays, hash maps, trees, graphs, dynamic programming
  • Coding Practice (30%) - Solve medium to hard problems on LeetCode, HackerRank
  • System Design (20%) - Logistics systems, route optimization, delivery systems
  • Technical Interview Prep (7%) - Core CS subjects, projects discussion
  • Behavioral Prep (3%) - Problem-solving approach, impact, teamwork

Daily loop (75-120 minutes)

  1. One timed block that matches Dunzo’s first round (coding + culture)
  2. Log misses: topic + why you failed (speed, concept, carelessness)
  3. Re-solve yesterday’s misses cold
  4. Twice a week: 10 minutes of resume/project narration out loud

6-8 week startup plan

Week Focus Exit criteria
1-2 DSA fundamentals Clean easy/medium solves
3-4 Projects + ownership stories Resume bullets measurable
5-6 Mocks + culture Explain trade-offs under pressure
7-8 Weak topics + HR No unfinished ‘hero’ projects on resume

Round-by-round strategy

Online Assessment

  • Order problems by confidence after a 3-4 minute skim
  • Passing test cases beats a brilliant half-solution
  • Invent edge cases before submit; watch timeboxes

Technical interviews

  • Restate → brute force → optimize → code → test
  • Show ownership; unfinished resume projects get punished.
  • Tie CS answers to a project when it strengthens the point

HR / managerial

  • Why Dunzo, why this team/role, location flexibility
  • STAR with a metric; pick 2-3 real company values and prepare proof

Dunzo-specific drills

  • Medium DSA
  • Routing/assignment style thinking

Topic checklist

  • Working code in one language
  • Projects you actually shipped
  • Ownership stories

Final stretch

30 days out: weekly full OA-style mocks; close weak DSA patterns; draft STAR stories.

7 days out: alternate mock / review days; re-solve misses cold; no new patterns.

Day before: skim notes, check machine/network/ID logistics, sleep.

Common mistakes for Dunzo aspirants

  1. Assuming hyperlocal domain talk replaces DSA - fix this first
  2. Preparing only interviews while failing Dunzo’s first round
  3. Collecting notes without timed mocks
  4. Listing five frameworks on the resume and defending none
  5. Changing language/stack one week before the drive
  6. Listing half-built side projects as production

Practice on this site

Comments & Suggestions

Coding questions

Interview experience

2026 papers

Dunzo hub

Similar companies

Swiggy · Zomato · Ola · Google · Amazon · Microsoft