What to Expect in the Myntra System Design Interview

Design at Myntra is tested in two different rounds. Senior candidates report a machine coding or low level design round, where you produce working code or a class design. They also report a hiring manager round that includes a high level design discussion.

The first round is graded on code, the second on the discussion. Junior candidates report the design rounds far less often.

The Machine Coding and LLD Round Comes First

A machine coding round gives you a written requirement and a time limit, and asks for a small working program, usually a console application with no user interface and no database.

One senior candidate reports exactly this at Myntra: build the back end of a small e-commerce site entirely in memory. An administrator adds products through the console, a file, or an external service, while a user views the products and buys them, either directly or in installments within a credit limit.

Other senior reports describe a class design question instead, such as a bus reservation system or a parking lot designed at both levels. If the difference between these rounds and a high level discussion is new to you, read the difference between system design and LLD.

What This Round Grades

Four things decide the machine coding round. First, the program must run and produce correct output for the stated cases, and second, the classes must match the domain, with responsibilities you can name in one phrase.

Third, a new requirement should be easy to add without a rewrite, and the installment payment option is a good example, because payment methods change often. Fourth, you must explain your choices afterward.

Spend the first 10 to 15 minutes on clarifying questions, then build the smallest complete version, because clean unfinished code scores better than a large submission that does not compile. For the general shape of the round, see what a machine coding round is.

The High Level Design Questions

Candidates report design questions in the hiring manager round and in separate design rounds for senior roles, and some are about e-commerce problems, such as a payment flow or a notification system for changes in a database. Others are about the Myntra app itself, and reports mention design patterns and the SOLID principles in that discussion.

The rest are general: reported examples include a location based search application with a database schema and an API design, and a review feed with caching and push or pull delivery. Others are trending topics with demographic filters, a rate limiter, and a database that serves very high read and write traffic. Prepare both kinds, because the interviewer chooses.

A Worked Example: Catalog and Checkout Under Sale Traffic

Here is a high level plan in the order an interviewer expects to hear it.

1. Requirements (5 minutes). Assume a large fashion catalog with size, color, brand, and fit attributes, and traffic that is steady most of the time and extremely high during a sale event. Correctness matters most wherever money or stock is involved.

2. Catalog and search. Store the product record once, then build a separate read model for browsing and filtering. Fashion products have many attributes, so the number of filter combinations grows quickly, which is why you precompute the common facets and cache them. Stale prices are unacceptable, so invalidate price and stock entries on every change.

3. The checkout path. Reserve stock before payment, with a short expiry on the reservation. Write the order, then publish an event that a queue sends to payments, the warehouse, and notifications, which keeps the shopper-facing write short.

4. Idempotency. Idempotency means that repeating a request does not change the result a second time, which matters because payment callbacks arrive more than once. Give every request a key, store the keys, and ignore repeats.

5. Returns. Returns are a large part of fashion commerce, because size and fit are guessed online, so model the return and the refund as explicit states, and say how stock returns to the catalog.

6. Sale traffic. Queue everything that is not urgent, such as notifications and analytics, protect the database with caches for catalog reads, and add rate limits while reducing service in steps rather than failing completely.

7. Measurement. Say what you would watch in production: failed payments, stuck orders, oversold items, and cache hit rate.

What the Interviewer Grades

State the requirements first, then a simple design, then the trade-offs you considered, and name the failure cases before the interviewer asks about them.

Myntra's technology leadership has said in public that senior candidates are judged on scalability, reliability, performance, and security, so address all four somewhere in your answer. The hiring manager also asks in detail about the work you own now, so be ready to break a design into parts you could deliver.

Common Mistakes in These Rounds

• Coding before clarifying. A written machine coding requirement is rarely complete, so silence for the first ten minutes usually produces the wrong program.
• Over-designing the small program. Applying many patterns in one session usually produces unfinished code.
• Ignoring returns. A fashion order design that stops at delivery is incomplete.
• Skipping stock correctness. Overselling during a sale event is the failure the interviewer is testing for, so explain your reservation approach.
• A generic answer. A social network answer scores poorly when the question is about payments or a product catalog.

How to Prepare

• Practice building under a timer. Write a small in-memory store back end in 90 minutes, then add a second payment method without rewriting the first.
• Learn class design properly. Grokking the Object Oriented Design Interview covers the structure this round grades.
• Study the building blocks. Grokking the System Design Interview covers queues, caches, sharding, and replication.
• Place the round in the loop. See where design appears in the Myntra interview process, and prepare the motivation answer with how to answer why Myntra.
• Know the waiting times. How long it takes to hear back after a Myntra interview lists the reported gaps.