Myntra Interviews

I recently went through the Myntra Ramp Up off-campus hiring process for the Software Engineering Winter Internship, and it was a challenging yet rewarding experience that tested my core problem-solving skills and fundamentals.

📝 Online Assessment (OA)

The process began with an online assessment that consisted of:

• Coding questions (DSA-based)
• MCQs on Computer Science fundamentals

The assessment focused on logical thinking, data structures, and core CS concepts rather than tricky or obscure problems. After clearing the OA, I was shortlisted for the interview rounds.

💻 Technical Interview – Round 1

The first technical interview was conducted online by a senior female software engineer.

She started by asking for my introduction and discussed my previous work experience as a Summer Intern at Accenture. After that, we moved to the coding questions.

She shared a Google Docs link containing the problem statement.

The first question was graph-based, involving DFS concepts.

I carefully went through the problem statement and started by explaining my approach step by step.

I used pseudocode and dry runs on sample cases to validate my logic.

With some hints and guidance from the interviewer, I was able to finalize the approach.

After that, she asked me to open an online code editor and implement the complete working solution.

I wrote the code, encountered a few errors initially,

Debugged them, and eventually completed the solution successfully.

Since we were running short on time, she quickly shared the second problem and mentioned that I only needed to explain the approach and pseudocode.

I explained the logic clearly and performed a dry run on sample inputs.

She seemed satisfied with the explanation.

At the end, she asked if I had any questions for her. I asked a few questions related to her experience at Myntra and the role, and that concluded the first round.

⚡ Technical Interview – Round 2

Soon after completing the first round, I received a call from HR informing me that I had cleared Round 1 and that Round 2 would take place within the next 30 minutes.

I was excited and nervous at the same time.

The second interview was conducted by a Senior Software Engineer.

He didn’t have a predefined question ready initially and took some time to decide.

Eventually, he gave me a problem based on the “Burning Tree” concept.

I quickly explained my approach and logic, and the interviewer was very supportive and interactive throughout the discussion.

He then asked me to code the solution.

I implemented it, but initially, the code did not produce the correct output.

We debugged the solution together, identified the issue, and fixed it.

Finally, the code worked as expected, although it took slightly longer than anticipated.

The interview concluded after that discussion.

🎉 Final Result

After the interviews, I had mixed feelings and was anxiously waiting for the result. The very next day, I received an email informing me that I had been shortlisted for the Myntra Winter Internship.

✨ Overall Experience

The entire process was fair, transparent, and well-structured

Interviewers focused heavily on problem-solving approach and clarity of thought

Hints were provided when required, making it a great learning experience

Emphasis was more on fundamentals and reasoning rather than memorized solutions

Overall, the Myntra Ramp Up hiring process was a valuable experience and gave me strong exposure to how top product-based companies evaluate engineering candidates.

Hello everyone, I know how much we all love reading real interview stories before our own placements, so here’s mine! I’m in my final year at UPES, Dehradun, and got the chance to interview for the Software Development Engineer (SDE) Internship role at Myntra through an open campus drive on Unstop.

This is a quick walkthrough of my experience — from the online assessment to the interviews. Hopefully, it helps you in your own prep!

Phase 1: Online Assessment (Unstop)

I started my journey with an online assessment hosted on Unstop. It featured a mix of coding and theoretical questions. I faced two coding questions, which I found to be in the easy-medium range, along with 15–17 MCQs covering DBMS, OS, CN, OOPs, and Aptitude. There were also 2–3 debugging MCQs, primarily testing basic error identification rather than trick questions. I managed to solve both coding questions and most of the MCQs successfully.

Phase 2: Technical Interviews

Both interviews were elimination rounds and took place on the same day.

Round 1: DSA Focus (~60 minutes)

This round was purely centered on problem-solving. I was given two problems:

• Problem 1: Find the unique element in a sorted array where all other elements appear twice.
• Problem 2: Another array-based problem.

For each problem, I first explained my logic clearly, then proceeded to write clean, efficient code, and finally discussed the time and space complexity with the interviewer. Within about an hour, I received a call informing me that I had cleared Round 1 and should get ready for the next.

Round 2: DSA + Project + Applied Questions (~75 minutes)

This round began with a casual introduction before we moved into a deep discussion about my summer internship project. The interviewer showed a keen interest in my design choices, the challenges I encountered, and my rationale for picking certain technologies.

Following the project discussion, we transitioned to the problem-solving segment:

