At Amazon, the interview lasted 60 minutes and was structured into two main parts: behavioral questions and technical coding. The behavioral section focused on two main questions, with follow-ups to dive deeper into my experiences and decision-making process, following Amazon’s Leadership Principles. The technical portion consisted of one coding problem, where I had to explain my approach, optimize my solution, and discuss edge cases. I prepared using the Blind 75 problem set, which helped me feel confident in solving the problem efficiently. Overall, it was a well-structured interview that tested both problem-solving skills and alignment with Amazon’s work culture.
Interview questions [1]
Question 1
There is only one behavioral question and one technical question.
The interview process was straightforward and friendly. It started with a recruiter screening, followed by a technical interview. The interviewer asked basic coding questions, object-oriented programming concepts, and a few behavioral questions based on Amazon Leadership Principles. The coding problems were not very difficult, and the interviewer was willing to provide hints when needed. Overall, the experience was positive and well organized.
LC top 100 tagged — would recommend doing the top 100 and it is likely you will have question from there — the first 40 mins were behavioral lp, then the technical
The Quick DSA Check: A 20-minute easy question usually means the company treats coding as a baseline filter rather than a tool to stump you. They want to see clean code, good communication, and proper edge-case handling without the stress of a complex puzzle.
The Deep Dive: Spending time on your projects and tech stack allows you to show ownership. Interviewers love to see why you chose a specific technology and how you handle technical trade-offs.
The Behavioral Weight: A full 30 minutes dedicated to behavioral questions means this team deeply cares about culture fit, communication, and how you collaborate under pressure.
