Meesho Software Engineer interview typically runs 4 rounds: online assessment, DSA, machine coding/LLD, and manager or HR. It usually takes 1-3 weeks and leans heavily toward design and practical implementation.
$4800K
Avg. Base Comp
$5000K
Avg. Total Comp
4-5
Typical Rounds
2-4 weeks
Process Length
We’ve seen a clear pattern across Meesho candidate experiences: the company cares less about flashy algorithm tricks and more about whether you can turn a messy product requirement into a clean, workable system. Multiple candidates reported prompts like a payment system, ordering cart, polling system, parking system, grocery store, and ride or food delivery flows. That repetition matters. Meesho seems to favor engineers who can structure edge cases, data flow, and tradeoffs without getting lost in theory. Even when DSA shows up, it’s often framed around practical implementation or explanation, not just arriving at the right answer.
A second recurring theme is that they want candidates to be vocal and specific. One candidate noted that the machine coding round began with 15 to 20 minutes of Q&A, and another described an LLD round where they were expected to explain SRP before coding. That tells us Meesho is listening for how you think, not just what you build. We also saw several mentions of resume and project deep-dives, plus core CS basics like OS, DB, mutexes, locks, and multithreading. The non-obvious filter here is whether your explanations stay grounded in real implementation choices. Candidates who only gave surface-level project summaries or rushed through assumptions seemed to struggle more than those who could defend design decisions clearly.
Synthesized from 6 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Meesho process.
I went through a pretty standard Meesho process for a software engineer role, and the part that stood out most was how much they leaned on design rather than pure DSA. I first had an online assessment with three questions, two worth 50 points and one worth 100, and after clearing that I was moved into an LLD round that was run in a group-discussion style format. That round was centered on designing a Meesho app flow for price and sales updates with discounts, so it was less about writing code and more about how I structured the system and explained the moving parts. I answered what I could, but I still didn’t get pushed forward after that.
The technical interview itself was very product-oriented. In the machine coding round, they asked me to build a reviews system for a food delivery app covering restaurant, food, and delivery reviews. The round was on HackerRank, though they said I could use my own IDE. The first 15 to 20 minutes were just Q&A, and I’d definitely recommend using that time to clarify every assumption because they expect you to be vocal. After that, I had roughly an hour to an hour and fifteen minutes to code, and the remaining time was used to run test cases and discuss follow-up questions. The second round was HLD, where I was asked to design a payment system for Meesho. I also heard of a version of the process that included an HR screen and Android-focused technical rounds with Kotlin, OOP, MVVM/MVP, lifecycle scenarios, and project discussion, but my own experience was much more centered on machine coding, LLD, and HLD. Overall, the interviews were smooth and the interviewers were professional, but the bar was clearly high on system design and practical implementation. I didn’t receive an offer, and my main takeaway is to prepare for detailed product-style design prompts and to communicate assumptions very clearly during the coding round.
Prep tip from this candidate
Practice building a reviews system and a payment system end-to-end, because those exact product-style prompts came up in machine coding and HLD. Also be ready for an LLD-style discussion around pricing/discount updates and to spend the first 15–20 minutes of machine coding clarifying assumptions out loud.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Meesho
Write a query to display the top three users by downloads each day
| Question | |
|---|---|
| Scrambled Tickets | |
| Identifying User Sessions | |
| Target Indices | |
| Ride-Sharing App Schema | |
| Upsell Carousel | |
| Shortest Path Algorithms | |
| Duplicate Product Names | |
| Parking Application System Design | |
| 2nd Highest Salary | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Random SQL Sample | |
| Bagging vs Boosting | |
| Raining in Seattle | |
| Prime to N | |
| Delivery Estimate Model | |
| Upsell Transactions | |
| Monthly Customer Report | |
| Rectangle Overlap | |
| Find the First Non-Repeating Character in a String | |
| P-value to a Layman | |
| Hurdles In Data Projects | |
| Average Quantity |
Synthesized from candidate reports. Individual experiences may vary.
Candidates typically start with an OA containing 3 questions, often a mix of DSA and problem-solving with medium to hard difficulty. Several experiences mention needing to solve at least 2 questions, and the assessment is used as the first filter before technical interviews.
This round focuses on core algorithms and data structures, with questions such as priority queue, graphs, dynamic programming, topological sort, BFS, and Bellman-Ford. In some cases, the interviewer expects pseudocode rather than full implementation, and the emphasis is on clear reasoning and approach.
Candidates are asked to build a practical system live, such as a polling system, parking system, grocery store, payment system, car ride system, or a reviews module. The round often includes an initial discussion to clarify assumptions, followed by coding on HackerRank or a similar platform, with strong emphasis on design structure, implementation quality, and communication.
This round tests product-style design thinking through prompts like designing an ordering system with coupons, a food ordering system, or a Meesho app flow for price and sales updates. Interviewers look for how candidates structure components, handle scaling, and explain tradeoffs rather than just producing a diagram.
The final round is usually with the hiring manager and is more conversational, covering resume deep-dives, past projects, contributions, challenges, and behavioral questions. Some candidates also faced basic CS fundamentals here, including OS, databases, mutexes, locks, and multithreading, along with discussion of system design and scaling.