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 63% positive. To compare, the company-average is 67.2% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 50 days to get hired, when considering 19 user submitted interviews for this role. To compare, the hiring process at Amazon overall takes an average of 33 days.
Common stages of the interview process at Amazon as a Software Engineer according to 19 Glassdoor interviews include:
Skills test: 33%
Phone interview: 27%
One on one interview: 20%
Personality test: 7%
Other: 7%
IQ intelligence test: 7%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 6 months. I interviewed at Amazon (Dresden) in Apr 2024
Interview
Quite possibly the worst interview process I’ve ever seen. I applied in March and got an OA in April. I completed both questions on the OA and all test cases. They said I’d hear back “soon”. Fast forward to September, I’ve completely forgotten I even interviewed there and I get invited to a final round(panel). They give me the days it would be held and I gave them my availability. They then said it had to be rescheduled because of “business issues”. I’ve tried to reach out to the recruiter 3+ times but they are out of office. Today my application got moved to “no longer considered”. Idk if I did something or if they just gave up on the position.
Interview questions [1]
Question 1
Leetcode easy-medium idk cuz it was like 5 months ago at this point.
Recruiter screen, online assessment, technical interviews, and behavioral rounds focused heavily on Amazon Leadership Principles. The process was structured, with a strong emphasis on problem-solving, coding skills, and examples demonstrating impact and ownership.
Recruiter screen, followed by an online coding assessment and then a technical phone interview. The final round was a virtual onsite loop with multiple interviews covering data structures, system design, debugging, and Amazon Leadership Principles. The technical questions were practical but time-constrained, and the behavioural questions required specific examples using the STAR format.
Interview questions [1]
Question 1
Design a scalable URL shortening service and explain how you would handle high read traffic, collisions, database schema, expiration, and basic monitoring.
That moment when the interviewer asked about finding indices in an array for a target sum was wild — I had just tackled something identical while prepping on PracHub. The interview included a technical round with another question about designing an in-memory LRU cache and a behavioral question about meeting tight deadlines. After a smooth discussion, I was told I'd received an offer, which I happily accepted. Overall, the process felt pretty straightforward and not overly challenging.
Interview questions [3]
Question 1
Given an array of integers return the indices of two numbers summing to a target