Dunzo

Software Engineer 2

Software EngineerL2Medium

This interview process is designed to assess candidates for the Software Engineer L2 role at Dunzo. It evaluates technical proficiency, problem-solving skills, system design capabilities, and cultural fit.

Rounds

3

Timeline

~7 days

Experience

2 - 5 yrs

Salary Range

US$180000 - US$250000

Total Duration

135 min

Overall Evaluation Criteria

Technical Skills

Problem-solving approach
Algorithmic thinking
Data structure knowledge
Code quality and efficiency

System Design

System design principles
Scalability considerations
Trade-off analysis
API design

Behavioral & Cultural Fit

Communication clarity
Teamwork and collaboration
Adaptability
Ownership and accountability

Preparation Tips

1Brush up on core data structures and algorithms (Arrays, Linked Lists, Trees, Graphs, Hash Tables, Sorting, Searching).
2Review common system design concepts (Databases, Caching, Load Balancing, Message Queues, Microservices).
3Prepare examples for behavioral questions using the STAR method (Situation, Task, Action, Result).
4Understand Dunzo's business model and the challenges in the hyperlocal delivery space.
5Practice coding problems on platforms like LeetCode or HackerRank, focusing on medium-difficulty problems.

Study Plan

1

Data Structures & Algorithms

Weeks 1-2: Data Structures & Algorithms Fundamentals. Practice problems.

Weeks 1-2: Focus on fundamental data structures (Arrays, Linked Lists, Stacks, Queues, Hash Maps) and algorithms (Sorting, Searching, Recursion, Dynamic Programming). Practice problems related to these topics.

2

Advanced Data Structures & Algorithms

Weeks 3-4: Advanced DSA. More coding practice.

Weeks 3-4: Dive into more advanced data structures (Trees, Graphs, Heaps) and algorithms (Graph Traversal, Greedy Algorithms, Backtracking). Continue practicing coding problems.

3

System Design

Week 5: System Design Concepts. Review common questions.

Week 5: Focus on System Design. Study concepts like database design, caching strategies, load balancing, API design, and microservices architecture. Review common system design interview questions.

4

Behavioral & Company Research

Week 6: Behavioral Prep & Company Research.

Week 6: Prepare for behavioral questions. Think about your past experiences and how they align with Dunzo's values. Practice answering using the STAR method. Research Dunzo's mission and recent developments.

5

Mock Interviews

Week 7: Mock Interviews & Final Review.

Week 7: Mock interviews and final review. Practice coding problems under timed conditions and conduct mock system design and behavioral interviews.

Commonly Asked Questions

Design a system to track delivery partners in real-time.
How would you handle a sudden surge in delivery orders during peak hours?
Write a function to find the k-th largest element in an unsorted array.
Explain the difference between SQL and NoSQL databases and when to use each.
Tell me about a time you disagreed with a technical decision and how you handled it.
How do you ensure the scalability and reliability of a distributed system?
What are the trade-offs when choosing between a monolithic and a microservices architecture?
Describe a situation where you had to mentor a junior engineer.

Location-Based Differences

Bangalore

Interview Focus

Understanding of local market nuances and customer behavior.Adaptability to local tech stack and infrastructure.

Common Questions

How would you optimize a database query for a high-traffic e-commerce platform?

Describe a challenging bug you encountered and how you debugged it.

Tell me about a time you had to work with a difficult stakeholder.

Tips

Research common e-commerce or logistics challenges specific to the region.
Be prepared to discuss how you'd tailor solutions for the local user base.

Gurugram

Interview Focus

Experience with scaling systems in a rapidly growing market.Familiarity with distributed systems and microservices architecture.

Common Questions

How would you design a scalable delivery route optimization system for a new city?

Discuss your experience with cloud platforms like AWS or GCP.

How do you handle code reviews and ensure code quality?

Tips

Highlight projects where you've scaled systems or worked with microservices.
Be ready to discuss trade-offs in distributed system design.

Process Timeline

1
Data Structures and Algorithms45m
2
Architecture & Scalability60m
3
Behavioral & Team Fit30m

Interview Rounds

3-step process with detailed breakdown for each round

1

Data Structures and Algorithms

Coding round to assess DSA skills.

Technical Interview - CodingMedium
45 minSoftware Engineer (L3/L4)

