J'ai postulé via une autre source. Le processus a pris 2 semaines. J'ai passé un entretien chez Amazon (Seattle, WA) en mars 2011
Entretien
Post resume online and an Amazon recruiter contacted me. Two phone interviews. Got rejection message from the recruiter two days after the 2nd interview. Asked to write code to reverse a string and search a substr. Asked algorithm to produce power set. Did not do well on the second interview since I forgot the formula to calculate combination and slow to react to interviewer's hint to get the answer. Also did not communicate well enough as I was thinking hard. I rated the difficulty level as average because the algorithms would be easy for people freshly out of college. Asked some generak OO design questions about 1. designing a parking lot and 2. components to handle orders. Interviewers seemed to be professional and smart. Thought I did well enough to make it thru the 2nd round but... I thanked the inverviewer after the interview both times but never contacted the recruiter. Not sure if they liked that. Never showed enthusiasm at all during the interview process as I was sure Amazon is not a right place for me. I accepted the interview just to find out what their culture is. Not worth it. No regret at all.
Questions d'entretien [1]
Question 1
Algorithm to produce the power set of a given set.
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.
Questions d'entretien [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!
Questions d'entretien [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.
Questions d'entretien [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.