Meesho is a Bengaluru e-commerce marketplace built around low prices and small sellers across India. Candidates consistently report an online assessment, a machine coding round with a strong object-oriented bias, and DSA and design rounds after it. This page covers what Meesho builds and who it hires, the process candidates commonly report, the technical depth the teams care about, representative problem types, what interviewers score, and a three-week prep plan.
What Meesho builds and who it hires
Meesho's engineers build the marketplace, seller tools, search and ranking, ads, logistics and an in-house ML platform. Its engineering blog describes rewriting Java Spring Boot services in Go and replacing Cassandra with ScyllaDB to cut infrastructure costs, and a Meesho job posting describes peak traffic of about 14 million requests per second across more than 1,000 microservices.
- SDE-1 and SDE-2: back-end engineers in Java or Go.
- SDE-3 and above: design-heavy loops.
- Front-end and mobile engineers: the shopper and seller apps.
- Data science and ML engineers: ranking, recommendations and the feature store.
What the process tends to look like
| Stage | What happens | How to prepare |
|---|---|---|
| Recruiter call or referral | Role, level (SDE-1, SDE-2 or SDE-3), team and timeline | Know the product, the team and your own résumé in detail |
| Online assessment | Reports describe about three DSA problems in roughly 90 to 105 minutes, rated medium to hard | Timed mixed sets; sometimes debugging questions too |
| Machine coding | About 90 minutes to implement a set of functions from scratch with OOP | Clarify assumptions early, then code core features with validations |
| DSA round | Problems with optimization follow-ups | State complexity and improve step by step |
| Design (SDE-2 and above) and hiring manager | HLD or LLD discussion, then projects and culture | One marketplace design and two ownership stories |
Processes differ by team, level and office and change over time, so treat this as the common shape candidates report and confirm the specifics with your recruiter.
Machine coding and e-commerce design
Machine coding. Candidates describe a problem statement with several functions to implement from scratch using object-oriented design, like an LLD round that must run. SDE-3 reports include building an expense splitter. Expect follow-up questions on the design patterns you used.
Speed and validations. Reports stress that coding speed matters: cover the core functionality and input validations first, then add extras. Spend the first minutes confirming requirements aloud.
Marketplace design. Good design topics are a catalog with millions of seller listings, ranking for price-sensitive shoppers, and cash-on-delivery orders with returns. Meesho's write-ups on its Go rewrite and feature store also make good material for a performance discussion.
Representative problem types
These are the kinds of problems candidates describe, not a leaked question list. Practice the category, not the exact question.
- Implement an expense splitter or an in-memory cart and checkout.
- Design a product catalog with variants for many sellers.
- Design a feed that ranks products for a shopper.
- Implement a coupon engine with stacking rules.
- Design order tracking with returns and refunds.
- Medium-hard array, string and graph problems under time pressure.
- Debug a broken function in a given codebase.
What interviewers score
- Working code: a solution that runs, handles edge cases and is readable by the next engineer.
- Practical judgment: the trade-offs you name and the simplest design that meets the requirement.
- Product sense: understanding who the user is and what failure looks like for them.
- Ownership: examples where you shipped, measured and fixed things yourself.
The behavioral side
Technical rounds decide most outcomes, but every Meesho loop also asks about how you work. Prepare a short story for each of these, with a result and what you learned:
- Something you shipped end to end. Cover the user problem, your decisions, what you measured and what you would change.
- A disagreement with a teammate. Show how you made the decision on evidence and kept the relationship.
- Why this company? Connect its product and engineering problems to the work you want to do next.
Structures and sample answers for the common questions are in our software engineer behavioral answers guide.
A three-week prep plan
- Week 1: practical coding: build small features against an API, parse and transform data, and write tests, in the language you will interview in.
- Week 2: system design for the company's domain, plus two behavioral stories about shipping and fixing something under pressure.
- Week 3: timed mixed problems, a mock interview every other day, and research into the product and its engineering blog.
For practice lists, use LeetCode company-tagged questions, the Striver A2Z sheet or the Love Babbar 450 sheet, and if your drive starts with a test, read our guide to new-grad online assessments.
Where CoPilot Interview fits
Most of a Meesho loop is spoken: you explain an approach, defend a trade-off and talk through your past work. CoPilot Interview is an AI interview assistant whose free AI mock interview builds technical and behavioral questions from your résumé and the job description, reads them aloud and scores each spoken answer out of ten, so you can rehearse the explanation as well as the code. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. Online assessments and many coding rounds forbid outside help, so practice beforehand and follow your employer's rules on the day.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.
Frequently asked questions
What programming language should I use in a Meesho interview?
Java and Go are the main back-end languages in Meesho's postings; use whichever you write cleanest object-oriented code in.
Does Meesho send an online assessment?
Yes, for most reported drives. Reports disagree on the platform, naming both HackerRank and HackerEarth, so read the invitation; our <a href="/blog/hackerearth-assessment">HackerEarth assessment guide</a> and <a href="/blog/hackerrank-assessment-guide">HackerRank assessment guide</a> cover both formats.
Which platform does Meesho use for its online assessment?
Candidate reports name both HackerRank and HackerEarth, and the platform can change between drives. Reports describe about three timed DSA problems of medium to hard difficulty, sometimes with debugging questions. Your invitation names the platform, so practice in that editor beforehand.
How should I prepare for Meesho coding questions?
Practice practical problems under time limits, build small features against an API in your interview language, and prepare one system design in Meesho's domain. Explain every solution out loud, because follow-up questions about trade-offs matter as much as the first answer.
Can I use AI tools in a Meesho interview?
Only if the instructions you receive say so. Online assessments and live coding rounds generally forbid outside help, and some companies now state their AI policy in the invitation. Use AI to practice beforehand, and follow your employer's rules.
Practice this interview before the real one
The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.
Start a mock interview