This round focuses on your fundamental programming skills. You will be asked to solve coding problems that test your knowledge of data structures and algorithms. The interviewer will assess your ability to write clean, efficient, and correct code, as well as your approach to problem-solving.

What Interviewers Look For

Strong understanding of data structures and algorithms.Ability to translate requirements into working code.Clear communication of thought process.Attention to detail in coding.

Evaluation Criteria

Correctness of the solution
Efficiency of the solution (Time and Space Complexity)
Code readability and maintainability
Problem-solving approach

Questions Asked

Given an array of integers, find the contiguous subarray with the largest sum.

ArrayDynamic Programming

Implement a function to reverse a linked list.

Linked ListPointers

Find the shortest path between two nodes in a graph.

GraphBFSDFS

Preparation Tips

1Practice coding problems on platforms like LeetCode, HackerRank, or GeeksforGeeks.
2Focus on understanding the time and space complexity of your solutions.
3Be prepared to explain your thought process clearly.
4Practice writing code on a whiteboard or a shared editor.

Common Reasons for Rejection

Lack of fundamental programming knowledge.
Inability to articulate thought process.
Poorly structured or inefficient code.
2

Architecture & Scalability

System design round to assess architectural skills.

System Design InterviewHard
60 minSenior Software Engineer / Engineering Manager

This round evaluates your ability to design scalable, reliable, and maintainable software systems. You will be presented with a high-level problem and asked to design a system to solve it. This includes defining APIs, data models, and discussing architectural choices.

What Interviewers Look For

Ability to design complex systems from scratch.Knowledge of distributed systems principles.Experience with cloud technologies.Pragmatic approach to problem-solving.

Evaluation Criteria

Scalability of the proposed design
Reliability and fault tolerance
Clarity of design choices
Understanding of trade-offs
API design

Questions Asked

Design a system for a ride-sharing service like Uber or Ola.

System DesignScalabilityReal-time

Design a URL shortening service.

System DesignDistributed Systems

How would you design a notification system for millions of users?

System DesignScalabilityMessage Queues

Preparation Tips

1Study common system design patterns and architectures.
2Understand concepts like load balancing, caching, databases, and message queues.
3Practice designing systems for real-world applications (e.g., social media feeds, URL shorteners, ride-sharing apps).
4Be prepared to discuss trade-offs and justify your design decisions.

Common Reasons for Rejection

Inability to design scalable and reliable systems.
Lack of understanding of distributed systems concepts.
Poor trade-off analysis.
3

Behavioral & Team Fit

Behavioral round to assess cultural fit and soft skills.

Behavioral InterviewMedium
30 minHiring Manager / Team Lead

This round focuses on your behavioral aspects and how you fit into the team and company culture. You'll be asked questions about your past experiences, how you handle challenges, teamwork, and your career aspirations. The goal is to understand your working style and motivation.

What Interviewers Look For

Good communication and interpersonal skills.Ability to work effectively in a team.Proactiveness and ownership.Cultural fit with Dunzo's values.

Evaluation Criteria

Communication clarity
Teamwork and collaboration skills
Problem-solving approach in team settings
Adaptability and learning agility
Alignment with Dunzo's culture

Questions Asked

Tell me about a time you faced a significant technical challenge and how you overcame it.

BehavioralProblem Solving

Describe a situation where you had a conflict with a colleague and how you resolved it.

BehavioralTeamworkConflict Resolution

How do you stay updated with the latest technologies?

BehavioralLearning

Preparation Tips

1Prepare specific examples using the STAR method (Situation, Task, Action, Result) for common behavioral questions.
2Research Dunzo's values and mission.
3Be ready to talk about your strengths and weaknesses.
4Think about why you want to work at Dunzo and for this specific role.

Common Reasons for Rejection

Poor communication skills.
Lack of alignment with company values.
Inability to provide specific examples of past behavior.
Negative attitude or lack of enthusiasm.

Commonly Asked DSA Questions

Frequently asked coding questions at Dunzo

View all
Count Complete Tree NodesEASYArithmetic Slices II - SubsequenceHARDFind All Good StringsHARDBuild Array Where You Can Find The Maximum Exactly K ComparisonsHARDNumber of Ways to Form a Target String Given a DictionaryHARDWays to Make a Fair ArrayMEDIUMStone Game VIIMEDIUM