---
title: Zomato Data Engineer Interview Questions (2026 Guide)
description: Real Zomato data engineer interview questions — SQL, data modeling and pipeline design for search ranking and restaurant-catalog freshness — with a prep plan.
url: https://usegreenroom.app/blog/zomato-data-engineer-interview-questions
last_updated: 2026-07-25
---

← Back to blog

India · Zomato

# Zomato data engineer interview questions

July 25, 2026 · 9 min read

![Zomato data engineer interview questions — cover from Greenroom, the AI mock interviewer](/assets/blog/zomato-data-engineer-interview-questions-hero.webp "")

Rohan had just finished explaining a tidy pipeline for restaurant search rankings when the interviewer asked a question that had nothing to do with tidiness: "A restaurant marks itself closed at 10:58pm. Your search index still shows it as open until the next batch run at midnight. Someone orders anyway. Whose bug is this?" Rohan started to answer "the frontend's," then stopped, because he realized the honest answer was "mine" — and spent the next ten minutes redesigning the freshness guarantee on his own pipeline, live.

That's the real texture of a **Zomato data engineer interview**: it's less about writing a correct query once and more about noticing where staleness, ordering and edge cases quietly break a design that looked fine on the whiteboard. I built Greenroom after freezing in exactly this kind of live, follow-up-driven round — so this guide covers the real SQL, modeling and pipeline questions Zomato asks, with a prep plan built around speaking your reasoning out loud.

## The Zomato data engineer interview process

The **Zomato data engineer interview process** runs four stages:

- **Online coding assessment** — 90–120 minutes: 2–3 DSA problems plus a debugging exercise.
- **Technical rounds (2–3)** — DSA combined with low-level design and system design, with SQL and data-modeling depth for DE roles.
- **Managerial round** — run by an Engineering Manager, focused on ownership and how you handle ambiguity.
- **HR round** — compensation, notice period, culture fit.

Most candidates report the loop wraps in **2–3 weeks**. The condensed round-by-round breakdown lives on our [Zomato Data Engineer interview prep page](/prep/zomato-data-engineer-interview) — this post goes deep on the actual questions.

## Zomato data engineer SQL interview questions

SQL comes live, shared-screen, and it's graded on correctness under edge cases as much as syntax. Reported shapes:

- **Write a SQL query to find the 7-day rolling retention of users.**
- **Find restaurants whose menu was updated more than 5 times in the last 24 hours** (a catalog-churn signal).
- **Return each user's top 3 most-ordered cuisines, breaking ties consistently.**
- **Compute a 3-day trailing average of order volume per city:**

```sql
-- 3-day trailing average of order volume per city
SELECT
  city,
  order_date,
  AVG(order_count) OVER (
    PARTITION BY city
    ORDER BY order_date
    ROWS BETWEEN 2 PRECEDING AND CURRENT ROW
  ) AS trailing_3day_avg
FROM daily_city_orders
ORDER BY city, order_date;
```

The follow-up is rarely about the query itself: *what if two menu-update events for the same restaurant arrive out of order — does your query silently pick the wrong one?* Our [SQL interview questions guide](/blog/sql-interview-questions) covers the window-function patterns underneath this question family.

<!--verdict-->The core truth: Zomato's DE bar rewards candidates who volunteer the edge case before being asked — late data, out-of-order events, ties. Getting the happy-path query right is table stakes; catching what breaks it is what separates a pass from a strong pass.<!--/verdict-->

## Data modeling questions

The modeling round anchors to domains Zomato runs at real scale:

- **Design a data model for restaurant catalog and menu management.** Grain first: is one row a menu item, a menu-item-price-version, or a daily snapshot?
- **When would you choose a star schema over a wide denormalized table for a search-ranking feature store?**
- **Explain SCD Type 1 vs Type 2 — and where Zomato would need Type 2** (menu price history, restaurant open/closed status history).
- **How do you partition a fact table queried by date platform-wide, and by restaurant individually for owner dashboards?**

Interviewers reward "what's one row?" before any table gets drawn. Jumping straight into schema names reads as pattern-matching rather than reasoning.

## Pipeline and system design questions

The design round is a data-flavored system design interview, usually anchored to search or notifications:

- **Design a pipeline that keeps the restaurant search index fresh within seconds of an open/closed status change.**
- **Batch or streaming for updating a restaurant's live delivery-time estimate — defend the choice.**
- **A backfill needs to reprocess 2 days of order events without corrupting the search-ranking feature store. Walk me through it.**
- **How do you handle late-arriving or out-of-order menu-update events in a partitioned warehouse?**

Structure wins over vocabulary: state your freshness/latency requirement out loud, propose ingestion → buffer → storage → transform → serve, then volunteer failure modes — idempotent writes, dead-letter queues, ordering guarantees — before being asked. The general framework is in our [data engineer interview questions guide](/blog/data-engineer-interview-questions).

