Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo
      employer logo
      employer logo

      Amazon

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Amazon | Offres d’emploi chez Amazon | Salaires chez Amazon | Avantages sociaux chez Amazon
      Entretiens chez AmazonEntretiens d’embauche pour Software Development Engineer III/Senior Engineer chez AmazonEntretien chez Amazon


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Glassdoor LLC. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Glassdoor LLC.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour Software Development Engineer III/Senior Engineer

      21 mai 2014
      Candidat à l'entretien anonyme
      Seattle, WA

      Autres retours d’entretien d’embauche pour un poste comme Software Development Engineer III/Senior Engineer chez Amazon

      Entretien pour Software Development Engineer III/Senior Engineer

      13 mai 2014
      Employé (anonyme)
      Seattle, WA
      Offre acceptée
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 2 mois. J'ai passé un entretien chez Amazon (Seattle, WA) en févr. 2014

      Entretien

      I was contacted through LinkedIn by the AWS Mobile division, as I had stated in my profile that I had been developing SDKs for mobile applications. The whole process lasted two months and Amazon HR were extremely helpful and straightforward throughout. The first steps were a couple of Skype interviews and a CV profiling, which took a week. After that, they announced they were going on a recruiting trip to Barcelona, in the same dates as the Mobile World Congress. They offered to pay for all expenses, including plane, taxi and hotel, so I could make it to Barcelona for the personal interviews. Personal interviews were at the same time interesting and puzzling. They set up shop in a touristic apartment building, and interviewed 4 candidates each morning. Each candidate was shown a room and stayed there while the interviewers were rotating. Interview slasted one hour and were half technical (simple problem resolution) and half personal (predefined questions and general chatting). The technical part was quite easy: pen and paper exercises writing algorightms for tree traversing, sorting, parsing HTML, and such. Interviewers were specially interested in knowing the order of magnitude of my solutions and if I could devise some ways to optimize them without the limitations of a pen and paper test. On the other hand, the personal questions were a stopper. For starters, the interviewers were developers just like me, not HR people and not even managers. They weren't used to asking those kind of questions and it showed, as they were unable to get the conversation going if I stumbled finding an answer or simply understanding the question. That was a bummer, because once we put aside the standard questions and started chatting about what they did in Amazon, and more technical details, it was really fun and interesting. Personal questions didn't allow me to speak about myself in a freely manner, so I had to use those 15 minutes between interviews to pass along some tips about my strong points. The standard personal questions they had to ask (and write down the answers, as they really didn't have the means, nor the interest of expanding on them) were all of the kind: "Tell me about a past experience where you... resolved a conflict with a teammate | provided value for a client | had to deal with a deadline you couldn't meet ...". Those questions were really exhausting, because I had first to understand what they were really asking and what kind of answer was expected. Then, to navigate through my memory to find a suitable experience to tell. And finally, translate it to comprehensible terms, which in the case of a developer often implies a lot of technical context sure to be lost in the transcription. Worst of all, there wasn't any of the more usual questions like "things you do well, things you must improve, what do you want to do in the future, etc." that you may have rehearsed. I was told I would receive an answer after a week, but I didn't. I kept asking by e-mail each week, and always told I was still in the process and a decision had not been made yet. After more than three weeks I was finally told the positions had been covered by other candidates. I reckon I was being kept as a replacement in case some of them didn't accept their offer.

      Questions d'entretien [1]

      Question 1

      I was asked to elaborate about an example of my technical creativity: present the problem to the interviewer and delineate the solution in quite a detailed way.
      1 réponse
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 2 mois. J'ai passé un entretien chez Amazon (Seattle, WA)

      Entretien

      I have initiated communicated with recruiter via linkedIn. On next day the first phone interview has been scheduled. At total, during next 2 weeks had 4 phone interviews. After last one i have been invited to fly to Seattle for one day on site interview. The overall experience is very positive. The recruiters works very fast, waited no more for 2 days to get result from phone interview. The onsite interview I did on Friday and next Tue afternoon I got a job offer.

      Questions d'entretien [1]

      Question 1

      The technical questions was very interesting but nothing not expected. Cannot share more information, since has been asked not to publish it.
      Répondre à cette question
      1

      Entretien pour Software Development Engineer III/Senior Engineer

      7 juin 2014
      Employé (anonyme)
      Palo Alto, CA
      Offre acceptée
      Expérience positive
      Entretien difficile

      Candidature

      J'ai postulé via une autre source. Le processus a pris 2 semaines. J'ai passé un entretien chez Amazon (Palo Alto, CA) en mars 2014

      Entretien

      2 phone interviews followed by one written exam and onsite interview. Most of the questions are around algorithm and data structures. Look for trees and hash tables and distributed designs
      6

      Entretien pour Software Development Engineer III/Senior Engineer

      29 mars 2014
      Candidat à l'entretien anonyme
      Cambridge, MA
      Aucune offre
      Expérience neutre
      Entretien difficile

      Candidature

      J'ai postulé via une autre source. Le processus a pris 3 semaines. J'ai passé un entretien chez Amazon (Cambridge, MA) en févr. 2014

      Entretien

      Reached out to Amazon Recruiter via LinkedIn. The Recruiter responded very quickly. After a Phone screen by the recruiter, got scheduled for a local Hiring-event in Cambridge. The interview was a typical 4-hour long event. 5 different sets of people, each chatting for about 45mins. I did 4 of the 5 okay...took a little longer to come up with the answer they were looking for in one case. Oh well...

      Questions d'entretien [1]

      Question 1

      Write a program to generate a "Unique Ticket" for each request. The number of requests could be quite large - up to a million per second.
      Répondre à cette question
      4