Dunzo's coding rounds are generally medium to hard difficulty, focusing heavily on clean, efficient code and optimal solutions. While similar to Amazon's focus on Data Structures & Algorithms (DSA), it often includes a stronger emphasis on real-world problem contexts relevant to logistics and quick commerce, so practice applying patterns to domain-specific scenarios.
A dedicated 2-3 month preparation period is ideal. Allocate 60% of your time to solving 150-200 LeetCode problems (prioritize medium/hard on arrays, trees, graphs, and DP), 30% to mastering Dunzo's specific Leadership Principles with STAR-formatted stories, and 10% to high-level system design fundamentals if interviewing for SDE-2+ roles.
For SDE-1, focus intensely on core DSA and writing production-quality code. For SDE-2 and above, expect a dedicated system design round covering scalability, microservices, and database design—study scalable architectures for on-demand delivery systems. All levels should be prepared to discuss past projects in depth, focusing on trade-offs and impact.
The top mistake is under-preparing for the behavioral/Bar Raiser round; Dunnzo values leadership principles highly. Another is not clarifying problem requirements or constraints before jumping into code. Also, candidates often fail to communicate their thought process verbally during coding, which is a key evaluation metric.
Excelling in the Bar Raiser round by providing specific, principle-aligned examples of ownership, customer obsession, and bias for action is critical. Standout candidates also discuss scalability implications of their code solutions and demonstrate genuine product intuition about Dunzo's business model during system design or project discussions.
The process usually takes 4-6 weeks: 1-2 weeks for initial screening, 1-2 weeks for technical rounds, and 1-2 weeks for the Bar Raiser and team match. If you haven't heard back within a week after your final round, a polite follow-up email to your recruiter is appropriate. Delays can occur due to hiring manager availability.
SDE-1 interviews test strong DSA fundamentals and coding hygiene. SDE-2 adds a significant system design round and expects you to demonstrate impact in past projects. SDE-3 emphasizes deep system design (often API design for large-scale systems), architectural thinking, and leadership influence, with a heavier weight on the Bar Raiser's evaluation of strategic impact.
Use LeetCode (tagged company questions) and Grokking the System Design Interview for core skills. Critically, review Dunzo's careers page and engineering blogs for their Leadership Principles and tech stack mentions. Practice explaining your projects using Dunzo's principles (e.g., 'How did you show customer obsession?'). Mock interviews with peers familiar with high-velocity problem-solving are highly recommended.
