My Myntra SDE Interview Experience

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!

Detail | Information
Role: SDE Internship (PPO based on performance)
Hiring: Open Campus via Unstop
College: UPES, Dehradun
Year: 4th Year (Fresher)
Stipend: ₹70,000 per month
Duration: 6 months (Jan – June 2026), Bangalore
PPO CTC: 16 – 18 LPA (based on performance)

Phase 1: Online Assessment (Unstop)
The OA was hosted on Unstop and had a mix of coding + theory:

2 Coding Questions (Easy–Medium)

15–17 MCQs (DBMS, OS, CN, OOPs, Aptitude)

2–3 Debugging MCQs (spot errors or predict output)

I managed to solve both coding questions and most of the MCQs. Debugging was more about basics than trick questions.

Phase 2: Technical Interviews
Both interviews were elimination rounds, held on the same day.

Round 1: DSA Focus (~60 minutes)
This round was purely problem-solving.

Problem 1: Find the unique element in a sorted array with duplicates (only one element appears once, others appear twice).

Problem 2: Another array-based problem.

I first explained my logic, then wrote clean code and discussed the time/space complexity.
Within about an hour, I got a call saying I had cleared Round 1 and should get ready for the next.

Round 2: DSA + Project + Applied Questions (~75 minutes)
This round started with a casual intro and then moved into a discussion on my summer internship project. The interviewer was interested in the design choices, challenges, and why I picked certain technologies.

Then came the problem-solving part:

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 in O(N²) and we discussed edge cases and handling duplicates.

Problem 2: A string manipulation question, testing careful handling of edge cases.

Along with DSA, I was also asked a couple of applied questions related to my personal projects: one about designing a Python automation script, and another around a RAG (Retrieval-Augmented Generation) chatbot. The interviewer kept confirming my approach multiple times, probably to test if I was sure, but I stayed firm and explained 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.

Result: I didn’t receive any official communication after this round. Since it was an open campus drive, my college placement team later informed me that I couldn’t make it through.

Final Thoughts
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 your personal projects inside out. This experience definitely sharpened my preparation, and I walked away more confident for future opportunities.

That was my Myntra interview experience! Hope it helps you in yours.

Comments (5)