I applied through a recruiter. The process took 6 weeks. I interviewed at Amazon (Seattle, WA) in Oct 2011
Interview
3 Phone Screens + 1 in-house interview day
First phone screen: Development Manager position. I felt like I did good enough to warrant further consideration, but I knew I wasn't likely the best software manager candidate they ever interviewed. Interviewer was professional and friendly. He indicated there would be more screening.
Second phone screen: Senior Development Manager position. Interviewer was a very senior director level manager of a large organization within Amazon. When answering questions about about project scheduling and live site issues, I failed to realize that Amazon's highest priority is keeping their existing services working perfectly and that trumps any new development. If I had recognized that part of their business before the call, I may have given more impressive answers.
Third phone screen: Software engineering (individual contributor position). This was a very comfortable interview for me. Mostly all technical and programming questions. I knew I had done well when I got off the phone.
Between each phone screen, a few weeks would go by without hearing anything. I would wait at least a week and then politely email the recruiter about next steps. Each time, the recruiter would apologize for the delay and setup the next phase (which would usually be for the subsequent week). Treat those Amazon recruiters nicely - Amazon is going through a huge growth spurt right now and their recruiters have way too many positions to fill to give anyone individual attention. So if you get anxious, wait at least a week, and send very short and professional mails to the recruiters asking about next steps. They are good about following up to any email you send within a few days.
In person interview: 6 hours of interviews. This included 4 separate hour-long interviews of coding and design problems on the white board. I felt like I did very well.
Interview questions [1]
Question 1
I won't give away the questions asked, as that would violate the NDA I signed. (Because I might actually want to work there some time down the road...)
But I will say this: Almost every coding and design question asked has been posted on Glassdoor. While I am a very experience programmer, I recognized long before the interview process, that I would need to put in some long hours preparing for this company. I spent a lot of time spent refreshing myself on data structures and applying that to problem solving. I went through like fifty Amazon programming questions posted here. I copied each one down, and made a note of the number of times an equivalent variation of that question was posted. Then I made sure I could solve each one with my own code. Extra attention given to the problems posted multiple times.
Prior to my interview, I had heard from many friends who interviewed at Amazon that they were asked at least one question involving a hash table. Amazon is famous for asking questions about hash tables. Either they ask about the hash table constructs in various programming languages (like Java and Perl, hash vs. map, etc..), or a coding problem where the hash table affords an O(N) or O(1) solution. So if you are asked a question that involves looking up a value in one array and searching for a corresponding value in the same or other array - the answer likely involves "use a hash table".
Also, Amazon quizzes candidates on their ability to recognize runtime ordering of the coding solutions. So know your "big-O" notation (e.g. O(N), O(N lg N), polynomial, exponential, etc...)
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 (Dublino, Dublino)
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.
