Reports describe a Myntra Software Engineer process built around an online assessment and DSA-heavy live rounds, with occasional CS fundamentals, system design for a senior role, and a managerial conversation.
$38K
Avg. Base Comp
$62K
Avg. Total Comp
3-6 rounds
Typical Rounds
Not reported
Process Length
Myntra's Software Engineer interviews in these reports are built around data structures and algorithms. Candidates describe an online assessment, then live coding rounds where the problems range from binary search and prefix sums to dynamic programming and graphs. Reported questions include trapping rain water, house robber, searching a rotated sorted array, right view of a tree, and finding subarrays with equal zeros and ones.
Interviewers appear to care about how you improve a solution, not just whether it runs. One candidate said they pushed past brute force toward better time and space complexity, and another dry-ran code against test cases and fixed edge cases they had missed. Another candidate, given a twist on house robber, lost most of the round to confusion; saying early that a variation is unclear would likely have helped.
Beyond coding, fundamentals show up in smaller doses: relational versus nonrelational databases, OOP abstraction, Java and a little SQL. A senior backend candidate also had a system design round and a conversational managerial round. Outcomes were mixed across these reports, with both offers and rejections. Treat this as a pattern from a small sample and confirm the exact format with your recruiter.
Synthesized from 12 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Myntra process.
My interview process at Myntra started with an online assessment using Mettl, which was honestly frustrating. The MCQ section had code snippets with obvious errors—random characters, syntax that wouldn't compile—and I couldn't tell if these were platform glitches or intentional tricks. I had to guess on several answers just based on what seemed least wrong. The coding round was worse: the problem descriptions were vague, they'd introduce concepts without explanation, and when a test case failed, there was no feedback—no input shown, no console output, nothing. I had to reverse-engineer what the problem wanted from minimal examples.
Despite that rough start, I moved forward to two technical rounds. The first focused on fundamentals: arrays, strings, and stacks—pretty standard stuff and manageable. The second round jumped to graph problems, specifically toposort with follow-ups, which was noticeably harder. Then they shifted gears entirely and gave me a JSON response scenario: I had to build a system that analyzed login attempts and flagged cases where the same person logged in from different IP addresses within a 10-minute window. It was a mix of data structure choices and logical thinking rather than pure algorithmic difficulty.
The whole experience felt inconsistent—the assessment tool was poorly designed, the problem statements lacked clarity, but the actual interview rounds with a person were more reasonable. I came away with an offer, though I'd say the Mettl platform alone would have killed my motivation if the later rounds hadn't been better structured.
Prep tip from this candidate
Don't stress over Mettl's buggy MCQ section—assume platform issues and move on quickly. For the coding rounds, practice graph problems like toposort and be ready to handle real-world scenarios (like login fraud detection) that combine DSA with system thinking.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Myntra
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Sharding vs Partitioning | |
| International e-Commerce Warehouse | |
| Simple Explanations | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Random SQL Sample | |
| Flight Records | |
| Prime to N | |
| Upsell Transactions | |
| Top 3 Users | |
| P-value to a Layman | |
| Recurring Character | |
| Project Pairs | |
| Address Schema | |
| Retailer Data Warehouse | |
| Permutation Palindrome | |
| Download Facts | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Daily Retention Summary | |
| Average Quantity | |
| Completed Shipments |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an online assessment before any live interview. One senior backend candidate took it on Mettl; another reported two coding questions on Unstop alongside fifteen multiple-choice questions on OOPs, DBMS and operating systems. Others described a dynamic programming problem plus an easy sliding window question, or five coding questions mixed with five subject-based ones.
Several candidates describe two live DSA rounds. Reported problems include trapping rain water, graph path finding, house robber with a twist, binary search and greedy questions, rotated array search, prefix sums, and tree right view. Interviewers reportedly pushed for better complexity than brute force, so talk through your approach and flag confusing twists early.
One candidate was asked about relational versus nonrelational databases and how abstraction works in OOP when the coding question ran short. Another reported questions on Java and SQL. The senior backend candidate had a system design round on architecture patterns and trade-offs; no other candidate here reported one.
Two candidates described a managerial round that was largely conversational, covering current and previous roles, accomplishments and how they solved problems. The senior backend candidate's final HR round covered compensation, role expectations and team fit. Be ready to walk through your projects and decisions clearly.
