HR interview questions
Common Meesho HR questions, sample answer frames, and STAR tips.
Meesho Interview Experiences
How Meesho fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat this as a prep map, not a script.
Meesho placement process includes: 1. Application (on-campus via college placement cell, off-campus via Meesho Careers portal, or through referrals), 2. Online Assessment (OA) - 2-3 coding problems (60-90 minutes), 3. Technical Interviews (2 rounds) - DSA, system design, projects (45-60 minutes each), 4. Managerial Round - Technical depth and behavioral fit (45 minutes), 5. HR Interview - Behavioral and offer (20-30 minutes). Total duration: 2-3 weeks from application to offer letter.
Eligibility (from student reports): 7.0+ CGPA in 10th, 12th, and graduation.
Fresher package ballpark (from student reports): SDE-1: ₹25-35 LPA. Confirm on your offer letter.
Round-wise process
Section titled “Round-wise process”| Round | Duration | What they test |
|---|---|---|
| Online Assessment | 90 min | 2-3 coding problems |
| Technical Round 1 | 45-60 min | DSA + project discussion |
| Technical Round 2 | 45-60 min | System design (orders / logistics) |
| HR | 20-30 min | Behavioural + culture fit |
Real interview experiences
Section titled “Real interview experiences”These are rewritten from public student write-ups. Two things recur across almost every Meesho account, so plan around them: the coding round is long and genuinely hard (not a 2-easy-questions screen), and the round most people underestimate is a machine-coding / low-level-design round, not a distributed-systems whiteboard.
Experience 1: SDE-1, on-campus (selected)
Section titled “Experience 1: SDE-1, on-campus (selected)”Source: Meesho Interview Experience for SDE-1, On-Campus (Virtual) - GeeksforGeeks
Round 1 - coding + MCQs
- 3 coding problems plus ~20 MCQs on OS, networking, and programming.
- Reported problems: common elements across arrays, minimum changes to make strings anagrams, and weighted job scheduling (a DP problem, not a warm-up).
- 15 candidates cleared this stage.
Round 2 - technical (~1.5 hours)
- Activity selection via greedy - solved in about 15 minutes.
- A harder “water the plants” simulation problem that took 30-40 minutes, with the interviewer giving hints along the way. Being coachable mattered as much as being fast.
- Then general OS and DBMS questions. 9 candidates moved on.
Round 3 - technical 2 (~1 hour)
- Design a database schema for one of their own projects and write SQL queries against it.
- One coding question solved with DFS.
- Rapid-fire fundamentals: ARP, DNS, OSI layers, semaphores vs mutexes, paging and virtual memory, threading, SQL vs NoSQL, normalisation, ACID. 4 candidates reached HR.
Round 4 - HR
- The candidate described it as close to a formality at that point.
Result: Selected.
Experience 2: SDE-1, open campus 2025 (rejected after the final round)
Section titled “Experience 2: SDE-1, open campus 2025 (rejected after the final round)”Source: Meesho SDE-1 Open Campus Interview Experience 2025 - GeeksforGeeks
- Screening: resume evaluation, with the coding round hosted on HackerEarth.
- Coding round: 165 minutes, three questions - two medium and one hard. Other 2025 accounts report a similar shape (roughly 105-165 min, 3 problems, topics like binary search, DP, and segment trees), plus in some drives a short MCQ/aptitude stage on Meesho’s NextLevel app before it.
- Technical interview (~30 min): a medium DSA problem on bipartite graphs.
- Machine coding round (60 min): implement a working design - this candidate got a car-pooling system; another 2025 account reports an inventory management system in 90 minutes. Expect to write real, runnable, class-structured code under time pressure.
- HR round: projects, internships, and a spread of OS, computer networks, and SQL questions - not a formality in this drive.
Result: Not selected, despite clearing every prior round. Worth knowing: reaching HR at Meesho is not the same as an offer.
What these accounts have in common
- The coding round is the real filter and it is long. Practise 3-problem, 2-hour-plus sets rather than single 45-minute problems.
- Core CS is asked in depth, not as small talk - OS, networking, and DBMS come up in every write-up.
- The LLD / machine-coding round rewards clean class design and working code over clever algorithms.
Questions that come up often
Section titled “Questions that come up often”Coding / technical
Section titled “Coding / technical”- Top-K frequent elements. Usually expects heap / bucket sort
- Shortest path in a grid. Usually expects BFS
- Merge overlapping delivery slots. Usually expects interval merge
- Discussion on catalogue search and reseller workflows, bottlenecks, failure modes, simple APIs
- Detailed project discussion, architecture, hardest bug, what you would change
HR / behavioural
Section titled “HR / behavioural”- Why this product?
- Working with unclear requirements
- On-call or weekend comfort
- Relocation
Practical tips for Meesho
Section titled “Practical tips for Meesho”- Clear the screening round first. Timed practice beats last-minute topic hopping.
- For domain questions, explain catalogue search in plain language, inputs, outputs, what breaks at scale.
- OOPs and SQL still open a lot of Meesho panels. Do not skip fundamentals.
- HR answers should be concrete. One story with a result beats five slogans.
- If you do not know something, say so and outline how you would find out.
HR interview
Section titled “HR interview”After technical rounds, Meesho usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.