What questions are asked in Meesho interviews?

Meesho interviews commonly cover DSA coding (Top-K frequent elements in order stream; Shortest path in a warehouse grid), core CS (OOPs, DBMS/SQL, OS basics where relevant), project discussion, and topics tied to the business such as catalogue search, reseller workflows, recommendation. Behavioural questions check ownership, teamwork, and why Meesho.

How many rounds are there in the Meesho interview?

Meesho typically has 4 stages: Online Assessment (90 min), Technical Round 1 (45–60 min), Technical Round 2 (45–60 min), HR (20–30 min). Some drives skip GD or merge HR with managerial. Always check the mailer for that cycle.

How should I prepare for Meesho interviews?

For Meesho, prioritise DSA practice with timed mocks, revise OOPs and SQL, prepare a crisp project narrative, and read up on catalogue search and reseller workflows. Use STAR for behavioural answers and ask one thoughtful question at the end.

Meesho Interview Experience 2025–2026 — Real Candidate Stories

Meesho interview experience

These write-ups reflect how Meesho fresher interviews usually go — campus and off-campus. Patterns shift by year and role, so use this as a prep map, not a script.

Meesho placement process includes: 1. Application (on-campus via college placement cell, off-campus via Meesho Careers portal, or through referrals), 2. Online Assessment (OA) - 2-3 coding problems (60-90 minutes), 3. Technical Interviews (2 rounds) - DSA, system design, projects (45-60 minutes each), 4. Managerial Round - Technical depth and behavioral fit (45 minutes), 5. HR Interview - Behavioral and offer (20-30…

Most drives expect a clean academic record (often around 6.0–6.5+ CGPA with no active backlogs). Candidate-reported detail: Meesho eligibility criteria for freshers 2026 include: Minimum 70% or 7.0+ CGPA in 10th, 12th, and graduation. Degree required: B.Tech/B.E./M.Tech in Computer Science, IT, ECE, or related fields. Final year students and…

Fresher offers (candidate-reported) often land around ent Engineer - SDE-1 role) ranges from ₹25-35 LPA total compensation in India. This includes base salary (₹15. Treat numbers as directional — confirm on your offer letter.

Round-wise process

Round	Duration	What they test
Online Assessment	90 min	2–3 coding problems
Technical Round 1	45–60 min	DSA + project discussion
Technical Round 2	45–60 min	System design (orders / logistics)
HR	20–30 min	Behavioural + culture fit

Real interview experiences

Experience 1: SDE / Software Engineer (2025)

Profile: B.Tech CSE, 7.8–8.4 CGPA, tier-2 college, 1 internship, decent DSA practice (150+ problems)

Online / written round

Focus stayed on problem-solving speed and clean code, not trick questions.
Cleared with full or near-full test cases; shortlist mail came in a few days.

Technical rounds

Coding: Top-K frequent elements in order stream — approach used: heap / bucket sort. Interviewer cared about complexity and edge cases.
Follow-up coding: Shortest path in a warehouse grid — BFS.
Domain discussion around catalogue search and reseller workflows — they wanted practical trade-offs, not buzzwords.
Project deep dive: why you chose the stack, what broke in production/testing, what you would redo.

HR / managerial

Why this product?
Example of working with ambiguous requirements
Keep answers short and specific. Name the conflict, what you did, and the result.

Result: Selected What helped: Explaining approach before coding, admitting unknowns early, and linking project work to Meesho’s domain (catalogue search).

Experience 2: SDE / Software Engineer (2024–2025)

Profile: B.Tech IT / ECE, 7.2 CGPA, strong projects, average competitive programming

What differed

OA felt tougher on time; one medium-hard problem needed an optimised solution to clear the bar.
Second technical leaned more into recommendation and system design basics (APIs, DB choice, failure modes).
Coding warm-up: Merge overlapping delivery slots — interval merge.

Mistakes to avoid

Jumping into code without clarifying constraints
Treating HR as a formality — Meesho still filters on communication and intent
Memorising system design jargon without a simple capacity / bottleneck story

Result: Selected after a managerial / HR round Takeaway: For Meesho, consistent DSA plus a clear story on catalogue search beats a perfect CGPA with weak explanation.

Questions that come up often

Coding / technical

Top-K frequent elements in order stream — typically expects heap / bucket sort
Shortest path in a warehouse grid — typically expects BFS
Merge overlapping delivery slots — typically expects interval merge
Discussion on catalogue search and reseller workflows — capacity, failure modes, simple APIs
Project deep dive — architecture, hardest bug, what you would change

HR / behavioural

Why this product?
Example of working with ambiguous requirements
Weekend / on-call comfort
Relocation

Practical tips for Meesho

Practise DSA under a timer. Clearing the OA matters more than polishing a perfect resume line.
For domain rounds, be ready to talk about catalogue search in plain language — inputs, outputs, bottlenecks.
Revise OOPs and SQL; many Meesho panels still open with fundamentals.
Keep HR answers concrete. One story with a clear result beats five buzzwords.
If you do not know something, say so and outline how you would find out. Guesswork wastes the round.

Meesho HR Interview Questions — common HR questions and how to answer them
Meesho Preparation Guide — round-wise prep plan
Meesho Coding Questions — practice problems with approaches
Meesho Previous Year Papers — past papers and patterns
Meesho Placement Papers — company overview, eligibility, and process

Last updated: August 2026