- Équilibre travail/vie privée
- Culture et valeurs
Aucun recrutement à Boston, MA (États-Unis) de Amazon Lab126 actuellement. Consultez tous les emplois Amazon Lab126
Je travaille chez Amazon Lab126 à plein temps
Working with very intelligent people
Working on cutting-edge technology
Work load is sometime overwhelming.
Activez cette page en publiant un photo. Cela ne prend qu'une seconde, et vos photos sont anonymes.Partager une photo
J'ai postulé via un recruteur. Le processus a pris 3 semaines. J'ai passé un entretien à Amazon Lab126 (Boston, MA (États-Unis)) en juin 2020.
TLDR: worst interview process I've ever experienced, I expected better from Amazon
process started when a recruited reached out to me, and set up a phone screen. The recruiter specifically told me that any coding problems could be solved in any common language (python was on the list of common languages). Despite this, on the phone screen the interviewer insisted I write in C, which I've used a good amount in the past but certainly wasn't fresh with. Somehow my weird mix of C syntax mixed with pseudocode and explaining my thought process was enough to be invited to do an on site interview. When the recruiter reached out to me saying they wanted me to do an on site, I mentioned I was surprised given the miscommunication over which languages were acceptable. The recruiter responsed that the interviewer 'really shouldn't have done that' and that they were 'fairly new to interviewing', but assured me going forward using python would be ok. A few days later, a different recruiter reached out to schedule the on site, and I again asked if python was acceptable, and she responded the same way. Given that they wanted to schedule the interview as soon as possible, and I have a full-time job, it didn't seem practical to relearn all of the details of the C language, so I figured I'd stick with python considering the recruiter(s) had said no less than 5-6 times that python was okay. Well the day of the interview came, and 3 out of 4 interviewers asked me to use C. This time I told them the recruiters had assured me python was okay, and 2 of the 3 seemed fine with that, while one of the interviewers clearly made up his mind the second I said anything. To wrap it all up, the last interviewer (who I was actually having a decent, engaging conversation with) essentially hung up on me right when time was up. The cherry on top was the rejection phone call from the recruiter lasted 25 seconds. No feedback, not even a 'sorry it didn't work out'
Questions d'entretien d'embauche