Coding questions
How to Prepare for Meesho
Meesho engineering interviews are product-company serious. DSA OA matters; reseller/marketplace intuition is a bonus, not a substitute.
What Meesho actually tests
First round: Meesho OA + interviews
Time split that matches how candidates report outcomes (not a marketing pie chart):
- DSA 50%
- Domain scenarios 20%
- CS/projects 15%
- Behavioral 15%
Patterns are from student reports and vary by role and drive. Trust your college placement email over blog folklore.
Hiring flow you should prep for
| Stage | Time | What they check |
|---|---|---|
| OA | timed | DSA |
| Tech + HR | multiple | Coding + fit |
Time allocation
- Master DSA fundamentals (arrays, trees, graphs, dynamic programming) - 40% time
- Practice 100+ coding problems on LeetCode/HackerRank focusing on medium difficulty - 30% time
- Learn system design basics (e-commerce systems, recommendation engines, scalability) - 20% time
- Study Meesho company values and prepare behavioral stories - 10% time
Daily loop (75-120 minutes)
- One timed block that matches Meesho’s first round (coding OA)
- Log misses: topic + why you failed (speed, concept, carelessness)
- Re-solve yesterday’s misses cold
- Twice a week: 10 minutes of resume/project narration out loud
8-Week ecommerce / marketplace plan
| Week | Focus | Exit criteria |
|---|---|---|
| 1-2 | Core DSA | Baseline mock logged |
| 3-4 | Graphs, heaps, hashing | Delivery/ranking style problems attempted |
| 5-6 | System design lite + projects | Catalog/order flow explained |
| 7-8 | Mocks + behavioral | Weak topics closed |
Round-by-round strategy
Online Assessment
- Order problems by confidence after a 3-4 minute skim
- Passing test cases beats a brilliant half-solution
- Invent edge cases before submit; watch timeboxes
Technical interviews
- Restate → brute force → optimize → code → test
- If domain comes up, reason about inventory/latency - do not recite blogs.
- Tie CS answers to a project when it strengthens the point
HR / managerial
- Why Meesho, why this team/role, location flexibility
- STAR with a metric; pick 2-3 real company values and prepare proof
Meesho-specific drills
- Medium-hard DSA
- Catalog/pricing/scale scenarios if asked
Topic checklist
- Medium DSA
- Debugging under time if OA includes it
- Projects with metrics
- Inventory, ranking, routing scenarios
- Caching / read-heavy API intuition
- Full-length mock every other day
- Light revision only - no new rabbit holes
- Sleep, ID proofs, machine/network checklist for test day
Final stretch
30 days out: weekly full OA-style mocks; close weak DSA patterns; draft STAR stories.
7 days out: alternate mock / review days; re-solve misses cold; no new patterns.
Day before: skim notes, check machine/network/ID logistics, sleep.
Common mistakes for Meesho aspirants
- Underestimating coding difficulty for a ‘startup’ brand - fix this first
- Preparing only interviews while failing Meesho’s first round
- Collecting notes without timed mocks
- Listing five frameworks on the resume and defending none
- Changing language/stack one week before the drive
- Only ecommerce talk, weak code
Practice on this site
- Meesho aptitude / mock quiz
- Meesho coding questions
- Meesho online assessment
- Meesho interview experience
- Meesho previous year papers
- Meesho 2026 guide
- Meesho hub
- PDF: Meesho Placement Papers PDF (2026)

