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.