Software Development Engineer at Dunzo

How it went

What they would tell you

How to prepare

Round by round

1. 1

   Phone Screening45 min

   This initial conversation felt like a deep dive into my motivation and technical understanding. The recruiter wanted to know why I chose Dunzo and probed my knowledge of designing large-scale systems, especially in hyperlocal delivery tech. It was more about mindset and approach than coding. Questions & Approach:

   • “Tell me about a large system you designed, what trade-offs did you make?”
   • “How do you debug performance issues in distributed environments?”
   • “What attracts you to hyperlocal delivery technology?"
2. 2

   DSA and Problem Solving90 min

   This round was tougher than I anticipated, the problems were rooted in real-world delivery platform scenarios. It tested my ability to model graph problems and use data structures efficiently. Questions & Approach: 1.Design a Routing Algorithm for Multiple Delivery Partners and Orders

   • Approach: Modeled the problem as a graph traversal with heuristics for optimizing routes. I discussed trade-offs in complexity and practical heuristics to handle NP-hardness. 2.Implement a Weighted Priority Queue for Delivery Sequencing

   • Approach: Built a heap-based priority queue that prioritized deliveries based on distance and urgency, ensuring efficient enqueue and dequeue operations. 3.Minimum Number of Trips to Deliver Orders with Capacity Constraints

   • Approach: Combined graph traversal with a greedy approach to minimize trips, carefully balancing capacity and route optimization. Throughout, I explained my thinking aloud and discussed time and space complexity at each step, keeping the code clean and modular.

3. 3

   System Design Interview75 min

   I was tasked with designing a real-time tracking system for delivery partners and customers. This involved streaming location data efficiently and handling unreliable networks gracefully. Focus Areas & Approach:

   • Used Kafka and WebSockets to stream high-frequency location updates with low latency.
   • Designed fallback mechanisms to handle poor network conditions without losing data integrity.
   • Proposed geospatial indexing for storing historical location data efficiently. Bonus discussion included designing a surge pricing system based on supply and demand, where I explained dynamic pricing models and data feedback loops
4. 4

   Behavioral + Cultural Fit60 min

   This round focused on my work style, attitude, and fit with Dunzo’s culture. Questions revolved around teamwork, handling pressure, and balancing technical debt. Questions & Approach:

   • “Tell me about delivering a project under tight deadlines.”
   • “How do you handle disagreements in team decisions?”
   • “How do you balance technical debt with faster delivery?”
5. 5

   Technical Manager Round60 min

   This round was a deep dive into my previous backend projects and leadership skills. The manager probed my experience with scalability issues and how I mentor junior team members. Discussion & Approach:

   • Described handling bottlenecks and improving system throughput.
   • Shared mentoring experiences and approaches to team growth.
   • Discussed ideas on reducing Dunzo’s delivery time through tech innovations.
6. 6

   HR and Offer Discussion30 min

   A smooth and friendly round covering motivation for choosing Dunzo, compensation details including ESOPs, career growth, and location flexibility.

What came up