Interview experience
Meesho Interview Questions
Overview
Section titled “Overview”Meesho’s fresher loop combines a long, multi-problem online assessment with a dedicated low-level-design machine-coding round, then closes with a hybrid round that mixes core CS fundamentals (OS, networks, SQL) back in alongside behavioral questions.
Meesho interview process at a glance
Section titled “Meesho interview process at a glance”| Round | Duration | What they test |
|---|---|---|
| Online Assessment | Up to ~165 min | 3 medium-hard coding problems |
| Machine Coding / LLD | ~60 min | Build a working system - class design, clean executable code |
| Technical Round(s) | 45-60 min each | DSA + system design (orders/logistics) + project discussion |
| Managerial / HR | 30-45 min | OS/networks/SQL fundamentals + behavioural fit |
Online Assessment
Section titled “Online Assessment”A long, timed coding test - up to roughly 165 minutes - with 3 medium-hard problems, noticeably more time pressure than a typical single-hour OA.
Common questions
- Array/string manipulation problems at medium-hard difficulty
- Tree and graph traversal problems
- Top-K / heap-based problems (e.g. top-K frequent elements)
Machine Coding / Low-Level Design
Section titled “Machine Coding / Low-Level Design”Roughly 60 minutes building a working system from scratch - candidates report tasks like a car-pooling system. The interviewer cares more about how you structured your classes and modules than how fast you finished.
Common questions
- Design and implement a car-pooling or booking-style system with clean class boundaries
- Justify your object-oriented design choices and how you’d extend the system
- Handle edge cases (capacity limits, cancellations, conflicting bookings) in your design
- Explain why the code is clean and executable, not just functionally correct
Technical Round(s)
Section titled “Technical Round(s)”Further DSA problems combined with system-design questions scoped to Meesho’s marketplace domain, plus a detailed walkthrough of a resume project.
Common questions
- Shortest path / BFS-style problems on a grid or graph
- System design for order or logistics flows at marketplace scale
- Discussion on catalogue search, reseller workflows, or recommendation systems - inputs, outputs, what breaks at scale
- Your project’s architecture, hardest bug, and what you’d rebuild
Round-by-round narratives are on the Meesho interview experience page.
Managerial / HR round
Section titled “Managerial / HR round”A closing round that blends core CS fundamentals with behavioral questions - candidates describe being asked about OS, networking, and SQL here, not just motivation and culture fit.
Common questions
- OS fundamentals (processes, scheduling, memory) and basic networking concepts
- SQL query and schema-design questions
- Tell me about a time you made a call with incomplete data in a fast-moving situation
- Describe a conflict with a cross-functional partner (ops, a reseller, or another team) and how you resolved it
Sample answer frameworks for each of these are on the Meesho HR interview questions page.
Frequently asked questions about Meesho interviews
Section titled “Frequently asked questions about Meesho interviews”What is the Meesho interview process for freshers?
Meesho’s process typically runs 4-5 stages: 1. Application (on-campus via college placement cell, off-campus via Meesho Careers, or referral). 2. Online Assessment (up to ~165 min) - 3 medium-hard coding problems. 3. Machine Coding / Low-Level Design round (~60 min) - build a working system from scratch (e.g. a car-pooling or booking system), judged on class design and clean, executable code. 4. Technical Interview(s) - further DSA, system design, and project discussion. 5. Managerial/HR round - technical-cum-behavioral questions covering OS, networks, SQL, plus culture fit and offer. Total duration is roughly 2-3 weeks.
What questions are asked in Meesho interviews?
The Online Assessment leans on medium-hard array, string, tree, and graph problems. Machine coding rounds ask you to design and build a working system - candidates report tasks like a car-pooling system - graded on class structure and whether the code runs cleanly, not just the approach. Technical rounds also probe domain topics like catalogue search, reseller workflows, and recommendation systems in plain language. The closing round mixes OS, computer networks, and SQL fundamentals with behavioral questions on ownership and ambiguity.
How many rounds are there in the Meesho interview?
Meesho typically runs 4-5 touchpoints: an Online Assessment, a Machine Coding/LLD round, one or two further Technical Interviews (DSA, system design, project deep-dive), and a closing Managerial/HR round that often blends technical fundamentals with behavioral questions. Some drives compress stages depending on role and experience level.
What is the Meesho technical interview like?
The Machine Coding round (about 60 min) focuses on low-level design - candidates report being asked to build a working car-pooling or similar system, with the interviewer more interested in class/module structure and whether the code is clean and executable than in raw speed. Later technical rounds add system-design questions scoped to Meesho’s marketplace domain (orders, logistics, catalogue search) plus a deep project discussion. The closing round often circles back to OS, networking, and SQL fundamentals alongside behavioral questions.
How should I prepare for Meesho interviews?
Practice medium-hard DSA across arrays, strings, trees, and graphs for the OA. For the machine coding round, practice designing and building small systems end-to-end with clean class boundaries rather than just getting something to run. Revise OS, computer networks, and SQL fundamentals, since Meesho’s later rounds test them directly alongside behavioral questions. For domain questions, be ready to explain catalogue search or reseller workflows in plain language - inputs, outputs, what breaks at scale.
What mistakes do candidates commonly make in Meesho interviews?
Coding before clarifying constraints in the OA, treating the machine-coding round as a race instead of a design exercise (Meesho graders explicitly weigh class structure over speed), and treating the closing HR/managerial round as a formality when it still tests OS/networking/SQL fundamentals. Candidate reports consistently note that a clear, working low-level design beats a fast but disorganised one.