Meesho Software Engineer Interview Guide

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.