J'ai postulé via un recruteur. J'ai passé un entretien chez Amazon (Seattle, WA)
Entretien
Worked very closely with the recruiter over a couple of months to work out a time to visit Seattle for an interview. The recruiter was very capable and showed great passion for finding me a good fit in Amazon. On interview day I met with 5 team members (plus a couple of people just sitting in on the interview) for a total of 45 minutes each. They each spent from 10-20 minutes discussing prior experiences and then gave me a somewhat open-ended coding problem to solve on the whiteboard. Most of them mentioned that the result wasn't important, but was more interested in how I came to the conclusions that I did. During the whiteboarding I got very little feedback on how I was doing (one interviewer was typing vigorously on his laptop the entire time & was either taking a lot of notes or doing work himself). It was very hard to tell if I was going off on a tangent that they weren't interested in or if I was on track. At the end of the day I was happy with all of my solutions & didn't feel like I'd gotten stumped on any of the topics. There was one interview, though, that looking back on I wish I'd done differently. The recruiter mentioned that I could use any programing language that I wanted, but I would suggest to everyone to consider using something that the interviewer is familiar with. In the one questionable interview I used C# along with IEnumerables & LINQ to solve the problem. The interviewer asked a lot of questions on what IEnumerables were & probably thought I'd made up LINQ. At the end of the interview I doubt he had any idea what I had done. In hindsight, I should've used more basic C# or used another language entirely so the interviewer could understand what I was doing.
Questions d'entretien [1]
Question 1
Write a function to calculate build order given a project with a list of dependencies that also need to be built
J'ai postulé en ligne. Le processus a pris 1 semaine. J'ai passé un entretien chez Amazon en avr. 2022
Entretien
Received an email from recruiter, and then an automatic email inviting me to do an Online Assesment. I'm still waiting results , I don't know if they will call me.
Questions d'entretien [1]
Question 1
2 Coding test (90 min max) that are very tricky, you should exercise on HackerRank. and then, 15 Min of Work simulation "responding" (multiple answers) to simulated emails from your or other teams, and a serie of behavioral questions.
J'ai postulé via un recruteur. Le processus a pris 2 semaines. J'ai passé un entretien chez Amazon (Toronto, ON) en avr. 2022
Entretien
A total of four approximately one-hour interviews were conducted on the same day. Three interviews focused on Data Structures and Algorithms, while one focused on System Design. All four interviews start with an introduction, followed by behavioural questions and end with the technical question. The technical part last around 20 - 30 mins.
The DS and Algo questions ranged from easy to medium, depending on your level of preparation. All four technical questions may be tailored to the team, especially the system design question.
J'ai postulé via un recruteur. Le processus a pris 2 semaines. J'ai passé un entretien chez Amazon (Boston, MA) en sept. 2021
Entretien
Interviewed 5 hours after written test. The interviewers follows exact pattern of questions which they prepared for. I would say they need to know what they want to know but not what the candidate knows. Clearly reflects Amazon's dictatorships style of working and that's why people are working like dog there. I will never ever join Amazon with this kind of people
Questions d'entretien [1]
Question 1
Tic Tac Toe. Binary tree relationship between nodes. Kindle design of bookmarks. etc.. apart from this many people management questions like explain difficult situations and how you handle that. Any time you had a conflict with your manager etc