• Problem 1: 3-Sum Problem (LeetCode #15) — the interviewer asked me to jump straight to the optimal approach. I implemented the sorted array + two-pointer method, achieving an O(N²) solution, and we thoroughly discussed edge cases and how to handle duplicates effectively.
• Problem 2: A string manipulation question, which primarily tested my careful handling of various edge cases.

Alongside the DSA problems, I was also asked a couple of applied questions related to my personal projects: one about designing a Python automation script, and another centered around a RAG (Retrieval-Augmented Generation) chatbot. I noticed the interviewer kept confirming my approach multiple times, likely to test my conviction, but I stayed firm and explained everything confidently.

Towards the end, we even touched on a system design-style discussion, where I was asked about the features of Google Meet and how one of them could be designed at a high level.

Unfortunately, I didn’t receive any official communication after this round. Later, my college placement team informed me that I couldn’t make it through.

Although I couldn’t clear the final round, the overall experience was incredibly valuable. It gave me a taste of how product-based interviews work — from DSA-heavy questions to resume deep dives and even touches of system design. One thing I realized is how important it is to know my personal projects inside out. This experience definitely sharpened my preparation, and I walked away more confident for future opportunities.

I applied for the SDE-1 Data role at Myntra through LinkedIn Easy Apply in early February 2025. Within two hours, a recruiter contacted me, leading to an online assessment (OA) and an onsite interview schedule for the following Friday.

The OA was conducted on the Mettl platform and consisted of three questions over two hours. I managed to pass, although I struggled with the last question.

The onsite interviews comprised four rounds:

Round 1: Technical (DSA Focused)
This round was of medium-hard difficulty and covered topics like Strings, Linked List Cycle Detection, and an advanced graph problem, with which I struggled a bit.

Round 2: System Design + Data Engineering Concepts
This round involved discussions on system design and core data engineering concepts. There was also one heap-based DSA question.

Round 3: Hiring Manager Round
In this round, we discussed my past projects and experiences in depth, and my knowledge of data engineering was assessed.

Round 4: HR Round
The final round, conducted on the following Tuesday, consisted of general behavioral questions.

Ultimately, I received a 'Not Selected' verdict. The feedback I received indicated a 'lack of clarity in some areas', particularly needing improvement in explaining concepts, strengthening system design, and advanced DSA.

As a 2023 Civil Engineering graduate from NIT, I currently work as an SDE1 at a bootstrap startup, bringing about 1.7 years of professional experience plus 6 months as an intern. A recruiter reached out to me via Naukri for an SDE-1 frontend position at Myntra in Bengaluru.

My interview process began with an Online Assessment. This round consisted of a question focused on arrays, another on implementing frontend functionality, and a JavaScript-based problem.

Following the OA, I proceeded to Technical Round 1, which lasted an hour. The discussion started with my current work experience. Afterwards, I was presented with questions related to 'Next Greater Element I' and 'Next Greater Element II'. The round concluded with a recursion problem specifically using JavaScript.

Unfortunately, I was unable to provide a satisfactory answer for the JavaScript-based recursion question, which ultimately led to my rejection from Myntra.

About Me

I hold a B.Tech degree from a Tier 1 NIT and currently work as an SDE1 at a startup, with 14 months of professional experience.

Myntra HR contacted me through Instahire regarding an SDE-1 Frontend Engineer role. After several rigorous interview rounds, I was fortunate enough to receive and accept their offer. Here’s a detailed breakdown of my interview process:

Round 1: DSA and JavaScript Questions

This round began with a Data Structures and Algorithms (DSA) problem. I was asked to solve the First Missing Positive problem. I managed to implement an efficient solution and completed it ahead of time. Following this, the interviewer transitioned to JavaScript-related questions. The JavaScript section covered various topics, including:

• The performance benefits of using promises.
• Predicting the output of a given code snippet.
• Discussions on the Virtual DOM and reconciliation process.
• JavaScript’s concurrency model, event loop, and lifecycle hooks.

Solving the DSA problem quickly allowed me extra time to address these additional questions from the interviewer.

Round 2: DSA, JavaScript, and CSS Questions

In the second round, I faced two DSA problems:

• Finding the minimum number of bit replacements required to convert one binary string to another.
• The Set Matrix Zeroes problem.

After the DSA portion, I was given another JavaScript code snippet to evaluate and explain its output, with a particular emphasis on demonstrating my understanding of pass by value vs. pass by reference. Finally, the interviewer asked me about CSS media queries and how to apply them effectively in web development.

Round 3: Projects and HLD Design Discussion

This round started with an in-depth discussion about my recent projects. I shared details about my work, the technologies I used, and the challenges I overcame. Following this, the interviewer tasked me with designing a High-Level Design (HLD) for a payment system. I proposed several solutions, but the interviewer challenged my approaches by presenting different scenarios where they might fall short, pushing me to think more deeply. To simplify the problem, he narrowed it down to a cash-on-delivery payment system, for which I offered a revised and more robust solution. Additionally, we discussed concepts related to CAPTCHA generation and authentication.

Round 4: HR Discussion

The final round was a standard HR interview. I was asked several common questions, including:

• Why I wanted to leave my current organization.
• Why Myntra should hire me.
• What I considered to be my weaknesses.
• How I transitioned from an Electrical Engineering graduate into a Software Developer role.

The discussion also touched upon my career aspirations and long-term goals.

Final Verdict

Four days after completing my final interview, I received a call from HR informing me that I had been selected for the position. It was a great outcome!

The interview process at Myntra kicked off on a weekday, with multiple candidates present for various roles. I had applied for the Frontend Developer position, which involved a total of four rounds: three technical rounds held at the Myntra office, followed by one HR round.

Technical Round 1: This round focused on Data Structures and Algorithms. I was given a DSA question based on binary search and was required to provide the pseudocode. The specific problem was Search in Rotated Sorted Array. Additionally, I faced questions on core JavaScript concepts, including objects, the this keyword, and hoisting.

Technical Round 2: This round delved deep into ReactJS. They asked me to explain the differences between functional and class components. We also discussed optimization techniques like useMemo, useCallback, and React.memo, as well as the concept of the Virtual DOM and other common ReactJS topics.

Hiring Manager (HM) Round: This round was primarily about my past work experience and included several situational questions. For instance, I was asked: "What would you do if you estimated a task to take 5 days but later realized it would take more time? How would you handle it?" and "Do you prefer team discussions or working independently?"

After successfully clearing these rounds, there was a waiting period of nearly a week before my HR round was scheduled. While I anticipated discussions about compensation, the questions were more about role expectations, such as: "What if you're asked to work on the backend as well?" and they also asked for the names of the interviewers to verify which team was involved.

About 1.5 weeks later, a different HR representative called me to discuss compensation. I informed them that I already had another offer and requested that Myntra's offer at least match it. The HR person stated they would look into it. A few days later, I received another call from HR, advising me to accept the offer as it was, stating that the compensation was fixed and non-negotiable. I agreed to their terms. Initially, there was a delay in receiving the official offer letter, which caused some uncertainty.

P.S.: I have since received the offer letter and successfully requested an extension for my joining date due to my notice period at my current company, which Myntra graciously agreed to.

I applied for a Senior Software Engineer position at Myntra in Bengaluru, India. I have 3 years of experience and hold a B.Tech from a Tier-3 college. The interview process consisted of five rounds, starting with a walk-in DSA screening, followed by a PSDS round, two virtual system design rounds, and finally, a virtual HR round. I received an offer upon completion of all rounds.

Round 1 (DSA Screening) - Walk-in Drive

Round 2 (PSDS) - Walk-in Drive F2F

Round 3 (System Design) (1 hour) - Virtual

Round 4 (Managerial) (1 hour) - Virtual

Round 5 (HR) (30 mins) - Virtual

I was delighted to receive an offer for the position.

My interview process at Myntra for the SDE1 position consisted of a single technical round. The interviewer started by asking for my introduction, then we delved into a detailed discussion about my past projects. After that, I was presented with two DSA problems to solve.

Current Position: Program Associate at Wells Fargo

With 8 months of experience, I applied for the Software Engineer - Backend (M1) role at Myntra in March 2022. The entire interview process was very well-organized, and I found the interviewers to be friendly and supportive throughout.

Round 1: OA Round

The first round was an Online Assessment with 31 questions across 8 sections, to be completed within 60 minutes. It included one programming question and multiple-choice questions on Java, HTML, JS, Data Structures, and DBMS.

Round 2: DS Algo Round

In this round, I was interviewed by two individuals who asked me to solve two coding problems on screenshare. We had a productive discussion on various approaches for each question, and I was expected to provide the time and space complexity for every solution proposed.

Round 3: Hiring Manager Round

This round commenced with the manager's introduction, followed by an overview of the role's responsibilities and the type of candidate they were seeking. I then introduced myself and discussed my projects in detail. The conversation also delved into DBMS concepts, specifically 'what is indexing,' 'why it is used,' and a discussion about 'Third Normal Form (3NF).' Additionally, I encountered OOPS-based questions and several situation-based questions, such as how I would handle a conflict with my manager or if I couldn't meet a deadline. I made sure to quantify my experiences, as I was advised to give numbers to my work, such as scaling applications from a thousand users to lakhs of users, or solving 80% of pending bugs in a project.

Round 4: HR Round

The final round was a conversational HR discussion. It began with my introduction and a brief summary of my projects and current responsibilities. The HR representative asked me about my reasons for seeking a switch, especially after only 8 months of experience, and why I was interested in Myntra.

The interviewers in all rounds were exceptionally friendly, and I must give a special mention to the HR team who constantly kept me updated and managed the entire process smoothly.

Verdict - Selected & Accepted the offer

My interview journey at Myntra for the SSE role began with a Coding Round. This round featured two problems: the first was Reverse Nodes in k-Group, and the second involved converting number 'x' to 'y' using only two operations – multiplying by two or subtracting one. I felt I performed exceptionally well, successfully nailing both questions.

The second Coding Round presented Letter Combinations of a Phone Number. The interviewer then modified this problem: one number would denote the first character, and repetitions of the same number could point to subsequent characters. For instance, '32' would result in 'da', while '322' could yield {'daa', 'db'}. I managed to code solutions for both parts but struggled to determine the time complexity for the modified version.

Next, I faced the Low-Level Design (LLD) Round. Here, the task was to design a system capable of scheduling millions of jobs daily at precise times, with an error margin of no more than 1 second. The system also needed to handle recurring jobs and be distributed across multiple servers for triggering. The interviewer's primary focus was on the mechanism for triggering jobs accurately at the specified time. I honestly didn't feel I performed very well in this round.

Finally, I had the Hiring Manager Round. This round consisted of standard HR questions, and I was also asked to design Google Drive. I believe I handled this round adequately.