MakeMyTrip is India's leading online travel platform, handling flight, hotel, and holiday bookings for tens of millions of users.
Their 2026 SWE interviews place heavy weight on large-scale system design: inventory aggregation, pricing engines, and high-availability search. You should understand distributed caching, eventual consistency, and how to design systems that survive supplier API failures gracefully.
About MakeMyTrip
MakeMyTrip (MMT) is India's largest online travel platform, listed on Nasdaq. It covers flights, hotels, holiday packages, and bus/rail booking across India and international routes.
Apply via MakeMyTrip careers portal, LinkedIn, or employee referral
HR screening call to assess availability and expectations
Online coding test on HackerEarth or HackerRank (90 minutes)
Two to three technical interview rounds conducted remotely
System design round for senior levels
HR and compensation discussion leading to offer
Round 1 - Coding Assessment (90 min)
Three problems covering DSA topics such as dynamic programming, graphs, and string manipulation on HackerEarth.
Round 2 - Technical Interview I (60 min)
Core CS concepts, Java or Python internals, OOPS design patterns, and one DSA problem solved with explanation.
Round 3 - System Design (60 to 75 min)
Design a flight search aggregation engine or a hotel inventory caching layer. Emphasise consistency models and failover.
Round 4 - Hiring Manager (30 to 45 min)
Behavioural questions using STAR, discussion of past scale challenges, and team-fit assessment.
Sourced from 2+ candidate post-mortems. Hit Practice to answer any one with AI voice feedback.
2 more questions. Sign up to unlock all
Sign up free: unlock all questionsThe typical MakeMyTrip recruitment process has 6 stages: Apply via MakeMyTrip careers portal, LinkedIn, or employee referral → HR screening call to assess availability and expectations → Online coding test on HackerEarth or HackerRank (90 minutes) → Two to three technical interview rounds conducted remotely → System design round for senior levels → HR and compensation discussion leading to offer.
MakeMyTrip typically conducts 4 interview rounds: Round 1 - Coding Assessment (90 min): Three problems covering DSA topics such as dynamic programming, graphs, and string manipulation on HackerEarth.; Round 2 - Technical Interview I (60 min): Core CS concepts, Java or Python internals, OOPS design patterns, and one DSA problem solved with explanation.; Round 3 - System Design (60 to 75 min): Design a flight search aggregation engine or a hotel inventory caching layer. Emphasise consistency models and failover.; Round 4 - Hiring Manager (30 to 45 min): Behavioural questions using STAR, discussion of past scale challenges, and team-fit assessment..
HireStepX recommends the RADIO framework for this type of interview: Requirements clarify scope: API design surfaces the contract: Data model grounds the schema: Implementation details cover components and trade-offs: Optimisations address scale and edge cases
To answer this question well, HireStepX recommends the RADIO approach: Requirements clarify scope: API design surfaces the contract: Data model grounds the schema: Implementation details cover components and trade-offs: Optimisations address scale and edge cases Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the RADIO approach: Requirements clarify scope: API design surfaces the contract: Data model grounds the schema: Implementation details cover components and trade-offs: Optimisations address scale and edge cases Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the RADIO approach: Requirements clarify scope: API design surfaces the contract: Data model grounds the schema: Implementation details cover components and trade-offs: Optimisations address scale and edge cases Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the RADIO approach: Requirements clarify scope: API design surfaces the contract: Data model grounds the schema: Implementation details cover components and trade-offs: Optimisations address scale and edge cases Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the RADIO approach: Requirements clarify scope: API design surfaces the contract: Data model grounds the schema: Implementation details cover components and trade-offs: Optimisations address scale and edge cases Ground your answer in a specific real example from your own experience.