![Zomato data engineer interview loop — online assessment, technical rounds, managerial round, HR](/assets/blog/zomato-data-engineer-interview-questions-diagram.webp "Coding, design and fundamentals chain inside the same round more often than at most companies.")

## Behavioral and managerial-round questions

The managerial round, run by an Engineering Manager, is where ownership under ambiguity gets tested:

- **Tell me about a data quality incident you owned end to end, and how you prevented a repeat.**
- **Describe a time stale data caused a real user-facing bug. What was your fix, and was it a patch or a redesign?**
- **Walk me through a modeling decision you'd make differently with hindsight.**

Answers need real numbers — "improved data freshness" loses to "cut index staleness from 15 minutes to under 30 seconds." Our [data engineer interview questions guide](/blog/data-engineer-interview-questions) has more STAR-shaped examples for technical behavioral rounds.

## LeetCode, StrataScratch, a friend's PDF — where each fits

An honest map of the usual prep stack for this specific loop:

- **LeetCode** — partially calibrated; the DSA section in Zomato's online assessment is real, but the technical rounds lean more on SQL, modeling and system design than pure algorithms.
- **StrataScratch / DataLemur** — close in shape to Zomato's SQL screens; good for reps, silent on the live edge-case follow-ups.
- **GeeksforGeeks interview experiences / a friend's WhatsApp PDF** — useful for calibrating recent loops, but treat as anecdotes since specific questions rotate by team.
- **ChatGPT** — fine for generating extra practice prompts or reviewing a written answer; it won't interrupt your design mid-sentence with "what if that event arrives late?" the way a real interviewer will.
- **Greenroom** — the spoken layer. [Ari, the AI interviewer](/), runs SQL-reasoning, modeling and pipeline-design rounds out loud with live edge-case follow-ups, scoring the structure a managerial round actually listens for. Pair it with the fundamentals above.

## How to prepare for the Zomato data engineer interview

- **Week 1:** SQL depth — window functions, trailing averages, dedup, ranking with ties — explained out loud, not just passed against test cases.
- **Week 2:** data modeling — catalog, menu and search-ranking domains, grain declared first, plus SCDs and partitioning trade-offs.
- **Week 3:** pipeline design — batch vs streaming, freshness guarantees, backfills, out-of-order events — talked through as full designs.
- **Week 4:** behavioral stories with real numbers, rehearsed until they survive a "tell me more about that decision" follow-up.

If you're interviewing at other Indian scale-ups in parallel, the loops rhyme but the specific stress test differs — our [Flipkart data engineer interview guide](/blog/flipkart-data-engineer-interview-questions) and [Swiggy data engineer interview guide](/blog/swiggy-data-engineer-interview-questions) cover where each diverges.

## Frequently asked questions

### What questions are asked in a Zomato data engineer interview?

Advanced SQL (window functions, trailing averages, dedup, ranking with ties), data modeling (star schema, SCDs, grain and partitioning for catalog and search), pipeline/system design for search-index freshness, and behavioral questions about data quality incidents.

### How many rounds are there in the Zomato data engineer interview?

Typically four: an online coding assessment, 2–3 technical rounds combining DSA with low-level and system design, a managerial round with an Engineering Manager, and HR. Most candidates report 2–3 weeks end to end.

### Is the Zomato data engineer interview hard?

The SQL and modeling bar is high but predictable in shape. What surprises most candidates is how often the follow-up targets a data-freshness or ordering edge case rather than the happy-path query.

### Does the Zomato data engineer interview include DSA coding?

Yes — the online assessment has 2–3 DSA problems plus a debugging exercise. Technical rounds then combine DSA with low-level design and system design, weighted more toward SQL and modeling for DE roles.

### What's the hardest part of the Zomato data engineer loop?

Volunteering edge cases — late-arriving events, out-of-order updates, ties — before the interviewer has to ask. Candidates who only defend the happy-path design tend to lose points on follow-ups.

### How do I prepare for the Zomato data engineer interview in one month?

Week 1 SQL window functions and trailing aggregates, week 2 data modeling for catalog and search, week 3 pipeline design with a freshness guarantee built in, week 4 spoken behavioral stories with real numbers — with at least one full spoken mock per round type before the real loop.

CTA: Zomato's DE loop is lost on the edge-case follow-up more often than the first answer. [Greenroom](https://usegreenroom.app/) runs mock SQL-reasoning, modeling and pipeline-design rounds with Ari, pushing edge-case follow-ups the way a real interviewer would. Free to start. Not sure where to start? Read our full [AI mock interview guide](/blog/ai-mock-interview).