Meesho hub
Meesho Online Assessment
Overview
Meesho online assessment (OA) is the first hard filter for many fresher and lateral engineering drives. This page covers format, sample Meesho OA questions, an 8-week prep plan, and mistakes that sink strong candidates.
Patterns are from student reports for 2025-2026. Confirm your invite.
Meesho hiring flow after the OA
| Stage | What candidates report | What you must show |
|---|---|---|
| 1. Online assessment | Timed coding OA | Correctness + reasonable complexity |
| 2. Technical interviews | DSA + projects | Explain approach and edge cases |
| 3. Later rounds | HM / HR | Depth + communication |
| 4. HR / offer | Role, location, CTC | Consistency with resume |
Meesho Online Assessment format
| Component | From student reports details |
|---|---|
| Platform | HackerRank / similar |
| Duration | About 90-120 minutes |
| Question mix | 2-3 coding problems |
| Languages | Java, C++, Python |
| Scoring | Test-case driven |
| Advance rate | Selective for campus/product roles |
What makes Meesho OA feel distinct
- Ecommerce/marketplace DSA
- Ranking, catalog, and logistics-flavored prompts in practice sets
- Startup-product speed: finish problems, then polish
- Culture/ownership rounds after OA
Question types
Core
- Arrays, hashing, heaps
- Graphs/BFS
- Greedy scheduling
- String processing
Secondary
- Ecommerce metrics intuition in interviews
- SQL for data-leaning roles
Usually not in OA
- Long aptitude-only NQT clones for SWE OA
- Full ML research papers
Sample Meesho Online Assessment questions
Question 1: top-k products by orders
Question 2: coupon interval merge
Question 3: warehouse grid reachability
Question 4: reseller catalog strings
Question 5: max orders in window
Question 6: group anagram skus
8-Week prep plan
| Weeks | Focus | Exit criteria |
|---|---|---|
| 1-2 | Arrays, hashing, two pointers | 40+ clean easy/medium |
| 3-4 | Trees/graphs/heaps as relevant | Implement BFS/DFS cold |
| 5-6 | Domain-flavored drills for Meesho | Timed section comfort |
| 7 | Full mocks at OA duration | Finish required problems with tests |
| 8 | Weak-topic repair | Re-solve misses in 48 hours |
Daily loop
- One timed medium problem
- Write complexity + 3 edge cases before coding
- Log misses by pattern
- Weekly full mock
Common mistakes
- Overbuilding solutions for simple constraints
- Missing edge cases on ranking/tie-break
- No time for problem 2
- Resume projects you cannot run through
- Weak communication in HM round
Day-of checklist
- Skim all problems for 3-4 minutes and order by familiarity
- Submit a correct simpler solution before over-optimizing if time is tight
- Invent edge cases the samples omit
- Do not leave a problem fully blank if a partial tested approach can score
- After the test, write down every problem from memory for interview prep
Interview transition plan (48 hours after OA)
- Re-solve your OA problems cleanly
- Prepare STAR stories (ownership, conflict, failure, impact)
- Revise OOPs, DBMS, OS one-pagers
- Rehearse a 2-minute project narration