I applied through an employee referral. The process took 3 days. I interviewed at Amazon (Seattle, WA) in Jan 2012
Interview
I first passed two phone interviews, with standard algorithm and design questions, similar to ones posted on GlassDoor. I was flown to Seattle for interviews. The hotel was nice, but breakfast was not included. I interviewed with 9 people, some 1:1, but most 2:1, and one 3:1. Most interview questions can be found on GlassDoor, or are very similar. The final interview was with the "bar raiser", which I basically failed. I also had a hard time with an algorithm efficiency question since the interviewer misunderstood my code. In general, the people were smart and nice. Questions were pretty much the same as posted on this site. The bar raiser asked questions requiring familiarity with implementation of Reliability and Durability within a distributed messaging system architecture. I was surprised to learn that Amazon developers are periodically on call, and even more surprised to learn they can expect to be called when they are! I would say the interview questions were more difficult than average, but it is hard to maintain high energy and mental agility through so many interviews, so I rate the process Very Difficult.
Interview questions [1]
Question 1
How would you find if a list of strings, at least one is a prefix of another?
The recruitment process consisted of several stages:
Online coding – a one-hour session focused on solving programming problems and demonstrating practical coding skills.
Technical meeting – a two-hour in-depth discussion covering system design, problem-solving approach, and technical knowledge relevant to the role.
Soft skills meeting – a 90-minute conversation assessing communication skills, teamwork, and overall cultural fit.
Interview questions [1]
Question 1
describe your current project, most interesting bug and feature.
the most important thing you are proud of.
slide-window algorithm, string parser
The technical round focused on a DSA problem about finding the closest points to the origin, where I was asked to explore multiple approaches like sorting, heaps, and quickselect. It felt straightforward, and I was ready for it thanks to the time I spent on PracHub brushing up on similar questions. The interview also included a behavioral section, but overall, I found the process to be very easy. Happy to say I received an offer, which I gladly accepted!
Interview questions [1]
Question 1
K Closest Points to Origin - given an array of points on the 2D plane and an integer k, return the k closest points to the origin (0,0). Walk through sort-by-distance O(n log n), heap-based O(n log k), and quickselect O(n) average; discuss when to prefer each based on the relationship between n and k.
Tough interview.
The Process: Automated Online Assessment (OA) with 2 coding questions and a system simulation, followed by a 4-round virtual Loop. Every single round started with 20 minutes of intense, behavioral behavioral questions diving into Amazon's Leadership Principles, followed by 25 minutes of technical coding or system design.
Amazon interviews are a test of mental endurance because you have to switch from deep behavioral storytelling straight into complex coding which can be so difficult. I used Apex Interviewer to practice the cognitive context switch. Running through their live-coding workspace helped me ensure my technical communication and architectural structures remained sharp and automatic, even after spending the first half of the interview defending my past project metrics. I fed the practice AI questions I extracted from glassdoor and gothamloop.
In the end, the offer was way lower than I hoped.
Interview questions [1]
Question 1
Design the backend inventory tracking and placement service for a global fulfillment network, ensuring strict transactional consistency across multiple regional warehouses during peak shopping events.
