J'ai postulé en ligne. Le processus a pris 2 mois. J'ai passé un entretien chez Amazon en févr. 2012
Entretien
Received three appointments for phone interviews all set up via email, none of them very quick as far as responses. Each interview was 45 minute, the last interview that was set up was a template email sent to my address "Hello [Name] I'd like to set up an interview on [Date]"... that never turned into an interview, and I removed myself from the process because I found a job locally in the mean time (the three interviews were over the course of more than a month). The interviews were all pencil and paper problem solving and programming knowledge. It was a review of technical algorithm and data concepts from school, I would suggest anyone to review their basic programming before the interviews. I watched Stanford's free youtube videos and they helped. Focus on heaps and other data structures and try to remember computational complexity, there is a concern for what is fastest versus slowest in the questions. The interviewers were generally nice, about par for a developer interviewing a developer.
Questions d'entretien [1]
Question 1
I was supposed to make a method that implemented the Fibonacci sequence. I froze up and forgot the actual equation before I stalled and finally stumbled my way through it.
Great interview process with three rounds, including a technical assessment and a technical interview. The interviewers were professional and supportive throughout the process. The questions mainly focused on DSA, problem-solving, and core technical concepts. The discussions were engaging and provided a good opportunity to demonstrate technical skills. Overall, the process was well-structured, smooth, transparent, and a very positive experience.
J'ai postulé via un établissement d'enseignement supérieur ou universitaire. J'ai passé un entretien chez Amazon (Dublin, Dublin)
Entretien
Online techincal assessment. Had to screen share and complete basic coding tasks similar to Leet Code. Could choose a language of your choice. Overall a very fair system and judged based on merit.
Questions d'entretien [1]
Question 1
Technical assessment so a basic leet code style question about reversing the orders of long numerical strings.
Loop — 4 rounds, all on the same day
Round 1 — Coding (DSA)
Interviewer was a senior SDE, very friendly.
Warm-up + behavioral: "Tell me about a time you took ownership of something outside your responsibilities."
Main question: Given a list of meeting intervals, find the minimum number of conference rooms required. I used a heap. He then asked a follow-up: what if meetings could be reassigned to minimize total idle time? We discussed approaches but didn't fully code it.
He cared a lot about how I talked through edge cases out loud.
Round 2 — Coding + Problem Solving
LP question: "Describe a situation where you disagreed with a teammate."
Coding: LRU Cache implementation from scratch. I used a hashmap + doubly linked list. He pushed on thread-safety and what happens at capacity 0.
Round 3 — Behavioral (Bar Raiser)
This was the toughest round — no coding, all Leadership Principles, very deep STAR-format probing.
Questions I got:
"Tell me about a time you failed and what you learned."
"A time you had to deliver something with a tight deadline and limited information."
The bar raiser kept drilling: "What was your specific contribution?" "What would you do differently?" "What data did you use?" Have 6–8 strong stories ready with metrics.
Round 4 — Low-Level Design
Design: Design a parking lot system (classes, vehicle types, spot allocation, pricing). Then he asked me to code the findSpot() and releaseSpot() methods.
Questions d'entretien [1]
Question 1
Most coding questions were LeetCode Medium. Common themes: graphs, heaps, sliding window, hashmaps, and LRU/design., system design,