
MakeMyTrip Frontend Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 14 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at MakeMyTrip.
Frontend Engineer
3 Technical rounds: First was like general Frontend, React questions and some React logical written coding questions. 2. Coding round (like leetcode) 3. Coding round (system design) - Had to write and explain architecture, design, business logic in google doc.
- How do you handle React performance optimization?
- Can you explain core JavaScript concepts?
- What are your thoughts on different JavaScript libraries?
Senior Frontend Developer
There were supposed to be 3 interview rounds. The first round went well. The second round was rescheduled because the original interviewer didn't show up, and it ended up being with someone unexpected, a mobile application principal engineer instead of a web engineer. I thought I did well in the second round and solved the coding problem, but I wasn't selected. The HR was professional and informed me that my coding practices weren't up to par, which I disagree with. They didn't ask me any frontend or React questions.
- Can you solve this JS problem?
- What about async defer?
- Do you have any JS DOM related questions?
Frontend Developer
This was the worst interview experience. The first round, they just asked me to introduce myself and then immediately asked me to share my screen and write code for Promise.all(). I said I wasn't sure, and they moved on. Then came two more questions: rotating a 2D array and infinite function currying. That was it. They didn't ask anything about JavaScript fundamentals, React, or the role itself. It felt like they only cared about the code output, not understanding the candidate. This isn't a good way to interview; you should assess the candidate's understanding first. Copy-pasting questions from Zoom chat and expecting a solution is not how it's done. In this one-hour interview, we barely spoke for 3 minutes. They just gave the questions and waited for the code. I doubt they could even solve them themselves if asked. Googling 'hard JavaScript questions' isn't a proper interview strategy. It seems like they would have passed me if I knew the answers without basic JS knowledge, which is wrong. I hope you don't get this interviewer; they don't care about your background, experience, or the role, only the output.
- What is Promise.all and can you code it?
- Can you code a solution to rotate the array [[1,2,3], [4,5,6], [7,8,9]] to [[7,4,1], [8,5,2], [9,6,3]]?
- Can you write code for infinite function currying?
MakeMyTrip Frontend Engineer Interview Questions
Quoted word for word from MakeMyTrip interview reports.
“What is the difference between class and function components in React?”
Read reports →“How does inheritance work in JavaScript?”
Read reports →“What is hoisting in JavaScript?”
Read reports →“Can you code a solution to rotate the array [[1,2,3], [4,5,6], [7,8,9]] to [[7,4,1], [8,5,2], [9,6,3]]?”
Read reports →“Regarding JS hoisting, what about variable scoping inside and outside a function?”
Read report →“Can you write code for infinite function currying?”
Read report →“What does 'offline first' mean?”
Read report →“What are the basics of Javascript?”
Read report →“What is Promise.all and can you code it?”
Read report →Formats, difficulty and experience
Across all 14 MakeMyTrip interview reports.