meesho logo
Meesho· SDE III

Meesho SDE3 interview experience

Posted
20 Jul 2025
502 reads

Summary

I interviewed for an SDE3 role at Meesho, which involved a machine coding round where I designed Splitwise and a High-Level Design round for an insurance aggregator system with inventory management. I was ultimately rejected after the second round.

How it went

Round 1 -

It was a machine coding round. Was asked to design and code splitwise. Evaluation - Interviewer did not ask much on the working of the code but more on Java internals.

Java questions asked - Internal working on Streams. Streams vs Parallel streams Working of GCs. Different types of GC what actually happens when we implement an interface Internal working on concurrent hashmap.

I could not give absolutely correct answers, but it was a good discussion, which made me think deeper.

Round 2 -

Design an insurance aggregator system (Policybazaar), with a catch that we will need to manage the inventory of the insurance as well, can not have an unlimited number of insurances and had other functional requirements such that the insurance company can take some time to approve and provide insurance. Discussions went around failures at making payments.

This was an HLD round.

Verdict - Rejected in Round 2

Questions asked (6)

  1. 01

    Design and Code Splitwise

    Data Structures & Algorithms

    Design and code the Splitwise application.

  2. 02

    Java Internals: Streams vs Parallel Streams

    Other

    Discussion on the internal working of Java Streams, including a comparison between Streams and Parallel Streams.

  3. 03

    Java Internals: Garbage Collection

    Other

    Discussion on the working of Garbage Collectors and different types of GC in Java.

  4. 04

    Java Internals: Interface Implementation

    Other

    What actually happens when we implement an interface in Java.

  5. 05

    Java Internals: Concurrent HashMap

    Other

    Discussion on the internal working of Concurrent HashMap in Java.

  6. 06

    Design an Insurance Aggregator System with Inventory Management

    System Design

    Design an insurance aggregator system (like Policybazaar). The system must manage insurance inventory, as the number of available insurances is not unlimited. Additional functional requirements included the ability for insurance companies to take time to approve and provide insurance, and discussions covered failures related to making payments.

Know someone preparing? Send it to them:WhatsAppLinkedInX

Interviewed at Meesho recently?

Write up your rounds while you still remember the questions. It helps the next person more than you would think.

Share your experience
Discussion 0

Questions for the author, or how your own interview compared.

Join the discussion

Sign in with Google to comment or ask the author a question.

No comments yet

Be the first to share your thoughts and start the discussion!