The hiring process
| Round | Format | What's tested |
|---|---|---|
| Online Assessment | ~90–120 min | DSA problem-solving |
| Coding / DSA Interview | ~60 min | Live algorithmic depth |
| Machine Coding / LLD | ~90–120 min | Building working, extensible code |
| HLD + Hiring Manager / HR | ~45–60 min | System design and fit |
Process and cutoffs vary by drive/team and change over time — confirm on the official careers page.
Round-by-round: exactly what's asked & how to prepare
Online Assessment
~90–120 minA timed HackerRank-style test, often two-to-three problems weighted by difficulty, sometimes allowing your own IDE. Problems skew medium-to-hard and reward strong fundamentals in classic patterns. Passing hidden test cases and time management decide the outcome.
- Greedy and dynamic programming problems
- Tree and graph traversal
- Hashing and frequency-based problems
- Sorting plus two-pointer or binary search
- Careful edge-case handling under time
- Grind LeetCode mediums across DP, trees, and greedy
- Practice on HackerRank to match the platform feel
- Time yourself on 2–3 problem sets end to end
- Use NeetCode 150 for pattern coverage
- Chasing the hardest problem and leaving easy points unclaimed
- Not testing against edge cases before submitting
- Multiple problems fully passing within the window
- Correct pattern choice with clean complexity
Coding / DSA Interview
~60 minA live round with 1–2 DSA problems and follow-ups on complexity and alternatives. Interviewers watch how you reason, handle edge cases, and optimize. Some candidates also get CS-fundamentals or SQL and schema questions mixed in.
- Optimizing brute force to optimal live
- Graph, tree, and interval problems
- SQL queries and schema design questions
- OS and networking basics (DNS, OSI) as follow-ups
- Complexity trade-off discussion
- Practice narrating solutions while coding live
- Review SQL joins and basic schema design
- Refresh OS and networking fundamentals
- Do mock interviews with a timer and a peer
- Silent coding with no reasoning shared
- Ignoring interviewer hints toward the optimal path
- Optimal solution with clear complexity analysis
- Comfort with adjacent CS fundamentals
Machine Coding / LLD
~90–120 minA hands-on task to implement a small working system with clean, modular, object-oriented design, sometimes run in a discussion-heavy format. They grade correctness, extensibility, and clarity of abstractions more than raw algorithm speed. You are expected to code a running solution, not pseudocode.
- Designing classes with clear responsibilities (SOLID)
- Modeling an e-commerce feature (cart, orders, inventory)
- Handling concurrency or edge conditions cleanly
- Writing extensible, testable code under time
- Choosing the right data structures and justifying them
- Practice machine-coding katas (parking lot, cart, splitwise)
- Learn SOLID and common design patterns
- Rehearse building a working demo in 90 minutes
- Read free LLD primers on common design patterns
- Over-engineering instead of delivering a working build
- Poor class boundaries that block extensibility
- Clean, running, extensible code on time
- Clear, justified abstractions and structures
HLD + Hiring Manager / HR
~45–60 minA high-level design conversation on a scalable system plus behavioral and project discussion. Expect questions on scaling, data stores, caching, and trade-offs at marketplace scale, then motivation and team-fit questions. Communication and pragmatic choices matter most.
- Designing a scalable e-commerce component end to end
- Databases, caching, and queues at scale
- Consistency, availability, and latency trade-offs
- Project ownership and impact stories
- Why Meesho and how you handle fast-paced work
- Study HLD basics: load balancing, caching, sharding, queues
- Practice designing a marketplace feature aloud
- Prepare impact-focused STAR project stories
- Use free System Design Primer on GitHub
- Jumping to components without clarifying requirements
- Ignoring scale and trade-offs in the design
- Structured design with justified trade-offs
- Clear ownership and motivation for the role
What to master
- Data structures and algorithms
- Dynamic programming and greedy
- Machine coding / low-level design
- Object-oriented design and SOLID
- High-level system design
- SQL and databases
- OS and networking basics
- Behavioral / project impact
Eligibility
Role-based: SDE roles target strong coders across levels; campus hires need solid DSA and CS fundamentals, while lateral hires need design and delivery depth. Specifics vary by team and level.
Meesho salary & compensation (2026)
India e-commerce unicorn; competitive startup pay with ESOPs, below FAANG-India.
| Role / Level | Experience | India — total CTC | US — total comp | What to know |
|---|---|---|---|---|
| SDE 1 | 0–2 yrs | ₹20–32 LPA | — | base + ESOPs (liquidity via buybacks) |
| SDE 2 | 2–4 yrs | ₹32–52 LPA | — | ESOP grant grows |
| SDE 3 / Senior | 4–7 yrs | ₹52–85 LPA | — | equity meaningful pre-IPO |
| Staff / Engineering Manager | 7–11 yrs | ₹85 LPA–1.4 Cr | — | larger ESOP grants |
| Principal / Director | 11+ yrs | ₹1.4–2.2 Cr | — | senior leadership, heavy equity |
How the package is structured
- Comp = base + ESOPs; ESOP value depends on valuation and buyback/IPO liquidity.
- Pays at the higher end of Indian startups but below FAANG-India cash.
- Pre-IPO ESOPs are the upside lever — size and eventual liquidity matter most.
- Growth via fast promotions typical of high-growth startups.
Indicative 2026 market ranges aggregated from public sources (levels.fyi, Glassdoor, AmbitionBox, candidate reports). Compensation varies widely by location, team, level calibration, and negotiation — use these as directional benchmarks, not guarantees.
Your prep plan
- Day 1–3: Grind LeetCode mediums in DP, trees, and greedy
- Day 4–6: Timed HackerRank multi-problem sets
- Day 7–9: Practice machine-coding katas with clean OOP
- Day 10–11: Study HLD fundamentals and design a marketplace feature
- Day 12–13: Refresh SQL, OS, and networking basics
- Day 14: Mock LLD + HLD rounds and prep project stories
Want this plan dated to your interview?
Upload your resume and tell Whis your interview date — get a personalized, day-by-day plan built around your gaps, then run Whis live in the interview.
Get my personalized planFrequently asked questions
How much does machine coding matter?
A great deal. Meesho weights the build/LLD round heavily, so working, extensible, well-structured code is often the deciding factor.
Is the DSA bar high?
Yes, the early screens skew medium-to-hard. Strong fundamentals in DP, greedy, and graphs are important to clear them.
Do they ask system design for all levels?
HLD depth scales with level; senior roles get deeper design rounds, while juniors focus more on DSA and machine coding.