I applied online. The process took 2 months. I interviewed at Amazon (Seattle, WA) in Aug 2010
Interview
It took quite some time (say six weeks) to get a response after I had submitted my resume, and the email came from a recruiter. The phone interview was for a position unrelated to the one for which I had submitted my resume.
Setting up the phone interview took a couple of emails and a phone call, and the software engineer from the team called me precisely on time. He spent about 30 minutes asking me questions and I spent about 20 minutes asking him questions.
The most technical questions were akin to:
* if you had to keep a list of numeric values, how would you search it for all pairs of values which add to a fixed value?
* give a back-of-the-envelope OO (class-level) design for a dictionary system
A respectable amount of time was spent asking me about a technical solution I was proud of or a great technical challenge I had overcome.
Interview questions [2]
Question 1
Show a class-level OO design for a dictionary service to be used by clients passing a complete document in for spell-checking.
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.