Myntra Interview Experiences

1. 📝

   Online Assessment (1 hour)

   I applied through a referral from a college senior and got the online assessment link about a week later. It was a one-hour test: three coding problems and ten MCQs. I started with the MCQs because they were quick — mostly core CS stuff like time complexity, OS basics and a couple of SQL questions — and finished them in under ten minutes. Then I opened the coding section. The first problem was an easy array question and I finished it in about ten minutes. The second was a medium string problem with a hashmap; I got it passing all visible cases on the second try after fixing an off-by-one. The third was a harder graph-flavored one and I only had about fifteen minutes left, so I wrote a working but slow solution and it passed most of the test cases. I submitted with a minute to spare. Four days later I got a mail saying I had cleared the assessment and the DSA round was scheduled for the next week.

2. 💻

   DSA Round (virtual, shared document, 1 hour)

   This round was on a video call with a shared document, no IDE, so I could not run anything. The interviewer pasted the first problem: longest increasing path in a matrix. I first explained a plain DFS from every cell, said it would be exponential, then added memoization on each cell and wrote it out. He asked if there was another way and I mentioned treating it as a DAG and doing a topological sort; he was happy with just the explanation. Second was binary tree right side view. I wrote the BFS version that takes the last node of each level, and then he asked for the DFS version, so I wrote the right-first traversal that records the first node seen at each depth. The last one was a custom DP: seat men and women across two rows under adjacency rules. I took a few minutes to define the state, wrote the recurrence, and he pushed me to cut the state size. I got most of the way there when the hour ended. Later I heard optimization was what he was grading hardest.

3. 🧑‍💼

   Hiring Manager Round (1 hour)

   The hiring manager round came two days after the DSA round. It was one hour and honestly harder than I expected. She started with my resume and picked one project, then kept asking follow-ups: why this database, what happens if this service goes down, how would you test it. Then she went back to the DSA round and asked me to explain the trade-offs between the BFS and DFS versions of the right side view question, and when I would prefer recursion over iteration. After that it switched to behavioral questions: a time I disagreed with a teammate, a time I missed a deadline, and how I handle feedback. I gave examples from my college projects and internship. Near the end she asked why Myntra, and I talked about fashion catalog problems like size and fit. She was polite but did not give much reaction, so I walked out unsure how it went.

4. 🔹

   HR Round (15 minutes)

   The HR round was the next morning and it was only about fifteen minutes. The recruiter asked when I could join, whether I was okay with Bengaluru, and if I had any other offers in hand. I said I had one process ongoing elsewhere. She explained the general structure of the offer process and said the final decision would depend on the feedback from all rounds. I asked how long it would take to hear back and she said about a week. Nothing technical at all, just a relaxed chat. About ten days later I got a mail saying they were not moving forward. I did not get detailed feedback, but from the DSA round I knew I had left the last DP problem unfinished and had not pushed the optimizations far enough, and I think that was the main gap.

Key takeaway: Optimization was called out as the key differentiator in the DSA round — a working brute-force solution isn't enough, interviewers want to see it pushed further — and practicing multiple approaches (BFS vs DFS, recursive vs iterative) paid off in discussing trade-offs on the spot.

1. 📝

   Online Assessment (on Unstop)

   I registered for the internship drive on Unstop after seeing it on my college placement group. The online assessment link came a few days later with a fixed time window. The test had three parts. First there were around fifteen to seventeen MCQs on core CS subjects — data structures, OS, DBMS and a few on OOP. I did those first and they took about fifteen minutes. Then there were two debugging exercises where a small piece of code was given and I had to find and fix the bug; one was a wrong loop boundary and the other was a wrong comparison in a sort. After that came the two coding problems. The first was an array question I solved with a hashmap fairly quickly. The second was a medium-level problem on strings and I passed all the test cases after one fix. I finished with a few minutes left and submitted. About a week later I got a mail that I had been shortlisted for the interviews.

2. 🔒 2 more rounds — continue this journey in the full kit

1. 🔹

   Resume Shortlisting

   I found the RampUp Hiring Challenge through a post on LinkedIn and applied on the last day of the window. The first stage was just resume shortlisting, so there was nothing to do except wait. I had updated my resume the week before with my two main projects and my internship, and I made sure the skills section matched what the posting asked for. About ten days after applying I got a mail saying I had been shortlisted and that the online assessment would be held on a fixed date the following weekend. The mail had the assessment rules and the duration. I spent the days in between revising core CS subjects and doing a couple of medium problems a day, mostly on hashmaps and graphs, since I had read that earlier rounds of this challenge focused on those. That was the whole first stage — quiet, but a relief to clear.

2. 🔒 2 more rounds — continue this journey in the full kit