O processo levou 3 semanas. Fui entrevistado pela Amazon (Seattle, WA) em fev. de 2012
Entrevista
Amazon posted an intern offer on my school career website. I submitted my resume, was contact about 2 weeks later to schedule two 45 minute phone interview. First interview I was asked about to describe projects on my resume, then was asked to list off some data structures. Asked to list all the sorting algorithms I could think of (only listed mergesort, quicksort) and then was asked if I knew the runtimes of these. Then was a coding question which I can't remember, something to do with strings. I had to read it aloud back to him. Asked how I could improve it and the runtime. Then asked about object oriented programming and how I would represent a card game and which methods it would need. The interview ended with me asking questions. The second interview was with someone with a heavier Indian accent, he said he was a tester. He asked me the difference between an arraylist and linked list, then to write a program on paper, I cant remember what it was exactly. I was then asked how I would test the program and if there were bugs how I would deal with them. Then asked about polymorphism and inheritance. Interview ended with me asking questions. I was contacted about a week later to schedule a 3rd phone interview and they actually apologized that I had to have one. Had the interview a week later and right off the bat was asked only one programming question. It was how to find a subset in a string. I had to describe the runtime. The interview was only a half hour I believe and it ended with me just talking to the guy, he had been working there for 7 years and knew someone else who had for 13 years. Asked about the pagers, etc. The day after I was offered an acceptance. To tell the truth, I thought I ruined my chance with all interviews. I answered runtimes wrong, and admitted I didn't remember what polymorphism was. So I was very surprised that I had an offer for another interview. I also thought I ruined the 3rd interview because it took em a very long time to figure the answer--and I don't even know if i got the right answer in the end, because the interviewer had to help me. The main key is to EXPLAIN YOURSELF. I said I had difficulty with things, and how I would TRY to program it or fix it and just talked it out while I was writing it. It really helps to show how you think ,which I guess they liked in my case!
The assessment consisted of three parts and took approximately four hours in total. The first was a LeetCode-style coding challenge focused on applying the prefix sum technique. The second involved being given a full codebase — both frontend and backend — and tasked with identifying and fixing bugs such as broken search/filter functionality and incorrect URL redirects; an AI tool was available throughout, though it only provided guidance rather than direct solutions. The third was a behavioral assessment where I was presented with realistic workplace scenarios, including sample work emails, and asked to evaluate hypothetical responses by rating their appropriateness and explaining my reasoning.
Perguntas de entrevista [2]
Pergunta 1
Given an array of integers, use the prefix sum technique to solve [specific problem type, e.g. range sum queries / subarray sum]
You are given a full web application codebase (frontend and backend). Identify and fix bugs including broken search/filter functionality and incorrect URL routing, using an AI assistant for guidance only.
Candidatei-me online. Fui entrevistado pela Amazon (Bellevue, WA) em fev. de 2026
Entrevista
Applied in Sep 2025.
Online Assessment in Nov 2025. 2 coding questions. one medium one hard. followed by a bunch of behavioral questions.
Virtual Interview in Feb 2026. 2 rounds 1 hour each. continuous one after the other for 2 hours.
It was a great interview experience. very structured. before each round started, interviewer informed me about what would follow. first half leadership principle and then coding or vice versa.
round 1: engineer -> 3 amazon leadership principle based questions, followed by coding
round 2: hiring manager -> coding followed by 3 leadership principle (LP) questions.
Perguntas de entrevista [1]
Pergunta 1
Round 1: 3 LP questions -> expected very in depth answers based on my past work/projects. simple Low level design. implement few methods for the scenario given. I believe handling edge cases, choosing the right data structure, and the right class or object structure was important. These decisions simplified operations, and reduced time complexity of operations. Interviewer nudged me towards a couple of edge cases/ miss in code. expected optimal operations wrt time complexity. asked about my choice of data structure and class structure. interview overshot scheduled time by 10 mins.
round 2: course schedule II (topological sort) - leetcode - worded as amazon based system. expected optimal solution. followed by 3 LP questions - simpler than round 1 and depth of answers required was also lower. interview overshot scheduled time by 5 mins.
Candidatei-me online. Fiz uma entrevista na empresa Amazon.
Entrevista
Single hour interview fully technical. LeetCode medium question very similar to LRU Cache. Follow-up questions on run time and space time complexity are asked. Behavioral questions are also possible, though not guaranteed to be asked.
Perguntas de entrevista [1]
Pergunta 1
Design a class to track the last 10 files processed in a file system.
