What Is the Meesho Interview Process Like? (Round by Round)

Candidates report four to five rounds at Meesho. The process starts with a timed online coding assessment, and one or two technical interviews follow it. A machine coding round comes next for most software engineering roles, and an HR or hiring manager conversation is the final step.

Reports describe the full off-campus process as about two to four weeks. On-campus loops are much faster, because the rounds there are often scheduled a few hours apart.

Quick Overview

Stage 1: The Online Coding Assessment

Most reports begin with a timed online test, and several accounts name HackerEarth as the platform. The content varies by hiring drive. Some candidates report three coding problems, usually two at medium difficulty and one harder problem.

Other candidates report coding problems together with multiple choice questions on operating systems, networks, and core programming topics. Reported durations range from about 90 minutes to about 165 minutes. If this stage is new to you, read what an online technical assessment is.

Stage 2: Technical Interviews

Expect one or two live interviews on data structures and algorithms, and prepare binary search, dynamic programming, graphs, and segment trees, because reports name all four. One candidate reports a single question on bipartite graphs in a short interview of about 30 minutes. Another candidate reports a 90 minute session on HackerRank CodePair with two problems.

Interviewers also ask about your projects, your SQL queries, and operating system concepts. One reported campus loop asked the candidate to write code on paper and then explain it.

Stage 3: The Machine Coding Round

A machine coding round is a timed session where you build a small working program from a written requirement. Reported problems include a car pooling system, a parking lot system, and two features of a ride-sharing application. Some candidates also report low-level design questions modeled on Uber, and reported durations run from about 60 minutes to about two hours.

Graders look at whether the program runs, how the classes are organized, and whether a new requirement can be added without a rewrite. The full round is covered in the Meesho system design interview.

Stage 4: The High Level Design Round

Experienced candidates report a separate design round, which is a discussion rather than a coding exercise. The reported themes follow Meesho's own systems, such as catalog and search, order management, and payment flows. Junior candidates rarely report this round, so treat it as a senior stage.

Stage 5: HR or Hiring Manager Round

The closing round mixes background questions with values questions. Candidates report questions about projects, internships, and core computer science topics here as well, so the HR round is not always only behavioral. Prepare your motivation answer with how to answer why Meesho.

How the Campus Path Differs

Campus loops cover the same content in less time. One reported on-campus loop ran a coding test, a paper coding interview, a design problem, and an HR round in quick succession, with gaps of a few hours between some of the rounds. Campus rounds also test core computer science subjects more heavily than off-campus loops do.

Timeline and Decision

Reported waits vary by hiring drive. One candidate waited about one week between the application and the coding test invitation, then about three days between the test and the first interview. Off-campus reports often describe two to four weeks from the first contact to the decision.

Several candidates also report long silence after the final round. The stage-by-stage detail is in how long it takes to hear back after a Meesho interview.

Questions to Ask Them

Every round ends with time for your questions, so use it to judge the team rather than only to impress the interviewer. Useful questions here include how traffic spikes during sale events are handled, how ownership is divided between teams, and how success is measured for the service you would join. Meesho states a value called Speed Over Perfection, so ask what that value means for code review and testing on the team.

How to Prepare

• Drill algorithm patterns first. The assessment and the technical rounds decide most rejections, and Grokking the Coding Interview covers the patterns behind medium and hard problems.
• Practice building, not sketching. Write a complete car pooling or parking lot program in your own editor, under a timer, before the loop begins.
• Learn class design properly. Grokking the Object Oriented Design Interview teaches the structure that the machine coding round grades.
• Revise core computer science. Operating systems, networks, and SQL appear in the assessment and in the interviews, so review all three.
• Prepare one project in depth. Interviewers ask follow-up questions until they reach the limit of your own involvement in the work.