Dunzo Interview Experiences

Dunzo has shut down

Dunzo completely ceased operations in January 2025 and is not conducting interviews or accepting applications. The content below is a historical record of Dunzo’s interview process while it was operating, not live prep material. If you’re targeting quick-commerce roles today, see Blinkit or Swiggy instead.

How Dunzo’s fresher interviews used to run, campus and off-campus, while the company was operating. Kept as a historical reference only.

For fresher tech roles, Dunzo historically ran an Online Assessment (90 min), Technical Round 1 (45-60 min), Technical Round 2 (45-60 min), and HR (20-30 min).

How to use this page

Read the round table first, then the experiences. Practise the coding patterns with edge cases, and keep one clear story each for ownership, conflict, and a project failure.

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

From candidate reports on campus / off-campus drives

Learn from real Dunzo placement interview experiences shared by candidates who successfully cleared the placement process.

Technical interview experience 1

Candidate Profile: B.Tech CS from Tier-1 college, 8.5 CGPA, 1 internship in logistics tech

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: Detailed discussion into projects, challenges faced
• Result: Advanced to HR round

Round 5 - HR Interview (30 minutes)

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

Key Takeaways: Strong problem-solving skills, clear communication, and understanding of logistics systems helped. Practice system design for logistics domain.

Technical interview experience 2

Candidate Profile: M.Tech CS, 8.0 CGPA, 2 years experience in e-commerce

Technical Interview 2 - System Design (45 minutes)

• Question: “Design a real-time delivery tracking system”
• Approach:
• Discussed architecture: API gateway, microservices, message queue
• Real-time updates using WebSockets
• Database design for location tracking
• Caching strategy for performance
• Result: Strong performance, advanced to next round
• Tip: Focus on scalability, real-time requirements, and performance optimization

Key Takeaways: System design skills and understanding of real-time systems are crucial. Practice designing logistics and delivery systems.

Questions that come up often

Coding / technical

1. Top-K frequent elements. Usually expects heap / bucket sort
2. Shortest path in a grid. Usually expects BFS
3. Merge overlapping delivery slots. Usually expects interval merge
4. Discussion on hyperlocal logistics and routing, bottlenecks, failure modes, simple APIs
5. Detailed project discussion, architecture, hardest bug, what you would change

HR / behavioural

1. Why this product?
2. Working with unclear requirements
3. On-call or weekend comfort
4. Relocation

Practical tips for Dunzo

• Clear the screening round first. Timed practice beats last-minute topic hopping.
• For domain questions, explain hyperlocal logistics in plain language, inputs, outputs, what breaks at scale.
• OOPs and SQL still open a lot of Dunzo panels. Do not skip fundamentals.
• HR answers should be concrete. One story with a result beats five slogans.
• If you do not know something, say so and outline how you would find out.

HR interview

After technical rounds, Dunzo usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.

HR interview questions→

Common Dunzo HR questions, sample answer frames, and STAR tips.

Similar companies

Swiggy · Zomato · Ola · Google · Amazon · Microsoft