Meesho Software Engineer candidates commonly report a timed DSA assessment, technical problem-solving, and a machine-coding or design exercise, with project and HR discussion in some processes.
$138K
Avg. Base Comp
$168K
Avg. Total Comp
3-4 rounds
Typical Rounds
2-4 weeks
Process Length
Meesho Software Engineer candidates in the supplied accounts commonly describe an early coding assessment followed by technical interviews, although one candidate had only a 45-minute progressive coding session. The recurring practical challenge is solving problems accurately under time pressure while explaining the reasoning behind the code. Assessments included coding, debugging, and, in one case, multiple-choice questions. Reported topics include graphs, dynamic programming, arrays, strings, trees, sorting, searching, and linked lists.
For DSA preparation, practice both isolated problems and longer mixed assessments. Candidate-reported questions included graph coloring, longest increasing subsequence, longest common subsequence, finding two BST nodes that sum to a target, finding the kth node from the end of a linked list, adding forward-order linked-list numbers with a stack, and Asteroid Collision. Be ready to explain the state and transitions in a dynamic-programming solution, handle edge cases, and discuss time complexity.
Some processes shifted from algorithms into design or machine coding. Supplied examples include implementing a messaging app, discussing a scalable system, and completing a short pen-and-paper design exercise. One preparation-stage account described uncertainty about whether a two-hour practical round would emphasize low-level design or DSA, so it should not be treated as a confirmed universal format.
Project, manager, or HR conversations may cover technical choices, hypothetical scenarios, education, work experience, strengths, improvement areas, and difficult situations. Core Java also appeared in one successful process, including Singleton, constructors, OOP, and differences among String, StringBuilder, and StringBuffer.
Synthesized from 24 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Meesho process.
The interview process at Meesho was structured to assess technical depth across multiple dimensions—DSA, system design, and database fundamentals. I went through several rounds, each designed to test different competencies.
The first round was an online assessment with three DSA questions of varying difficulty. Two of the problems touched on dynamic programming and greedy approaches, which required careful optimization. I also encountered SQL queries that tested understanding of window functions and query optimization. The questions weren't trivial—they demanded strong problem-solving fundamentals and the ability to think through trade-offs under time pressure.
Following the online assessment, there was a written coding interview conducted in small batches. This round felt more collaborative, with the interviewer interested in my approach and reasoning rather than just the final solution. The technical bar remained consistent with the first round—solid DSA fundamentals were essential.
The final round was comprehensive. It covered DSA problems, object-oriented design principles, and low-level system design. There was also a case study component that asked me to design a solution for a real-world scenario. This round felt less about gotcha questions and more about evaluating whether I could think architecturally and communicate my reasoning clearly.
Overall, the interviewers were professional and genuinely engaged. The questions were relevant to what engineers actually build, and the progression from pure coding to design made sense. While I didn't receive an offer, the experience felt balanced and fair. The process gave me a clear sense of what the team values—strong fundamentals, clear communication, and the ability to scale thinking from implementation details to system-level concerns.
Prep tip from this candidate
Focus heavily on DP and greedy algorithm problems, and ensure you're comfortable with SQL query optimization and window functions—these appeared consistently across rounds. Be ready to move between coding, design, and case study discussions in a single final round, so practice articulating architectural trade-offs, not just implementing solutions.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Meesho
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Top Three Salaries | |
| Top 3 Users | |
| Scrambled Tickets | |
| Size of Joins | |
| Average Order Value | |
| Identifying User Sessions | |
| Precision and Recall | |
| Hurdles In Data Projects | |
| Cumulative Sales By Product | |
| Target Indices | |
| Equal Binary Subarrays | |
| Sequentially Fill in Integers | |
| Filling Supermarket Bag | |
| Ride-Sharing App Schema | |
| NxN Grid Traversal | |
| Upsell Carousel | |
| Hidden Culprit | |
| Shortest Path Algorithms | |
| Duplicate Product Names | |
| Median Household Income | |
| Parking Application System Design | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report HackerEarth- or HackerRank-style assessments ranging from three coding problems to roughly four or five coding/debugging questions in 105 minutes. Reported coverage includes graphs, DP, arrays, strings, trees, and core CS MCQs; difficulty and scoring thresholds vary.
Candidates report DSA interviews using live coding, pseudocode, Google Docs, or paper. Examples include linked lists, graph traversal, LCS, monotonic stacks, priority queues, and range queries. Interviewers may ask for a dry run, edge cases, and time or space complexity.
Many candidates report a practical design round where working code and, in some cases, passing supplied tests matter. Reported first-hand prompts include a vending machine, carpooling, coupon checkout, e-commerce features, parking lot, messaging app, and an in-memory TTL cache.
Some candidates report a final conversation covering projects, resume claims, core CS concepts, problem-solving scenarios, teamwork, and career goals. This stage may be combined with technical discussion rather than being purely behavioral.
