Academic snapshot
Marks: 6.5+ CGPA / 65% (candidate-reported)
Degree: B.E. / B.Tech / M.E. / M.Tech / MCA
Backlogs: None active
Year: Final-year and recent grads (~1 year)
Zomato Placement Papers 2026
Zomato, now under Eternal Limited, is a leading Indian restaurant aggregator and food delivery company founded in 2008. It is known for restaurant discovery, food delivery, and Blinkit quick commerce across India. Zomato recruits engineers for logistics, mobile apps, and large-scale consumer platform systems.
HQ: Gurugram, India
Employees: 5,000+
Revenue: $6B+ (Eternal group, reported scale)
Website: zomato.com ↗
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Zomato fresher eligibility for campus drives
Who this hub is for
- For: Students targeting SDE / Software Engineer roles on Zomato product teams - food delivery, restaurant discovery, and related consumer platforms - and often Zomato x Blinkit campus labels under Eternal.
- Not the same track: Pure delivery-partner ops, restaurant onboarding sales-only, or non-engineering support roles. Those bars do not map to this OA → DSA → design → Team Fit loop.
- Experienced hires: SDE-2+ loops add harder design, concurrency, and hiring-manager depth. Use fresher sections as a base, then read senior interview notes separately.
On-campus vs off-campus
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | Batch OA window, PPT timing, college CGPA list when printed | Coding bar, design depth |
| Careers portal / referral | Resume screen volume; branding may say Eternal / Zomato / Blinkit | Still expect OA + tech loop |
| Intern → full-time | Conversion interviews may skip a stage | You still defend projects and code |
Off-campus does not mean “easier coding.” It often means more applicants fighting the same 90-120 minute filter. If your CGPA sits near 6.5, spend energy on mocks, not on hunting a mythical lower cutoff blog post.
Degree, projects, and “is 6.5 enough?”
Is 6.5 CGPA enough? It matches the commonly reported floor. Selection still hinges on OA correctness and interview narration. A 6.7 with clean timed coding and a coherent tracking story beats an 8.8 that freezes on edge cases.
Branches: CS/IT/ECE/EE dominate shortlists. Related streams show up when DSA is solid. If your college lists only certain branches for a drive, read the notice.
Gaps and backlogs: Active backlogs are the usual blocker at offer time. Max ~1 year education gap appears in many write-ups - explain it with a skills story. Lying about CGPA or backlog status is an instant integrity fail in HR.
What helps the resume screen: One project you can defend end-to-end (stack choice, hardest bug, metric), any internship with ownership language, and honest tech keywords you can explain. Certificates are optional extras - DSA and OA mocks matter first. See certifications only after fundamentals are solid.
Branch & skills
Preferred: CS / IT / ECE / EE and related
Languages: Java, C++, Python, Go
Focus: DSA, debugging, food-tech design
Differentiator: Scale + customer-impact storytelling
Detailed eligibility criteria breakdown
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 6.5+ CGPA / ~65% across 10th, 12th, graduation | Some notices mirror college norms; verify every drive |
| Degree | B.E. / B.Tech / M.E. / M.Tech / MCA | Related computing degrees on many posts |
| Branch | CS, IT, ECE, EE (and related) | Strong DSA can help adjacent branches on some drives |
| Year | Final year + recent grads (~1 year) | Internship → conversion paths also appear |
| Backlogs | No active backlogs | Clear them before offer paperwork |
| Gap | Max ~1 year often cited | Explain with skills, not silence |
| Coding languages | Java, C++, Python, Go | Stick to one for OA + interviews |
Zomato CGPA criteria
Minimum CGPA required (candidate-reported): 6.5+ CGPA / 65% across 10th, 12th, and graduation is the commonly cited campus floor for fresher SDE roles. Treat it as a shortlisting filter when printed - Zomato still decides on OA correctness and interview narration. Always verify your drive notice.
Zomato shortlists on academics when the JD prints a floor, then filters hard on the Online Assessment. Clearing CGPA only gets you into the funnel - coding speed and debugging decide whether you see an interviewer.
Zomato does not publish one universal India cutoff for every SDE drive. Numbers below are candidate-reported from campus notices, JDs, and interview write-ups (as of August 2026). Your placement cell mailer always wins.
Zomato previous year paper PDFs
Download 2026 Zomato placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What Zomato previous year papers actually train
Zomato does not publish one permanent official paper set. “Previous year papers” on this site are pattern trainers for the first filter and early technical rounds - not leaked live assessments.
| Round (typical) | What to practice |
|---|---|
| Online assessment | Timed accuracy on 90-120 min OA: DSA + debugging (sometimes CS MCQs) |
| Technical 1-2 | Live coding narration: brute force → optimize → edge cases |
| Design / domain | Prompts around orders, tracking, catalog, payments, rate limits |
| Team Fit / HR | Values (customer focus, ownership, innovation), relocation, goals |
Themes that keep repeating (2024-2026)
- 2024 cycles: HackerRank OAs with CS MCQs + 3 coding on some Zomato x Blinkit campus drives. Medium-hard DSA (heaps, lists, graphs). Students who only drilled unsorted LeetCode without debugging practice lost easy marks on broken snippets.
- 2025 loops: More write-ups describe coding-heavy OAs (2-3 DSA + debugging), then DSA + system design even for SDE-1 (payments, rate limiters, tracking). Team Fit stays real - values language matters. Golang concurrency shows up when the team uses Go.
- 2026 prep expectation: Keep medium-hard DSA and debugging warm. Expect design rounds to stay fresher-depth (actors, APIs, bottlenecks) - not staff-level distributed systems. Treat PDF packs as pattern catalogs: Master the heap template, do not memorize that exact story.
How to use one paper set in a single sitting
- Timed: run a full 90-120 minute mock (DSA + debugging / MCQs if present) with the same language you will use on test day.
- Untimed review: rewrite the cleaner solution; list three edge cases you missed (empty cart, single restaurant, timeout).
- Map each coding miss to a theme (heap / graph / DP / string) and pull two cousins from coding questions.
- Spend 15 minutes explaining order tracking or idempotent payments out loud like a teammate, not a Wikipedia page.
- Log one STAR story the session reminded you of (ownership under a broken demo, customer-impact decision).
Related problems to practice
| Theme you saw in a set | What to drill next | Why Zomato asks it |
|---|---|---|
| Top-K / heaps | Frequent items, priority queues | Restaurant ranking, alert priority |
| Graph BFS/DFS | Shortest path, components | Delivery / zone intuition |
| Merge lists / intervals | K-way merge, windows | Batching, time slots |
| LRU / caches | Hash + DLL | Hot catalog pages |
| Debugging broken code | Off-by-one, null, wrong complexity | OA debugging section |
2024 PDFs often drill “merge K delivery queues.” Own the heap merge template - then drill a related problem with deadlines. That transfers to interviews; memorising the story text does not.
From application to offer at Zomato
Zomato / Eternal hires freshers through campus placement cells, the careers portal, referrals, and occasional challenge or internship conversion paths. After resume screen, the shape is product-company style: timed OA with debugging, then coding + domain interviews, Team Fit, then HR.
Application methods
Campus recruitment
Through college placement cells - PPT, then OA and interviews on a batch timeline. Some drives labeled Zomato x Blinkit.
Online applications
Apply on zomato.com / Eternal careers for early-career / fresher tech roles; follow the invite mailer for platform and duration.
Referrals
Employee referrals improve visibility. You still need passing OA code and clear interviews.
1. Resume / eligibility screen
Placement cell or recruiter checks degree, CGPA floor when printed (6.5+ / 65% commonly reported), backlogs, gap rules, and year of passing. Projects and internships help when volumes are high. This is a gate, not the hard filter - coding is.
2. Online Assessment - Zomato OA (90-120 min)
Candidate reports commonly describe a 90-120 minute assessment on HackerRank (or similar) with 2-3 DSA problems plus debugging. Some campus Zomato x Blinkit drives mix CS MCQs with coding. Exact section splits vary by drive and year; treat the table as a working map, not a sealed blueprint.
| Section (typical) | Questions (reported range) | Time feel | Focus |
|---|---|---|---|
| CS MCQs | ~0-20 (when present) | ~20-30 min | OS, DBMS, OOP, networks |
| Coding | 2-3 problems | ~60-90 min | Arrays, trees, graphs, strings, DP |
| Debugging | 1+ (when present) | Mixed in | Fix broken logic / edge cases |
Languages: Java, C++, Python, Go. Platforms: HackerRank appears often - confirm yours in the invite.
Pass bar in practice: Solve at least 2 problems with optimal, fully passing solutions. Roughly 10-15% advance on tough drives. Debugging accuracy matters when present.
Student tip: Spend 3-4 minutes skimming all coding prompts. Bank the solvable one first. Invent two edge cases before submit. Do not burn the clock proving a fancy algorithm if a clean O(n log n) already passes.
Example timing for a 120-minute OA
| Minute | Move |
|---|---|
| 0-5 | Skim full paper / all coding + debug statements; mark easy wins |
| 5-25 | MCQ block if present - skip sticky items, return later |
| 25-70 | Coding problem 1: restate → brute → optimize → code → tests |
| 70-105 | Coding problem 2 (+ start 3): same loop; harden edge cases |
| 105-120 | Debugging + flagged MCQs; do not open a new hard DSA rabbit hole |
Deeper OA notes and drills: Zomato Online Assessment.
3. Technical interview 1 - DSA (~45-60 min)
Video or onsite shared editor. Expect 1-2 DSA problems plus a short project warm-up. Patterns candidates report: Top-K / heaps, graphs, strings, DP, and data structures for real-time order-style updates.
You should:
- Clarify constraints (null inputs, duplicates, time windows)
- Narrate brute force → bottleneck → target complexity
- Code in your chosen language without syntax stalls
- Walk edge cases and complexity at the end
Interviewers care about debugging out loud. Silent staring after a failed mental test case is a common reject signal even when the idea was right.
Warm-up before the call: One easy array/hash problem in your interview language so syntax is warm. Keep water nearby; 60 minutes of narration is tiring.
Example narration shape (Top-K restaurants): “Brute force is sort-by-rating O(n log n). For top-k we can heap in O(n log k).” I’ll use a hash map then a min-heap of size k… Empty input returns empty; ties - I’ll state the rule before coding.” That 40-second plan already signals interview readiness.
4. Technical interview 2 - DSA / System Design (~45-60 min each)
Fresher depth, not staff-architect theater - but SDE-1 panels do ask design. Typical prompts:
- Food delivery tracking: actors, location updates, what fails offline
- Order management: place → pay → assign rider → deliver
- Restaurant catalog / search: ranking signals, empty results
- Payments: idempotency, retries, concurrency
- Rate limiter: why it matters for APIs
Start with users → data → APIs → bottlenecks. Plain language beats “we will use Kafka and Redis” with no requirements. Tie one resume project to consumer scale if it fits - catalog, orders, caching - without forcing it.
Worked mini-outline - delivery tracking:
- Actors: customer, restaurant, rider app, tracking service, notifications.
- Happy path: order confirmed → rider assigned → location pings → ETA updates → delivered.
- Failure: rider app offline → last-known location + stale ETA warning.
- Data: order_id, rider_id, lat/long stream, TTL on pings.
- Scale later: only after the above is clear - sharding by city is fine; do not lead with a buzzword diagram.
If the interviewer pivots to payments, talk idempotency keys, retries, and what the user sees on double-click checkout. That is enough for most fresher panels.
5. Managerial / team fit - ~45 min
Zomato values assessment: customer focus, ownership, innovation, dealing with ambiguity. Scenario questions (“restaurant is late - what do you do?”) and deep project ownership. Use STAR. Do not fake “I live on Zomato every day” without a real product observation.
6. HR / offer - ~20-30 min
Why Zomato / Eternal (not “food app” only), relocation to Gurugram / Bengaluru, notice period / exams, strengths-weaknesses with proof, CTC discussion. Know the ₹18-25 LPA SDE-1 total band so talk is grounded. Ask one real question about the team’s product surface (delivery, Blinkit, discovery) - it beats “what is the culture?”
| # | Round | Duration | What they check |
|---|---|---|---|
| 1 | OA (DSA + debug ± MCQs) | 90-120 min | Timed correctness |
| 2-3 | Technical (DSA / design) | 45-60 min each | Code + systems |
| 4 | Team Fit | ~45 min | Values + ownership |
| 5 | HR | 20-30 min | Fit, location, CTC |
Timeline from application to offer
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | PPT week then OA window |
| OA completion → shortlist | Few days common | Tough OAs shortlist ~10-15% |
| Interview loop | ~1-2 weeks | Tech → Team Fit → HR |
| Offer / paperwork | Days after final round | Written offer wins over verbal |
| End to end | ~2-4 weeks often | Off-campus can stretch |
Experienced-hire loops sometimes compress interviews into consecutive days or add in-office managerial chats - treat those as level-specific when reading senior write-ups.
OA pattern cheat-sheet
| Component | Focus | Prep move this week |
|---|---|---|
| Coding Q1-Q3 | Heaps, graphs, DP, strings | Two timed mediums + one hard attempt |
| Debugging | Broken logic, edges | Fix 5 buggy snippets under 20 min |
| Design follow-ups | Orders, tracking, payments | Explain one flow in 3 minutes aloud |
| Team Fit / HR | Values, relocation | Four STAR stories + city answer |
Zomato aptitude, coding & interview practice
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
A practical Zomato prep plan
If a Zomato invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Zomato sits around ₹18-25 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Zomato fresher eligibility for 2026 is candidate-reported, not one official published cutoff. Common campus/SDE baseline: B.E./B.Tech/M.E./M.Tech/MCA in CS, IT, ECE, EE, or related fields; final-year students and recent graduates (within ~1 year); typically 6.5+ CGPA / 65% across 10th, 12th, and graduation; no active backlogs; max ~1 year education gap preferred. Always verify the drive notice or Eternal/Zomato caree.
What you are training for: Zomato fresher SDE loops commonly run: Online Coding Assessment (90-120 min, 2-3 DSA + debugging on HackerRank or similar) → Technical interviews (2-3 rounds, DSA + system design) → Managerial / Team Fit (~45 min) → HR / offer (~20-30 min). Campus and off-campus timelines often land around 2-4 weeks from OA to offer.
Short version of the prep split: Treat Zomato like product hiring with a food-tech domain. Split time roughly: 50% DSA (including debugging practice), 20% system design lite (orders, tracking, catalog), 15% projects/CS, 15% Team Fit / values STAR stories. Clear timed OA mocks before deep interview prep. Languages: Java, C++, Python, or Go.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Oa pattern first: sit one untimed paper, then redo it under the real clock. Open the Zomato previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Zomato drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Zomato usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Zomato?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Star stories + one project walkthrough recorded on your phone. If you still have energy, redo only the questions you failed in week 2.
Where the hours should go
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Zomato-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Practice pages to open this week
- OA / assessment notes
- aptitude mock quiz
- coding question bank
- interview experiences
- HR question bank
- week-by-week guide
- previous year papers
- 2026 paper page
Use this hub for the Zomato story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 Zomato PDFs and never sitting one under a timer.
- Switching languages every weekend because a senior used a different one.
- Memorising HR answers before they can finish the OA.
- Ignoring the company-specific quirk on this page (unique round, exam name, or role band) and preparing like a generic service-company drive.
If you do one thing after reading this: schedule three timed Zomato papers on three different days, then interview prep on the leftovers.
If you are starting from a service-company prep base
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Zomato papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Zomato-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
10-day crash version
Days 1-3: one timed Zomato paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why Zomato. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
What to carry into the interview room
Know your project at the level of what broke and what you changed, not only the tech list on the resume. For Zomato, interviewers often poke the same hole the OA already tested - be ready to re-solve a warm question on a shared editor or whiteboard. If you used AI to draft code while practising, you still need to type it yourself on the day.
Tracking that does not become a second job
A single note with date, paper name, score/time, and three misses is enough. If you cannot name your last three Zomato mistakes, you are collecting content, not preparing.
Zomato fresher CTC in India (2026)
Figures below are candidate-reported India bands (as of August 2026). Actual offers depend on level, location (Gurugram / Bengaluru), hiring year, and written components (base / bonus / ESOPs).
Software engineer bands students ask about
| Band | Base (reported) | Typical total CTC (candidate-reported) | Notes |
|---|---|---|---|
| SDE-1 (fresher) | ~₹12-18 LPA | ₹18-25 LPA | Primary band for this hub |
| SDE-2 (2-4 YOE) | ~₹22-28 LPA | ₹28-35 LPA | Not the fresher campus default |
| Senior SDE | ~₹35-50 LPA | ₹50-65 LPA | Mid-senior |
| Lead+ | ₹60+ LPA | ₹80 LPA+ | Outside fresher prep scope |
Confirm base, joining bonus, ESOPs, and benefits language on the written offer. Do not treat blog midpoints as guarantees.
Other roles candidates mention
| Role | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| QA / SDET | ₹8-14 LPA | Automation emphasis |
| Data / ML (entry-mid) | ₹15-30 LPA | Different loop than SDE OA |
| DevOps (entry-mid) | ₹10-20 LPA | Cloud + reliability |
Benefits students actually care about
Policies vary by BU and year. Candidates commonly care about:
- Health insurance and wellness support
- ESOPs / equity language on the offer
- Learning support after joining (manager-dependent)
- Hybrid or office norms for Gurugram / Bengaluru teams
- Relocation support when moving cities - ask HR, do not assume
How to talk CTC in HR without sounding lost
Know the ₹18-25 LPA SDE-1 total context, ask how the package splits (fixed vs variable vs ESOP), and clarify joining date vs final exams. One calm clarifying question beats aggressive negotiation with no market anchor.
What’s changed in Zomato hiring lately
- Digital / off-campus assessments remain common for Zomato / Eternal alongside campus drives.
- DSA + debugging after resume screen stays the real filter - weak coding rarely survives.
- System design for SDE-1 shows up in more 2025 write-ups (payments, rate limiters, tracking) - not only senior loops.
- Zomato x Blinkit campus branding appears; prep the same DSA bar, customise quick-commerce stories if the JD says so.
- HackerRank-style platforms appear in recent write-ups; always trust your invite for duration and section list.
- Team Fit remains a real filter - values without proof fail late.
- Treat ₹18-25 LPA as a reported SDE-1 total band, not a promise for every role or college.
- End-to-end still often lands in the 2-4 week window.
Zomato placement FAQs
Process & papers
What is the Zomato placement process for freshers?
Typical fresher path: Online Coding Assessment (90-120 min, DSA + debugging) → Technical interviews (2-3) → Team Fit → HR. Timelines often land around 2-4 weeks. Confirm round names on your invite.
How many interview rounds does Zomato usually have?
Most fresher SDE loops report OA + 2-3 technicals + Team Fit + HR. Some drives merge managerial into Team Fit. Count the mailer, not a random blog.
Can I download Zomato placement papers PDF for free?
Yes. Free Zomato placement papers PDF and 2024-2026 style practice sets are on this site - pattern trainers with solutions, not leaked live papers. No registration for the main downloads. Start with the 2026 PDF or the paper archive.
What does the Zomato Online Assessment look like?
Candidate-reported OA is often 90-120 minutes with 2-3 DSA problems plus debugging. Some campus drives add CS MCQs. Languages: Java, C++, Python, Go. Platforms like HackerRank show up in write-ups - verify yours.
Eligibility & offer
What eligibility / CGPA do fresher SDE drives usually expect?
Commonly reported floor: 6.5+ CGPA / 65% across 10th, 12th, graduation; CS/IT/ECE/EE-related degrees; final-year or recent grads (~1 year); no active backlogs; max ~1 year gap. Zomato does not publish one universal cutoff - your drive notice overrides this page.
What is Zomato fresher salary in India?
Candidate-reported SDE-1 total CTC often lands around ₹18-25 LPA (base commonly cited ~₹12-18 LPA) as of August 2026. Main hubs: Gurugram, Bengaluru. The written offer letter is the only number that matters.
Do I have to relocate?
Gurugram and Bengaluru are the hubs candidates report most often. HR usually checks relocation and hybrid comfort. Be honest about constraints early.
Prep & Zomato-specific
How should I prepare for Zomato?
Split time roughly 50% DSA (incl. debugging), 20% design lite, 15% CS/projects, 15% Team Fit/HR. Clear timed OA mocks first. Keep one coding language. Details: preparation guide.
Which programming languages are allowed?
Java, C++, Python, and Go are the usual set. Confirm on the invite. Do not switch languages the week of the drive.
Is Zomato the same as Eternal or Blinkit?
Zomato is under Eternal Limited; Blinkit is the quick-commerce brand in the group. Drives may be labeled Zomato, Zomato x Blinkit, or Eternal. Prep the same DSA bar; customise domain stories to the JD team.
What food-tech topics should I revise?
Order management, delivery tracking, catalog/search, recommendations, payments/idempotency, and rate limiting at fresher depth: APIs, data, bottlenecks, failure modes in plain language. Practice sketches beat memorised architecture diagrams.
How is Zomato different from Swiggy or Flipkart for freshers?
All care about DSA. Zomato loops often emphasise food-tech + Team Fit values and may include Blinkit quick-commerce context. Swiggy is a peer food-tech bar; Flipkart skews e-commerce retail vocabulary. Prep DSA for all; customise domain stories per company.
What certifications help before joining?
For campus SDE, DSA + debugging + OA mocks + one strong project beat certificate stacks. Cloud or domain certs are optional extras after fundamentals. See certifications.
Any pro tip that actually changes outcomes?
Practice debugging under time, bank solvable OA problems first, keep an error log, and rehearse one tracking or payments explanation out loud before Team Fit. Correctness under time beats a half-finished clever solution.
Where can I read real interview experiences?
Start with Zomato interview experience on this site, then cross-check recent GeeksforGeeks / Medium write-ups for your target level. Patterns shift by year - use them as maps, not scripts.
Real Zomato interview notes from candidates
Fresher SDE loops (2024-2025)
Profile patterns that got selected: B.Tech CSE/IT/ECE, roughly 7.0-8.5 CGPA, tier-1 and tier-2 mix, one internship or a strong project, steady DSA practice rather than last-week panic.
Online assessment: Timed coding on HackerRank or similar. Clean, fully passing solutions on at least two problems beat partial cleverness. Debugging accuracy helped when present. Shortlist rates on tough drives sat around 10-15%.
Technical rounds: Coding such as Top-K restaurants (heap), graphs, DP mediums. Design chat around tracking, orders, and payments - plain explanations worked better than buzzwords. Project deep dive: stack choice, hardest bug, what you would rebuild. Later rounds sometimes leaned into rate limiters and concurrency.
Team Fit / HR: Why this product? Ownership under ambiguity? Customer-impact story? Relocation comfort? Keep answers short: situation → what you did → result.
Takeaway candidates repeated: clear DSA plus a coherent order/tracking story beats a high CGPA with weak explanation. Talking through the approach before coding mattered as much as the final snippet.
What hurt other candidates in the same cycles: coding before clarifying constraints; skipping debugging prep; treating Team Fit as a formality; system-design jargon without a simple bottleneck story; optimising one hard OA item while leaving an easy problem incomplete.
Sourced colour
An SDE-1 candidate posting on 22 August 2025 described a virtual technical round, then noted Round 2 “was a high-level system design round, even though it was for an SDE-1 role,” focused on a payments backend (idempotency, retries, concurrency) before an in-office managerial/HR conversation on motivation and compensation (Medium). Zomato’s fresher bar can still include design thinking, not only DSA.
A 2024 on-campus SDE-1 candidate for Zomato x Blinkit wrote on GeeksforGeeks that 220 students sat a 90-minute HackerRank OA (20 CS MCQs + 3 coding), with 18 shortlisted. In Round 1 they said “I used illustrations and diagrams to explain concepts, which seemed to impress the interviewer,” covering RAG, Docker/K8s, and DSA. Round 2 pushed Golang concurrency and a rate limiter; three students, including them, got offers after HR.
Freshers should copy the signals: passing tests, design clarity, and Team Fit proof - not memorize those exact prompts.
More fresher narratives: Zomato interview experience.