← Interview experiences
Rejected

SDE-2 at MakeMyTrip

Difficulty
Process took
1-2 Weeks
Rounds
3
Format
Remote
Applied via
Job Portal

How it went

  • Not every interview process feels collaborative, but take it as a moment to stay confident in communicating your approach. Sometimes, culture or interviewer style won’t be a fit, even if your technical depth is solid.

What they would tell you

  • Not every interview process feels collaborative, but take it as a moment to stay confident in communicating your approach. Sometimes, culture or interviewer style won’t be a fit, even if your technical depth is solid.

How to prepare

  • If interviewing for MakeMyTrip, expect heavy rounds.
  • For LLD, brush up on not just class/method decomposition but also “standard” design patterns.

Their background

I’ve spent the majority of my career working in backend development, and designing APIs. I enjoy approaching DSA problems. This was my first time interviewing with MakeMyTrip at the SDE-2 level.

Round by round

  1. 1

    Data Structures & Algorithms60 min

    I could choose any language, so I went with Python for its readability. After a quick intro, I was given two DSA problems: Question-1: Group Anagrams: I tackled this classic hash-mapping/string manipulation problem by sorting characters to build the hash key, making sure to discuss edge cases and time complexity as I coded. Question-2: Reverse Nodes in k-Group: This required manipulating linked lists in segments, so I explained the approach before touching code—especially edge cases with groups less than k and in-place reversal. The round was focused, technical, and went smoothly.

  2. 2

    LLD60 min

    This round was concentrated on designing a vending machine system. Instead of pseudocode or white-boarding, the interviewer wanted me to jump directly into code, defining classes and their relationships. I initially outlined object flows and main methods in Notepad, then switched to IntelliJ for code structure. I explained my approach to state and cash logic, suggesting Chain of Responsibility (CoR) for cash computation, but didn't go deep into classic state management patterns since I manage state explicitly. The interviewer seemed to expect application of state design patterns and singleton, but I argued for explicit object references unless multiple instantiations are a realistic risk. The pace was rapid, and honestly, it felt less like a conversation and more like a checklist. My attempts to discuss design decisions and clarify requirements were largely set aside; the interviewer preferred to “see code first” before discussing, making the round feel transactional. There was a brief talk about how I’d handle concurrency, but it was cut off for follow-up on design patterns instead.

  3. 3

    Hiring Manager & Behavioral60 min

    This was a standard HM round focusing on past work experience, project ownership, team fit, and behavioral questions. Discussion revolved around “why MakeMyTrip,” my career progression, challenges faced in previous roles, and examples where I contributed beyond coding.

What came up

MediumRemote3 4 years

A candidate-reported account, lightly edited. Interview processes change by team and date.

Sources