medibuddy logo
Medibuddy· SDE 2

MediBuddy | SDE 2 | Interview Experience

Result
Offer
Experience
2.2 years
Posted
10 Dec 2022
312 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.

How it went

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.

Questions asked (4)

  1. 01

    Remove All Adjacent Duplicates In String

    Data Structures & Algorithms · Easy

    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.

    Open the problem
  2. 02

    Top K Files by Size

    Data Structures & Algorithms · Medium

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

  3. 03

    Design a Rate Limiter (LLD)

    System Design · Hard

    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.

  4. 04

    Design a Notification Service System

    System Design · Hard

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

Know someone preparing? Send it to them:WhatsAppLinkedInX

Interviewed at Medibuddy 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!