Zomato filters on DSA, then probes design and ownership with food-delivery context. Code correctness first; domain stories second.
What actually rejects people
Generic food-delivery buzzwords without a real design or code plan.
First round: Zomato OA + DSA/system interviews
Time split that matches how candidates report outcomes (not a marketing pie chart):
DSA 50%
Domain scenarios 20%
CS/projects 15%
Behavioral 15%
Patterns are from student reports and vary by role and drive. Trust your college placement email over blog folklore.
Stage
Time
What they check
OA
timed
DSA coding
Technical
multiple
DSA + design/projects
HR / culture
varies
Customer focus, ownership
Master DSA fundamentals - practice arrays, trees, graphs, dynamic programming on LeetCode and HackerRank
Study system design basics - understand scalable architecture, database design, API design
Practice coding problems - solve 100+ problems in Java, C++, Python, or Go
Prepare for behavioral questions - use STAR format for Zomato values (customer focus, innovation, ownership)
Review core CS subjects - OOPs, databases, networking basics
Practice mock online assessments - improve time management and problem-solving speed
One timed block that matches Zomato’s first round (coding OA)
Log misses: topic + why you failed (speed, concept, carelessness)
Re-solve yesterday’s misses cold
Twice a week: 10 minutes of resume/project narration out loud
Week
Focus
Exit criteria
1-2
Core DSA
Baseline mock logged
3-4
Graphs, heaps, hashing
Delivery/ranking style problems attempted
5-6
System design lite + projects
Catalog/order flow explained
7-8
Mocks + behavioral
Weak topics closed
Order problems by confidence after a 3-4 minute skim
Passing test cases beats a brilliant half-solution
Invent edge cases before submit; watch timeboxes
Restate → brute force → optimize → code → test
If domain comes up, reason about inventory/latency - do not recite blogs.
Tie CS answers to a project when it strengthens the point
Why Zomato, why this team/role, location flexibility
STAR with a metric; pick 2-3 real company values and prepare proof
Medium DSA grind
Order/restaurant/delivery design at SDE-1 depth
STAR stories on customer impact
Medium DSA
Debugging under time if OA includes it
Projects with metrics
Inventory, ranking, routing scenarios
Caching / read-heavy API intuition
Full-length mock every other day
Light revision only - no new rabbit holes
Sleep, ID proofs, machine/network checklist for test day
30 days out: weekly full OA-style mocks; close weak DSA patterns; draft STAR stories.
7 days out: alternate mock / review days; re-solve misses cold; no new patterns.
Day before: skim notes, check machine/network/ID logistics, sleep.
Generic food-delivery buzzwords without a real design or code plan - fix this first
Preparing only interviews while failing Zomato’s first round
Collecting notes without timed mocks
Listing five frameworks on the resume and defending none
Changing language/stack one week before the drive
Only ecommerce talk, weak code
Swiggy · Flipkart · Paytm · Phonepe · Meesho · Blinkit
Next step: Run one timed mock this week that matches Zomato’s first round (coding OA), then build the weeks around your weakest section - not around what is most fun to study.