amazon logo
Amazon· SDE II

Amazon India (HYD) SDE2 Interview Experience – Rejected

Result
Rejected
Location
Hyderabad, India
Posted
9 Feb 2025
305 reads

Summary

I interviewed for an SDE2 role at Amazon India (Hyderabad) and was ultimately rejected. The process included an Online Assessment, a Data Structures and Algorithms round featuring 'Word Ladder,' and a Low-Level Design round focused on 'Design Chess.'

How it went

My SDE2 interview experience at Amazon India (Hyderabad) began with an Online Assessment. The OA consisted of two DSA problems, one of which was Linked List-based and straightforward, though I can't recall the second one. There were also behavioral questions based on Amazon's Leadership Principles.

First Round

I joined on time, but the interviewer was 5 minutes late, which was fine by me. This round was split: 30-35 minutes for behavioral questions based on Amazon's Leadership Principles, and 20-25 minutes for a DSA problem – Word Ladder (LeetCode Hard).

I had extensively prepared for Word Ladder, having solved it 11 times over the past 1.5 years. I started with the optimal approach, explaining it in detail, as the interviewer expected production-level code within the 25-minute timeframe. However, the feedback I received stated that I provided an incorrect time complexity, though my double-check later confirmed my analysis was correct. Another concern was that I was in a hurry, but I felt that if the interviewer perceived rushing, they could have guided me.

Second Round

Similarly, I joined this round on time, and the interviewer was again late, which was not an issue for me. This round was also divided: 30-35 minutes for behavioral questions and 25-30 minutes for a Low-Level Design (LLD) problem – Design Chess.

For the LLD, given the time constraints, I structured my approach by first gathering requirements, then defining class names, and finally creating a UML diagram. My UML incorporated key design principles, utilizing the Strategy Pattern for rules and the Factory Pattern for chess pieces. The feedback I got was that I "over-designed" the problem and lacked sufficient experience.

Final Thoughts

I was genuinely shocked to receive the rejection email as I felt this was one of my best interview performances. I've dedicated over a year to preparation and have faced 7-8 rejections from HFTs already. Despite putting immense effort into this Amazon interview, I couldn't clear it. This experience has led me to reflect deeply on what interviewers truly seek.

Questions asked (2)

  1. 01

    Word Ladder

    Data Structures & Algorithms · Hard

    During a 20-25 minute Data Structures and Algorithms segment, I was presented with the 'Word Ladder' problem. This problem is explicitly identified as a LeetCode Hard difficulty. The interviewer expected a production-level code solution within the given time. Post-interview feedback indicated concerns about incorrect time complexity analysis and a perception that I was rushing through the problem-solving process.

  2. 02

    Design Chess

    System Design

    In a 25-30 minute Low-Level Design (LLD) round, I was tasked with designing a Chess system. My approach involved outlining requirements, defining class structures, and then creating a UML diagram. The feedback I received implied that my design might have been overly complex, suggesting an "over-design" and a lack of experience.

How they prepared

I had been preparing for over a year, specifically for companies like Amazon, and had faced numerous rejections from HFTs prior to this. For DSA problems like Word Ladder, I ensured thorough practice, having solved it 11 times over the past 1.5 years. My preparation also involved understanding and applying design principles for LLD problems.

Know someone preparing? Send it to them:WhatsAppLinkedInX

Interviewed at Amazon recently?

Write up your rounds while you still remember the questions. It helps the next person more than you would think.

Share your experience
Discussion 0

Questions for the author, or how your own interview compared.

Join the discussion

Sign in with Google to comment or ask the author a question.

No comments yet

Be the first to share your thoughts and start the discussion!