Interview Experience with Meesho - Disheartening

Anonymous User
651
Oct 27, 2025
Oct 27, 2025

I recently went through two rounds of interviews with Meesho. The process had quite a few reschedules. The first screening round happened nearly 1.5 months after the recruiter initially reached out, mainly due to repeated last-minute cancellations from the company’s side sometimes even at a very last moment.

After the screening, I was scheduled for the next round, which also got rescheduled more than twice. When it finally happened, it turned out to be a 2.5-hour-long coding round. I understand such long sessions can be tiring for interviewers as well, but the lack of attentiveness from interviewer was quite disheartening. The question asked was good and involved considerable depth - I used 5+ design patterns, handled edge cases he didn't even think of, also concurrency and kept explaining my thought process throughout the 2 hours. Unfortunately, the interviewer did not seem very engaged; at one point, he was even discussing something with a peer.

In the end, despite explaining my solution clearly, I was rejected. The only issue I noticed was a minor one - my thread was not waking up after waiting for an entry in the queue. I had already mentioned that I knew how to fix it with just a couple of extra minutes, and I was confident about the underlying concepts.

Two days later, I received a rejection with no specific feedback provided.

I mean, in 2 hours long iterview when someone is communicating their thoughts throughout, thinking of every single edge case, using concurrency and you are judging them on single testcase(I strongly believe so)!!

Comments (5)