Zomato's data-engineering rounds probe bursty stream processing, cohort SQL, and warehouse workload isolation, reflecting a delivery business with sharp demand peaks.
In 2026 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.
About Zomato
Listed Indian food-tech (food delivery + dining out + Hyperpure B2B + Blinkit quick commerce).
Recruiter screen and technical pre-screen
SQL and data-manipulation round
Streaming pipeline and warehouse-design round
Hiring-manager and behavioural round, then offer
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.
Sourced from 2+ candidate post-mortems. Hit Practice to answer any one with AI voice feedback.
2 more questions. Sign up to unlock all
Sign up free: unlock all questionsThe 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
To answer this question well, HireStepX recommends the Burst-and-Isolate approach: Handle bursty delivery streams with autoscaling and event-time windowing, write cohort SQL with self-joins, and isolate operational from analytical warehouse workloads Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Burst-and-Isolate approach: Handle bursty delivery streams with autoscaling and event-time windowing, write cohort SQL with self-joins, and isolate operational from analytical warehouse workloads Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Burst-and-Isolate approach: Handle bursty delivery streams with autoscaling and event-time windowing, write cohort SQL with self-joins, and isolate operational from analytical warehouse workloads Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Burst-and-Isolate approach: Handle bursty delivery streams with autoscaling and event-time windowing, write cohort SQL with self-joins, and isolate operational from analytical warehouse workloads Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Burst-and-Isolate approach: Handle bursty delivery streams with autoscaling and event-time windowing, write cohort SQL with self-joins, and isolate operational from analytical warehouse workloads Ground your answer in a specific real example from your own experience.