Software Engineer applicants have rated the interview process at Amazon with 3.5 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 33% positive. To compare, the company-average is 63.8% positive. This is according to Glassdoor user ratings.
Here are the most commonly searched roles for interview reports -
I applied online. The process took 3 weeks. I interviewed at Amazon
Interview
3 Rounds in total in Interview loop on the same day. 1st was entirely behavioral based on Amazon Principles, 2nd had a medium difficulty graph question. Last round was based on the OOP design question.
Interview questions [1]
Question 1
Solve the graph question by telling them your understanding and though process side by side.
I applied online and heard back from a recruiter after about a week. First, I had to complete an online assessment with coding problems and a work style questionnaire. After passing that, I had a technical phone interview where I solved 1-2 algorithm questions in a shared editor.
Interview questions [1]
Question 1
Tell me about a time you took ownership of a project beyond your role. What was the outcome?
The Amazon SDE 2 interview process rigorously assesses both technical expertise and alignment with Amazon's Leadership Principles (LPs). Throughout the 4–5 round interview loop, each interviewer is assigned 1–2 LPs to evaluate alongside technical questions, meaning LP assessment is woven into every round rather than isolated. One dedicated behavioral round—often led by a hiring manager or Bar Raiser—focuses deeply on LPs like Ownership, Dive Deep, Bias for Action, and Deliver Results. Interviewers ask experience-based questions (e.g., “Tell me about a time you failed”) and expect structured responses using the STAR format (Situation, Task, Action, Result), with emphasis on the candidate's individual role, decision-making, and reflection. For SDE 2 roles, Amazon expects responses to demonstrate initiative, ownership beyond assigned tasks, cross-functional thinking, and an ability to drive long-term outcomes with limited guidance. Follow-up probing is common to test depth, authenticity, and learning mindset. Strong LP performance is as critical as technical correctness—failing to meet the bar on either can result in rejection, regardless of coding skill.
Interview questions [1]
Question 1
Tell me about a time you took ownership of a project outside your responsibility?