Candidatei-me online. O processo levou 7 semanas. Fui entrevistado pela Amazon em mar. de 2011
Entrevista
While the Seattle Times says Amazon is hiring a lot of people, I sure didn't see it in the attitudes of my interviewers. My experience consisted of two phone interviews spread out over almost two months from when I first applied.
The first interview consisted of questions about my management experience. Typical questions given to a front line manager (well below my level, but I played along) which included:
* Describe a time you had to fire an employee
* How many employees have you managed at one time?
* How have you helped your employees who have performance issues?
The interview was very one way. I never got a clue about the position, environment or if I might fit in.
The second interview consisted of a number of technical questions about performance and scaling issues present in their massive web server farm. While I have no experience in this, and was very up front about that, the questioning continued. The interviewer let me know that this is the Most Difficult Problem in all of computing history, and only those who are dedicated to solving it could be considered worthy of Amazon. Now I like my devs to have pride in what they do, but this was arrogant and turned me off to the Amazon Culture.
Two weeks after the second interview, I was sent a very brief form letter from the junior recruiter who had been walking me through the interview process.
Phone screen, 5 1 hour interviews for loop
Each hour was dedicated to 2 LPs. System design was more collaborative than i anticipated which was a pleasant surprise. The phone screen mostly focused on my previous experiences
Perguntas de entrevista [1]
Pergunta 1
Standard LP based scenarios, system design was actual system the team owns
Candidatei-me por indicação de um funcionário. O processo levou 2 semanas. Fui entrevistado pela Amazon (Tóquio) em fev. de 2026
Entrevista
The interview process is straightforward but intense.
First interview was with another Software Dev Manager in the same team. After that the famous loop interview where I had to take 5 interviews in a row over two days ( using paid holidays at work ). Recruiter gave a lot of information about possible questions and helped with materials. However, I had to use same stories few times as the different interviewers asked same questions few times.
Everything is okay, I had a good time during the interviews and it was a good exercise. However, I simply do not understand why they have to call to reject? I am not a customer to be obsessed with. A straight cut rejection via email works better than taking time out of my busy schedule.
If they used this time to share some feedback, that would be useful. If they do not share any reason why I have to continue formal small talk just to get the rejection on my face?
Perguntas de entrevista [1]
Pergunta 1
A time you were driving toward a goal and realized more than halfway in that it may not be the best goal.
Had 1 round of System design interview. I thought the interview went ok, if not bad, it went decently well. Received a rejection response, while asking to apply 6 months later.
