MediBuddy | SDE 2 | Interview Experience

medibuddy logo
medibuddy
SDE 22.2 yearsOffer
December 10, 202213 reads

Summary

I interviewed for the SDE 2 role at MediBuddy and successfully received an offer after three technical rounds covering coding, system design, and project discussions.

Full Experience

I recently interviewed for an SDE 2 position at MediBuddy. The entire process consisted of three rounds, culminating in an offer.

My first technical round, lasting 45 minutes, began with a discussion about my projects. Following that, I was asked to solve two coding questions:

The second technical round, an hour long, also started with project discussions. This round focused heavily on design, specifically asking me to design a Rate Limiter (Low-Level Design) and a notification service system.

Finally, I had the Hiring Manager round, which was also an hour. This round primarily revolved around discussing my projects again. I was given a graph-based question, for which I presented a recursive DFS solution. We also had a high-level design discussion around a notification system.

I was ultimately selected for the role.

Interview Questions (4)

Q1
Remove All Adjacent Duplicates In String
Data Structures & AlgorithmsEasy

Given a string S of lowercase English letters, a duplicate removal operation consists of choosing two adjacent and identical letters, and removing them. We repeatedly make duplicate removals on S until we no longer can. Return the final string after all such duplicate removals have been made. It is guaranteed that the answer is unique.

Q2
Top K Files by Size
Data Structures & AlgorithmsMedium

Given access to a file system, design and implement a mechanism to return the top K files based on their size.

Q3
Design a Rate Limiter (LLD)
System DesignHard

Design a low-level rate limiter system. Consider different algorithms like Token Bucket or Leaky Bucket, and discuss aspects such as concurrency, data structures, and how to handle various client requests.

Q4
Design a Notification Service System
System DesignHard

Design a distributed notification service system. Consider aspects such as different notification channels (email, SMS, push), reliability, scalability, message queues, and user preferences.

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!