What Is the Myntra Interview Process Like? (Round by Round)

Candidates report five to six rounds at Myntra. Myntra's own technology leadership has described five or six interviews with a panel of senior developers, architects, and managers. Candidate reports match that shape. A timed online assessment comes first, and two or three live coding interviews follow it.

Experienced candidates then report a design round and a hiring manager round, and an HR conversation closes the process. Review site aggregates place the median near two weeks for software engineer roles, though individual reports run both shorter and longer.

Quick Overview

Stage 1: The Online Assessment

Most reports begin with a timed online test, and the platform varies by drive. Candidates name HackerEarth and Mettl, and some accounts mention HackerRank. The content varies as well.

One senior candidate reports a 90 minute test on HackerEarth with a single hard array problem. An internship candidate reports about 90 minutes on Mettl with three coding problems and 10 to 15 multiple choice questions on code output and errors. If this stage is new to you, read what an online technical assessment is.

Stages 2 and 3: The Coding Interviews

Expect two live interviews of about an hour each on data structures and algorithms. Trees appear more often in reports than any other topic. Reported questions include deleting a node from a binary search tree, rebuilding a binary search tree from preorder and inorder traversals, and counting leaf nodes in an n-ary tree.

Other reported problems include stock buy and sell for maximum profit, counting distinct pairs with a given difference, the intersection point of two linked lists, and the minimum knight moves to a target square. One reported loop used a shared document rather than a coding tool. Interviewers ask for the running time and for alternative approaches, so state both while you write.

Stage 4: The Machine Coding or Design Round

Senior candidates report a round that grades design rather than algorithms. One senior report describes a machine coding round, where the task was to build the back end of a small e-commerce site entirely in memory. An administrator adds products, and a user views and buys them. Payment is either direct or by installments within a credit limit.

Other senior reports describe class design questions instead, such as a bus reservation system with its classes and methods, or a parking lot designed at both the high and the low level. Junior candidates report this round far less often. The full round is covered in the Myntra system design interview.

Stage 5: The Hiring Manager Round

Interviewers ask about your current responsibilities in detail. Candidates report questions about the technology stack they use, their API design choices, and the use cases behind them. Design questions appear here too.

Reported examples include a notification system for changes in a database, a payment flow, a rate limiter, and a database that must serve very high read and write traffic.

Stage 6: The HR Round

The closing round is behavioral. Candidates report questions about personal projects, strengths and weaknesses, the hardest problem they have solved, and their reason for changing jobs. Prepare the motivation question with how to answer why Myntra.

How the Campus and Internship Paths Differ

Myntra runs an internship hiring track that it calls Myntra RampUp, advertised off campus through an online hiring platform. Candidates there report an assessment followed by two technical interviews, with very short gaps. One candidate reports hearing the result of the first interview within about 30 minutes, with the second interview scheduled immediately, and the final result the next day. Campus loops also test core computer science subjects more heavily than experienced loops do.

Timeline and Decision

Candidates report gaps of a few days between the later rounds. Individual reports vary widely, so plan for a wait of several weeks rather than several days.

Myntra's technology leadership has described a score from one to five for each round, with three and above moving a candidate forward. The same account says junior candidates are judged on code design, modularity, the choice of data structures, naming, and documentation. Senior candidates are judged in addition on scalability, reliability, performance, and security. Write code in the interview that would pass a code review, not only code that passes the test cases.

Questions to Ask Them

Every round ends with time for your questions, so use it to judge the team. Useful questions here include how the platform is prepared for the End of Reason Sale, how ownership is divided between services, and how on-call works on the team you would join.

How to Prepare

• Drill algorithm patterns first. The assessment and the two coding rounds decide most rejections, and Grokking the Coding Interview teaches the patterns behind them.
• Revise trees thoroughly. Binary search trees, n-ary trees, and traversal problems appear in report after report.
• Learn class design properly. Grokking the Object Oriented Design Interview covers what the machine coding and LLD rounds grade.
• Prepare one project in depth. The hiring manager round asks about your current work in detail, so know the parts you did not build as well as the parts you did.
• Set your expectations on timing. How long it takes to hear back after a Myntra interview lists the reported waits.