← Interview experiences
Got the offer

Software Engineer at Zomato

Difficulty
Process took
1-2 Weeks
Rounds
4
Format
Remote
Applied via
Referral

How it went

  • Don’t underestimate Android-specific design and optimization questions. They are often more important than raw algorithmic depth.
  • Prepare your past project stories well, especially ones where you improved app performance, handled concurrency issues, or designed clean architecture.
  • Stay confident, even informal calls can become evaluation rounds. Treat every conversation as part of the process.

What they would tell you

  • Don’t underestimate Android-specific design and optimization questions. They are often more important than raw algorithmic depth.
  • Prepare your past project stories well, especially ones where you improved app performance, handled concurrency issues, or designed clean architecture.
  • Stay confident, even informal calls can become evaluation rounds. Treat every conversation as part of the process.

How to prepare

  • For Android roles at top product companies, go beyond surface-level understanding of Views and Activities, prepare deeply for Coroutines internals, ViewModel lifecycle, and performance optimization techniques.
  • Expect to write code in Google Docs, practice explaining logic clearly and walking through test cases aloud.

Round by round

  1. 1

    Phone Screening45 min

    I had a direct conversation with the Engineering Manager, who shared the interview process and i discussed my current work, and dove into my Android experience and domain depth.

  2. 2

    Android Fundamentals + DSA60 min

    Android Internals: Coroutines (deep internals), Activity Lifecycle, RecyclerView, ViewModel structure Performance: App optimization techniques, rendering performance, memory issues Problem Solving: One DSA question asked initially, followed by an extension to test edge handling and scalability of approach

  3. 3

    Mobile System Design60 min

    I was asked to design a feature from the Zomato app, covering the entire flow from a system design perspective. I was asked to implement a known design pattern (I chose Strategy Pattern) within the context of Android.

    • Used a simple example around dynamic UI behavior change.

    • Implemented the pattern and explained where such patterns are practically used (e.g., handling multiple payment modes, user login strategies). I was given a medium-level DSA problem.

    • Wrote the code directly in Google Docs.

    • Explained the logic clearly with a dry run on sample test cases.

  4. 4

    Hiring Manager Discussion30 min

    Set expectations around team fit, project nature, and long-term vision Discussed compensation, joining location, growth path Light behavioral questions around past projects and work dynamics

What came up

MediumRemote2 3 years

A candidate-reported account, lightly edited. Interview processes change by team and date.

Sources

Hiring now

Zomato is hiring right now

landed applies to roles like these for you, on each company’s own site, with answers written for the role.

  • Software Engineer – Back End

    Gurugram, HR, India

Get 5x interviews

10 free auto-applies. No card.

Or practice this interview first