Meesho Open Campus Recruitment Experience (Off-campus)

meesho logo
meesho
April 17, 20256 reads

Summary

I applied for Meesho's open campus recruitment through HackerEarth and was shortlisted for the Online Assessment. I proceeded through multiple virtual interview rounds covering Data Structures & Algorithms, Low-Level Design, and Hiring Manager questions, but ultimately got rejected.

Full Experience

Applied on HackerEarth for the Open campus recruitment process and got shortlisted (based on resume ig) for the OA.

OA (2 hour and 45 min)

Got 3 medium (upper level) to hard questions. Was able to solve 1 question completely and 2 partially. (Can't share the exact questions)

  1. Find a subsequence with length k and min score.
  2. Tree based multiple BFS question.
  3. Difficult graph based question.

Selected for the virtual interview process. Each round was an elimination round (i was told this in the official mail) and was hosted on google meet.

During the start of each round the interviewer introduced himself and was asked to do the same. So am not repeating this detail in each round individually.

Round 1 (DSA based - 30 min)

Only one question was asked and was told the write pseudocode for it in the google doc provided.

  1. Multi source BFS problem.

Got call for the 2nd round.

Round 2 (LLD based - 60 min)

Hacker rank's codepair platform was used, which provides a way to do pair programming (multiple people running or writing code on the same file).

Was told that i would be judged on the completeness of the code and then based on the quality/cleanliness and use of OOPs and design patterns in my code.

  1. Was asked to implement 6 functions for a shopping manager service.

Cleared all the doubts about requirements in the first 15 mins and then got to implementation. Was under time pressure so couldn't give too much time to design since the first and foremost requirement was a working code, still did my best to make it as lossely coupled as possible, while handling all the edge cases which came to my mind as well as choosing the most efficient ways to implement different functions (time complexity wise). Took around 60-65 mins

Than discussed about the code with the interviewer and ran it.

Went above the time limit by a bit, but couldn't have implemented it faster.

Got call for the 3rd round.

Round 3 (Hiring Manager based - 30 min)

  1. Got asked about my project and role in internship.
  2. Was asked to give a demo of one of the projects on my resume.
  3. Got asked some questions on OS fundamentals about mutex, semaphore, deadlock, etc.
  4. Was asked about my inclination towards a role, like backend or frontend, etc.
  5. A scaling question related to network.

At the end of the previous round as well as this round, I asked some questions about the work they do and was impressed by the quality and scale of work available at meesho. It definetely changed the image about meesho and other young startups i had in my mind and motivates me to want to work in them.

Edit : Got rejected

Interview Questions (7)

Q1
Find Subsequence with Length K and Min Score
Data Structures & AlgorithmsHard

Find a subsequence with length k and minimum score.

Q2
Implement Shopping Manager Service
System Design

Implement 6 functions for a shopping manager service. The implementation should focus on completeness, quality/cleanliness, and use of OOPs and design patterns.

Q3
Discuss Internship Project and Role
Behavioral

Discuss my project and role during my internship.

Q4
Project Demo
Behavioral

Give a demonstration of one of the projects listed on my resume.

Q5
OS Fundamentals: Mutex, Semaphore, Deadlock
Other

Questions on Operating System fundamentals, specifically covering concepts like mutex, semaphore, and deadlock.

Q6
Role Inclination (Backend/Frontend)
Behavioral

Questions about my inclination towards a specific role, such as backend or frontend.

Q7
Network Scaling Question
System Design

A question related to network scaling.

Preparation Tips

Advice

If you can't think of the optimal solution, keep thinking, atlast if you dont have any option implement the brute force and don't lose hope in the middle of the test, you don't know how others will perform.

Advice

  1. I took too much time explaining my role in internship, since i did not prepare for questions on it thorougly and was recollecting from my memory about something which happened 2 years back, so my explaination was a bit blurry. So thoroughly go through your projects and internship work, and focus on explaining why you did what you did, instead of explaining tech stack specefic things, like structure or call order etc.
  2. Also took a bit more time giving the demo of my project, due to starting everything locally, etc. So get your demo ready before the interview itself.
Discussion (0)

Share your thoughts and ask questions

Join the Discussion

Sign in with Google to share your thoughts and ask questions

No comments yet

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