Scale Engineer

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·~7d

Experience·2 - 5 yrs

Comp band·US$180000 - US$250000

Interview time·135 min

Evaluation

What they measure.

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

Preparation

How to prepare.

Tips

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

Study plan

Fig · Study plan — 05 phases

01 / 05
01

Phase 01 of 05

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.

Questions

Commonly asked.

  • 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.

Locations

Regional differences.

Fig · Regions — 02 locations

01 / 02

Location

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.

Rounds

Round-by-round.

Expand a step for evaluation criteria, sample questions, and prep notes.

Med

Technical Interview - Coding · 45 min · Software 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 they 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

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

Sample questions

  • 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

Prep for this round

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

Common rejection reasons

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

DSA

Coding questions at Dunzo.

Frequently reported on Dunzo loops

View all at Dunzo

Other guides

More at Dunzo.