Makemytrip's coding rounds are typically rated medium to hard, often involving 1-2 complex problems per round with an emphasis on clean, efficient code and edge-case handling. While comparable to Amazon's Bar Raiser in rigor, Makemytrip places a slightly higher weight on DSA fundamentals (especially Graphs and DP) and less on massive-scale system design questions unless you're interviewing for a senior role. Expect a strong focus on problem-solving approach over just the final answer.
Aim for 8-12 weeks of structured prep: Weeks 1-4 for core DSA (solve 2-3 LeetCode problems daily, focusing on Arrays, Graphs, Trees), Weeks 5-6 for system design basics (if applicable) and behavioral leadership principles, Weeks 7-8 for mock interviews and revisiting weak areas. Dedicate 2-3 hours daily with one full mock interview per weekend. Consistency is key—avoid last-minute cramming.
For SDE-1, focus intensely on DSA and OOPs. For SDE-2 and above, prioritize Low-Level System Design (design a rate limiter, parking lot, etc.) and scalability concepts. All levels must prepare deeply for the 'Leadership Principles' round—Makemytrip evaluates 10-12 principles (like 'Customer Obsession,' 'Bias for Action') using the STAR method. Also, have 2-3 in-depth questions ready about their tech stack (often Java/Go, AWS microservices).
Top mistakes include: 1) Rushing to code without clarifying requirements and edge cases, 2) Giving vague behavioral answers without quantifiable results (use metrics), 3) Neglecting to discuss trade-offs in system design, and 4) Not researching Makemytrip's specific products (like their dynamic packaging engine or trip disruptions AI). Interviewers look for structured thinking and ownership—demonstrate both in every round.
Standout candidates demonstrate 'impact-oriented' problem-solving. In coding rounds, they write production-quality code with tests. In behavioral rounds, they align their past projects with Makemytrip's leadership principles using specific, data-backed stories. For system design, they ask clarifying questions about *their* scale (e.g., 'How many bookings per second?') and propose iterative, scalable solutions. Showing genuine curiosity about their business challenges (travel domain) is a huge plus.
The process usually takes 4-6 weeks: 1-2 weeks for resume screening, 1 week for initial HR call, 2-3 weeks for technical rounds (typically 4-5 rounds in a single day or spread over a week), then 1-2 weeks for team matching and offer. If you haven't heard back 10-14 days after your final round, a polite follow-up email to your recruiter is appropriate. Delays often occur due to panel availability or team restructuring.
SDE-1: Heavy focus on DSA (medium-hard), OOPs, and basic behavioral questions. SDE-2: 40% DSA (medium), 30% Low-Level System Design, 30% behavioral/principle-based questions with focus on project leadership. SDE-3: Minimal DSA; major emphasis on High-Level System Design (multi-service architectures, data pipelines), deep behavioral questions about architectural decisions and mentorship, and often a 'Bar Raiser' round assessing cultural impact across the org.
Use LeetCode (filter by company tags), 'Grokking the System Design Interview' for design, and Amazon's 'Leadership Principles' guide (directly applicable). Study Makemytrip's engineering blog for tech stack insights. For mocks, practice with ex-interviewers from Pramp or Interviewing.io, and explicitly ask them to simulate Makemytrip's 'clarify-requirements-first' approach. Also, review recent Glassdoor reports for any pattern shifts in their question types.
