Meesho SDE-1 Backend Interview Experience (Remote | 3 Round) - Rejected

Last Month, I interviewed with Meesho for an SDE-1 Backend position. The hiring process consisted of three rounds: an Online Assessment, a DSA interview and a Machine Coding (LLD) round.

Overall, I really enjoyed the interview experience. Every interviewer was friendly, gave me enough time to think and was more interested in understanding my thought process than watching me write code as fast as possible. Although I didn't receive an offer in the end, the process helped me understand what Meesho expects from backend engineers.

The interview mainly evaluated three areas:

• Problem-solving and DSA
• Coding ability
• Low-Level Design and writing clean, working code

Based on several recent interview experiences, Meesho's backend interviews frequently combine coding rounds with machine coding or LLD discussions, especially for backend-focused roles.

Round 1 : Online Assessment

The first round was a 60-minute Online Assessment consisting of three coding problems. The questions gradually increased in difficulty. The first problem was relatively straightforward, the second required a good understanding of algorithmic patterns and the final one was considerably more challenging.

Unfortunately, I don't remember the exact problem statements since it's been quite some time since the interview. However, I do remember the overall difficulty and the type of thinking each question required.

Coding Questions

Topics Covered

The assessment mainly focused on:

• Greedy Algorithms
• Sliding Window
• Dynamic Programming

Overall, I found the difficulty level to be somewhere between medium and hard. Good familiarity with common DSA patterns made a big difference during this round.

Round 2 : Technical Interview (DSA)

The second round lasted around 45 minutes and focused entirely on problem-solving.

The interviewer started by sharing a coding problem that was very similar to the classic Rotten Oranges problem.

Since I had solved similar BFS problems before, I was able to identify the approach fairly quickly. I first explained my thought process, discussed why multi-source BFS would work and then moved on to implementation.

I completed the solution in roughly 25 minutes, after which we spent the remaining time discussing its time and space complexity along with a few edge cases.

The interviewer seemed satisfied with both my explanation and implementation and I came out of the interview feeling quite confident.

Round 3 : Machine Coding (LLD)

The final round was the most interesting part of the entire process. Instead of solving another DSA problem, I was asked to design and implement a Cab Booking System.

The interviewer gave me four core functionalities to implement:

• Add a Cab
• Book a Ride
• End a Ride
• Display complete ride information, including driver, passenger and ride details

Unlike a whiteboard design discussion, this was a machine coding round, so writing working code was the primary expectation.

I started by identifying the entities involved, designing the classes and then implementing each feature one by one. Throughout the interview, I kept explaining why I was choosing a particular design instead of simply writing code silently.

I was able to implement most of the required functionality within the allotted time. The core features were in place, but a few edge cases, validations and some cleanup were still pending. With another 10-15 minutes, I believe I could have completed the implementation.

The discussion with the interviewer remained interactive throughout the round. Whenever I made a design choice, they asked follow-up questions about alternative approaches, scalability and maintainability. Although I was able to justify most of my decisions, my implementation wasn't completely finished by the end of the interview.

Overall Experience

Although the final outcome was a rejection, I still consider the entire interview process a valuable learning experience.

The online assessment tested my DSA fundamentals, the technical interview focused on problem-solving under time pressure and the machine coding round evaluated how well I could translate a design into clean, executable code.

One thing that stood out to me was that interviewers weren't looking for overly complicated solutions. They cared more about whether the code was modular, easy to understand and actually worked correctly.

Looking back, I believe I performed reasonably well across all three rounds. However, backend interviews at companies like Meesho are highly competitive and sometimes even a good interview doesn't necessarily result in an offer.

My Preparation Tips

If you're preparing for a Meesho Backend interview, I'd recommend spending time on both DSA and Low-Level Design. For the coding rounds, focus on:

• Sliding Window
• Dynamic Programming
• Graphs
• BFS & DFS
• Greedy Algorithms
• Hash Maps
• Binary Search

For the machine coding round, practice implementing small backend systems from scratch rather than only drawing UML diagrams. The goal is to write clean, working, object-oriented code instead of only discussing the design.

Some good practice problems include:

• Cab Booking System
• Parking Lot
• Library Management System
• Splitwise
• Food Delivery System
• BookMyShow

Can ref Low Level System Design Sheet - Fast-Track to Cracking Tech Interviews.

My Advice

The biggest lesson I learned from this interview is that machine coding is very different from system design discussions.

Having a good design is important, but if the interviewer expects a working implementation, then code quality, correctness and completing the core functionality become equally important.

If you have limited time during the interview:

• Finish the core features first.
• Keep the design simple and modular.
• Explain your thought process continuously.
• Don't spend too much time perfecting one small part while leaving major functionality incomplete.

Even though I wasn't selected, I walked away with a much clearer understanding of what companies expect in backend interviews and that experience alone made the interview worthwhile.

Questions Asked