Software Engineer applicants have rated the interview process at Amazon with 3.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 67% positive. To compare, the company-average is 61.5% positive. This is according to Glassdoor user ratings.
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 1 day. I interviewed at Amazon (Bengaluru) in Mar 2022
Interview
In first round we were asked to write down code for stack in C++. After that for the shortlisted candidates from first round second round was conducted. Questions asked about on designing the software. Kind of HLD LLD questions. I was asked about designing the chess game.
Interview questions [1]
Question 1
How you will design chess game and write code for stack in C++.
I applied online. The process took 4 weeks. I interviewed at Amazon (Toronto, ON) in Jun 2025
Interview
Online assessment 1.5 hours. 2 coding + multiple choices for behaviour
Onsite 4 * 1 hour. Each has 30 min behaviour questions
System Design: an app that you can check in a location
Data Structure: design a class in memory to select seats for a flight
Coding:
deep copy an undirected graph
return all anagrams in a list. follow up: what if the words only contain A, C, I, G
Interview questions [1]
Question 1
project with tight dealine
project help others
mistakes made
I applied online. The process took 2 weeks. I interviewed at Amazon (Ammanabole) in May 2025
Interview
The interview process at Amazon was structured and challenging. It started with an online assessment focused on data structures and algorithms, followed by two technical interviews covering problem-solving, system design, and behavioral questions rooted in Amazon’s Leadership Principles. Communication and clarity were key. The process was intense but fair, and the interviewers were professional throughout.
Interview questions [1]
Question 1
One standout question was: “Design a scalable URL shortening service like bit.ly.” They wanted me to discuss trade-offs, database choices, hashing strategies, and how I’d handle high traffic.