Myntra

Myntra runs a role-specific loop that is mostly virtual, with an in-person or video onsite for final rounds. The engineering process is described below, with notes on how business and product roles differ.

1. Application and recruiter screen

Apply through the Myntra careers site, a referral, campus placement or a job portal such as Jobaaj. A recruiter reviews your profile for relevant skills and, for laterals, calls to confirm experience, notice period and expectations before scheduling anything.

2. Online coding assessment

Engineering candidates, especially freshers and early-career, receive a timed online test with two or three data-structure and algorithm problems, occasionally with a few MCQs on computer fundamentals. Business and analyst roles may get a case or an Excel-based exercise instead.

3. Technical interviews

One or two rounds of 45 to 60 minutes with engineers. These cover problem solving with live coding and, for experienced candidates, a deep dive into past projects and the systems you built.

4. Design round

Mid-level and senior engineers get a system design round: designing a catalogue search, a cart and checkout flow, or a notification service at Myntra's scale. Freshers may get a lighter low-level design or object-oriented design discussion.

5. Hiring manager round

A conversation with the engineering or business manager you would report to. It covers ownership, collaboration, how you handled ambiguity, and why Myntra. Product and category roles get a case-style discussion here on a real business problem.

6. HR discussion and offer

HR discusses compensation structure, ESOPs where applicable, joining date and background verification. Offers are usually released within a week of the final round.

The rounds below describe a typical software engineering loop. Product, analytics and category roles keep the same shape but replace coding with case and metrics discussions.

Round 1: Online coding test

Sixty to 90 minutes on a standard coding platform, auto-graded on hidden test cases. Problems are medium level; correctness and handling edge cases matter more than speed.

• Arrays, strings, hashing and two-pointer problems
• Trees and graphs traversal
• Dynamic programming basics

Round 2: Data structures and algorithms interview

Forty-five to 60 minutes with an engineer in a shared editor. You are expected to talk through the approach, discuss complexity, then code and test. Follow-up constraints are common.

• Top-k products by sales from a stream
• Interval and sliding-window problems
• Optimising a brute-force solution step by step

Round 3: Low-level or system design

Forty-five to 60 minutes. Freshers get class design; experienced engineers get distributed system design at e-commerce scale with a focus on trade-offs.

• Design a wishlist or cart service with high read traffic
• Model an order and returns workflow
• Caching, consistency and failure handling in a catalogue service

Round 4: Hiring manager interview

Thirty to 45 minutes on your past work, how you collaborate with product and design, and how you have handled production issues or missed deadlines.

• A feature you owned end to end
• A disagreement with a teammate and how it was resolved
• What excites you about fashion e-commerce

Round 5: HR round

Fifteen to 20 minutes on salary, notice period, work location in Bengaluru and joining timeline.

• Current and expected CTC
• Why are you leaving your current role
• Any offers in hand