Skip to main content
HireStepX is now in Beta! Be among the first to practise smarter and get hired on proof.
Technical · Zomato

Zomato Data Engineer Interview Questions India 2026

Zomato's data-engineering rounds probe bursty stream processing, cohort SQL, and warehouse workload isolation, reflecting a delivery business with sharp demand peaks.

By the HireStepX editorial team · How we source and label this

Questions12
Rounds4
Intense3 of 12
FrameworkBurst and isolate
Try it · Zomato question 1 of 10
Standard

Reverse a linked list in O(1) extra space. Then explain when you'd use this in production.

Think of your answer first, then reveal how to structure it.
Practise this out loud

Expect a pipeline round on near-real-time per-city delivery-partner utilisation metrics from order and location events that survives dinner-time bursts, a SQL round on ranking restaurants by repeat-order rate within each city (self-joins and window functions), and a modelling round on a warehouse that serves operational dashboards and ad-hoc analyst queries without resource contention. Interviewers reward reasoning about autoscaling, back-pressure, event-time windowing, and workload isolation over generic batch ETL. Ground answers in real delivery-operations analytics.

Practice questions

  1. 01

    Reverse a linked list in O(1) extra space. Then explain when you'd use this in production.

    Standard
    Practise
  2. 02

    What is the difference between a class and an object? Give an example.

    Warm-upTCS Ninja/Digital tracks lean heavily on CS fundamentals: OOP, OS, DBMS, SQL basics. Expect rapid-fire Q's, not deep dives.
    Practise
  3. 03

    Write a SQL query to find the second-highest salary in a department.

    Warm-up
    Practise
  4. 04

    What is normalisation in databases? When would you de-normalise?

    Warm-up
    Practise
  5. 05

    What's the difference between a stack and a queue? Give a real-world use case for each.

    Warm-up
    Practise
  6. 06

    Given a stream of integers, design a data structure that returns the median in O(log n).

    Intense
    Practise
  7. 07

    You have a service that's slow only on Tuesdays. Walk me through how you'd debug.

    StandardGoogleyness: structured debugging, hypothesis-driven, instrumentation-first.
    Practise
  8. 08

    Here's 200 lines of payment-processing code with several intentional bugs. Find them and explain the production impact of each.

    IntenseStripe's signature 'bug bash' round. Off-by-one, race conditions, wrong error handling, edge cases in money math. Communicating impact > finding all bugs.
    Practise
  9. 09

    Explain webhooks vs. polling for a developer who has never built a payment integration. You have 4 sentences.

    StandardStripe values writing clarity above almost everything. Length-constrained explanation tests prioritisation of ideas.
    Practise
  10. 10

    Walk me through Razorpay's fraud-detection model. How would you reduce false positives without increasing chargeback losses?

    IntenseRazorpay ML rounds tie model decisions to ₹ impact, chargeback cost vs. blocked-good-txn cost. Pure ML answers without business framing fail.
    Practise
2 more questionsCreate a free account to see the full set and practise any of them with scoring.Unlock all questions
Prep notes

How to walk in ready.

The typical Zomato recruitment process has 4 stages: Recruiter screen and technical pre-screen → SQL and data-manipulation round → Streaming pipeline and warehouse-design round → Hiring-manager and behavioural round, then offer.

Zomato typically conducts 4 interview rounds: Round 1 (45-60 min): SQL round on cohort metrics and self-joins; Round 2 (60 min): streaming pipeline round under bursty load; Round 3 (45-60 min): warehouse-modelling and workload-isolation round; Round 4 (45 min): behavioural and hiring-manager round.

HireStepX recommends the Burst and isolate framework for this type of interview: Handle bursty delivery streams with autoscaling and event-time windowing, write cohort SQL with self-joins, and isolate operational from analytical warehouse workloads.

TCS Ninja/Digital tracks lean heavily on CS fundamentals: OOP, OS, DBMS, SQL basics. Expect rapid-fire Q's, not deep dives.

Googleyness: structured debugging, hypothesis-driven, instrumentation-first.

Stripe's signature 'bug bash' round. Off-by-one, race conditions, wrong error handling, edge cases in money math. Communicating impact > finding all bugs.

Near-real-time per-city delivery-partner utilisation metrics from order and location events, with autoscaling, back-pressure, and event-time windowing to survive bursty dinner-time load.

Cohort-style metrics like ranking restaurants by repeat-order rate within each city, using self-joins and window functions partitioned by city.

Practice

Rehearse the room before you enter it.

Run a mock Zomato interview and get scored feedback on every answer.