I applied through a recruiter. The process took 1 day. I interviewed at Amazon (Boston, MA) in Dec 2011
Interview
This was a recruiting drive. I was contacted by email and asked if I wanted to participate in a recruiting drive in Boston. I had 4 hour long interviews one right after the other at a hotel. Amazon had rented out a suit of conference rooms for the event. The interviewers were pleasant, and seem to have a set of questions (or types of question) that they asked. Each interviewer seem to focus on different things. The interview process was very STAR (situation, task, action, result) oriented. Look this up in the web, it's worth it.
After the question, you were given a problem to work on. The problems are not difficult, just take your time and talk it out. Talking through the problem is really important since it can save you from going down the wrong path.
Interview questions [1]
Question 1
There was nothing especially difficult. I'm not allowed to discuss the specific problems but I will give some general answers. There were a couple of cute problems, but mainly the problems were related to searching some space. I had 2 problems that required breadth first searches. A problem which looked more difficult than it was. This is probably the hardest type of problem, because it requires that you think about it and play with it until you see the simple solution. Think out loud, this is important.
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.
Interview questions [1]
Question 1
Most coding questions were LeetCode Medium. Common themes: graphs, heaps, sliding window, hashmaps, and LRU/design., system design,
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.
I applied through college or university. I interviewed at Amazon (Dublín, Dublín)
Interview
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.
Interview questions [1]
Question 1
Technical assessment so a basic leet code style question about reversing the orders of long numerical strings.
