Candidatei-me por meio de recrutador(a). O processo levou 2 meses. Fui entrevistado pela Amazon (Seattle, WA) em set. de 2010
Entrevista
The process took so long not due to Amazon but because of my own scheduling constraints. I was first contacted early July, and had the first phone interview late July. The second phone interview was also late July. Then the on-site interview was at the beginning of September. About a week after the on-site interview they contacted me with their offer.
First the interview was for a position in the transaction risk management group (what the recruiter found me for), but then also for a position in the global fulfillment platform group. The second position was referred to me by a friend at Amazon because he knew the manager of the group. My first phone interview was with the first team, my second phone interview was with the second team, and for my on-site I talked with the first team in the morning and the second team in the afternoon. The on-site interview was spread out between two of Amazon's Seattle offices. Once everyone moves to the new South Lake Union office this thankfully shouldn't happen any more -- it's pretty annoying, especially when the interviewers don't really know the shuttle schedule that well and you miss the right shuttle!
On-site interviews consisted of one engineer from each team, the manager for each team, some engineers from other teams, and one architect that was working with multiple teams. I think the architect was probably the "bar-raiser" but really his questions were not any more difficult than the others. He did not seem as easy to get along with though which made it more stressful.
Perguntas de entrevista [3]
Pergunta 1
Given an ordered circular array of integers, find an element. Meaning the array is ordered, but the lowest element is not at the first index.
Example: array is [5,6,8,10,1,2,4]
Design a system for counting how many times an item is clicked on. You need to record clicks and be able to report how many clicks for a given item. Be able to report which items are the most popular. Keep in mind scalability, since this is Amazon we're talking about.
Design a system using only standard PCs for load balancing. No load-balancers allowed. Want speed, scalability, reliability, standardized configuration for all nodes.
It started with an OA, and then after a few weeks, I got invited to four rounds of interviews: technical and behavioral at 3 of the 4, and behavioral only at one.
The whole process stretched over nearly a month, longer than I anticipated. After an initial phone screen, I faced a technical round that included a Min Stack implementation question. We discussed design considerations and thread safety, which threw me for a bit. Fortunately, I remembered a specific mock interview I practiced on PracHub that mirrored this scenario closely, making me feel more at ease. Ultimately, I received an offer, but I chose to decline due to the company culture not feeling like the right fit.
Candidatura
Fiz uma entrevista na empresa Amazon (São Paulo, SP).
Entrevista
Um teste de código online, se aprovado, vai para o loop. O loop é 4 entrevistas seguidas, duas em inglês e duas em português. 3 entrevistas técnicas de código, todas as 4 têm pergunta de liderança.
Perguntas de entrevista [1]
Pergunta 1
Pergunta historicas baseada nos principios de lideranca da amazon.