MakeMyTrip Interview Experience | Senior Software Engineer Android (3 Years Experienced)
Question Details
Current Experience: 3 Years.Profile: Senior Software Engineer | AndroidThe interviewer was so laid back that I became unsure if I wanted to join the company.Round 1(Techni...
Full Details
Current Experience: 3 Years. Profile: Senior Software Engineer | Android The interviewer was so laid back that I became unsure if I wanted to join the company. Round 1(Technical Interview): It is a Zoom Call for around 1 hour Data Structure Question: Find a number of islands Article Link: https://www.geeksforgeeks.org/dsa/find-the-number-of-islands-using-dfs/ Practice Link: https://www.geeksforgeeks.org/problems/find-the-number-of-islands/1 Shuffle an Array Article Link: https://www.geeksforgeeks.org/dsa/shuffle-a-given-array-using-fisher-yates-shuffle-algorithm/ Fragments setArgument getArgument and Constructors and passing checking for onSavedInstance null before starting an activity. Round 2(Technical Interview): It is a Zoom Call for around 40 minutes Activity A calls Activity B life cycle in the middle Login Screen Implementation using MVP Design Patterns used. ANR Encountered LiveData Builder Design Pattern DS Question - Linked List with the nth element. Rotate first k elements and put it in the end Kotlin basics Android Architecture Components
About This Question
This is a reported interview question from a makemytrip interview for a android role (senior level) during the phone screen round reported in 2025.
It covers the following topics: Oop, Linked List, Sql, Graph, Graphs, Arrays .
More Makemytrip Interview Questions
About Makemytrip Interview Reports
This question was reported by a candidate who interviewed at Makemytrip. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Makemytrip are the higher-signal extractions to take from this report.
For broader preparation context, the Makemytrip interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Makemytrip reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Makemytrip Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Makemytrip reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.