Meesho

Meesho runs a structured, mostly virtual process that moves quickly once a hiring manager is engaged. The exact stages depend on the function, but most candidates see the steps below.

1. Application and resume screen

Apply on the Meesho careers page, through a job portal such as Jobaaj, via referral or through campus placements. Recruiters and hiring managers screen resumes for relevant skills, so quantify the impact of your projects and internships.

2. Recruiter conversation

A short call to confirm your background, current role, compensation expectations, notice period and interest in the role. For campus candidates this step is often replaced by a pre-placement talk.

3. Online assessment or take-home task

Engineering candidates usually complete a timed coding test on a standard platform with two or three data structures and algorithms problems. Product, analytics and business roles may get a case-style take-home assignment or an SQL and problem-solving test instead.

4. Technical or functional interviews

Two to three virtual interviews of 45 to 60 minutes each with engineers, product managers or business leads. Engineers face live coding, low-level design and, for experienced hires, system design. Product and business candidates work through product-sense, metrics and execution cases.

5. Hiring manager interview

The manager you would report to discusses your past work in depth, how you make decisions with incomplete data and how you would approach problems on their team.

6. Culture and values round

A senior leader or an interviewer from outside the team assesses ownership, frugality, speed and collaboration through behavioural questions. This round can be a deciding factor even for strong technical candidates.

7. Offer and onboarding

Offers are usually made within a week of the final round. Compensation includes fixed pay and, for many roles, stock units with a multi-year vesting schedule.

The rounds below describe the software engineering loop, with notes on how product, analytics and business roles differ.

Round 1: Online coding assessment

Roughly 60 to 90 minutes with two or three problems of easy to medium difficulty on a standard coding platform. Automated grading rewards correct, efficient solutions that handle edge cases.

• Arrays, strings and hashing problems
• Two-pointer and sliding-window techniques
• Basic tree or graph traversal
• Product and analytics roles: SQL joins, aggregations and a short case

Round 2: Data structures and algorithms interview

A 45 to 60 minute live coding session with an engineer. You are expected to talk through your approach, write clean code in a shared editor and analyse complexity before optimising.

• Medium-level problems on heaps, graphs or dynamic programming
• Follow-up constraints that change the optimal approach
• Testing your solution against tricky inputs

Round 3: Low-level or system design

Freshers get a machine-coding or low-level design problem; experienced engineers get a 60 minute system design discussion about scale, storage and trade-offs.

• Design a cart or order service with clean class structure
• Design a notification or search system for millions of users
• Consistency, caching and database choices

Round 4: Hiring manager and product sense

A 45 minute conversation about your projects, how you prioritise, and how you would improve a Meesho feature. Product managers face full product-sense and metrics cases here.

• Walk through a project you owned end to end
• How would you reduce return rates for low-ticket orders
• Which metrics would you track for a new seller feature

Round 5: Culture and values

A 30 to 45 minute behavioural interview with a senior leader on ownership, frugality and speed.

• A time you shipped something with very limited resources
• A disagreement with a teammate and how it was resolved
• Why Meesho and what you know about its users