What questions are asked in Dunzo interviews?

Dunzo interviews commonly cover DSA coding (Top-K frequent elements in order stream; Shortest path in a warehouse grid), core CS (OOPs, DBMS/SQL, OS basics where relevant), project discussion, and topics tied to the business such as hyperlocal logistics, routing, inventory. Behavioural questions check ownership, teamwork, and why Dunzo.

How many rounds are there in the Dunzo interview?

Dunzo typically has 4 stages: Online Assessment (90 min), Technical Round 1 (45–60 min), Technical Round 2 (45–60 min), HR (20–30 min). Some drives skip GD or merge HR with managerial. Always check the mailer for that cycle.

How should I prepare for Dunzo interviews?

For Dunzo, prioritise DSA practice with timed mocks, revise OOPs and SQL, prepare a crisp project narrative, and read up on hyperlocal logistics and routing. Use STAR for behavioural answers and ask one thoughtful question at the end.

Dunzo Interview Experience 2025–2026 — Real Candidate Stories

Dunzo interview experience

These write-ups reflect how Dunzo fresher interviews usually go — campus and off-campus. Patterns shift by year and role, so use this as a prep map, not a script.

Dunzo placement process typically includes online assessment, technical interview, and HR interview rounds. See the placement process section for complete details.

Most drives expect a clean academic record (often around 6.0–6.5+ CGPA with no active backlogs). Candidate-reported detail: Dunzo eligibility criteria for freshers include minimum percentage requirements, degree requirements, and other criteria. Check the eligibility section for detailed

Fresher offers (candidate-reported) often land around te-reported, 2026): Software Engineer: ₹12-18 LPA for new graduates, Senior Software Engineer: ₹20-25 LPA (1-. Treat numbers as directional — confirm on your offer letter.

Round-wise process

Round	Duration	What they test
Online Assessment	90 min	2–3 coding problems
Technical Round 1	45–60 min	DSA + project discussion
Technical Round 2	45–60 min	System design (orders / logistics)
HR	20–30 min	Behavioural + culture fit

Real interview experiences

Experience 1 — campus / off-campus drive

Profile: B.Tech CS/IT, mid-to-high CGPA, projects aligned to hyperlocal logistics.

Round 1 - Online Assessment (90 minutes)

Questions: 2 coding problems - Problem 1: Route optimization with time constraints (Medium-Hard) - Problem 2: Maximum deliveries in time window (Medium) - Approach: Solved both problems with optimal solutions - Result: Cleared OA - Tip: Practice logistics-related problems, focus on optimization

Round 2 - Technical Interview 1 (45 minutes)

Interviewer: Senior Software Engineer - Questions Asked: - “Design an algorithm to find optimal delivery routes” - “How would you handle real-time location updates?” - “Explain your approach to the OA problem” - My Approach: - Discussed graph algorithms and dynamic programming - Explained real-time system design considerations - Walked through OA solution with optimizations - Key Tips: - Think aloud, explain your thought process - Consider edge cases and scalability - Result: Advanced to next round

Round 3 - Technical Interview 2 (45 minutes)

Focus: System design for delivery optimization - Question: “Design a system to optimize delivery routes for multiple partners” - Discussion: Covered scalability, real-time updates, geospatial algorithms - Result: Advanced to managerial round

Round 4 - Managerial Round (45 minutes)

Questions: Behavioral questions about problem-solving, impact, teamwork - Technical Discussion: Deep dive into projects, challenges faced - Result: Advanced to HR round

Experience 2 — another candidate path

Round 5 - HR Interview (30 minutes)

Discussion: Career goals, why Dunzo, role expectations - Result: Received offer

Questions that come up often

Coding / technical

Top-K frequent elements in order stream — typically expects heap / bucket sort
Shortest path in a warehouse grid — typically expects BFS
Merge overlapping delivery slots — typically expects interval merge
Discussion on hyperlocal logistics and routing — capacity, failure modes, simple APIs
Project deep dive — architecture, hardest bug, what you would change

HR / behavioural

Why this product?
Example of working with ambiguous requirements
Weekend / on-call comfort
Relocation

Practical tips for Dunzo

Practise DSA under a timer. Clearing the OA matters more than polishing a perfect resume line.
For domain rounds, be ready to talk about hyperlocal logistics in plain language — inputs, outputs, bottlenecks.
Revise OOPs and SQL; many Dunzo panels still open with fundamentals.
Keep HR answers concrete. One story with a clear result beats five buzzwords.
If you do not know something, say so and outline how you would find out. Guesswork wastes the round.

Dunzo HR Interview Questions — common HR questions and how to answer them
Dunzo Preparation Guide — round-wise prep plan
Dunzo Coding Questions — practice problems with approaches
Dunzo Previous Year Papers — past papers and patterns
Dunzo Placement Papers — company overview, eligibility, and process

Last updated: August 2026