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 Director of Software Development 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 Director of Software Development

      29 oct. 2020
      Candidat à l'entretien anonyme
      Seattle, WA
      Aucune offre
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. J'ai passé un entretien chez Amazon (Seattle, WA) en nov. 2016

      Entretien

      I was contacted by a recruiter from AWS. They had a few questions for me and wanted to have me meet over the phone with someone in the same department. Schedule a time and met with another Director of Software Development. I passed the questions and was offered to meet in person in Seattle WA. Met with people all day, it really is an all day interview, even at lunch. Left feeling pretty good I gave it my best.

      Questions d'entretien [2]

      Question 1

      Describe the boot process of a desktop computer.
      1 réponse

      Question 2

      How many linux processes can run on a single server.
      1 réponse

      Autres retours d’entretien d’embauche pour un poste comme Director of Software Development chez Amazon

      Entretien pour Director of Software Development

      30 oct. 2022
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 6 semaines. J'ai passé un entretien chez Amazon en oct. 2022

      Entretien

      The recruiter and recruiting process seemed well-organized in terms of scheduling and being accommodating to my schedule. I had watched a few Amazon-focused interview prep videos and received some tips from colleagues who had interviewed at Amazon. Interestingly, my experience did not match the kind of interview that I was expecting from watching those videos. The interview questions that I was asked seemed incredibly shallow. There were actually no hypothetical problem solving questions at all, no questions on system design or organizational design, which is what I would expect in a technical director level role at Amazon. Half of the interviewers wanted to drill down into in my employment history, asking probing questions that seemed like they were trying to fit squares into round holes. Using the STAR format works to a certain extent to describe how one approached a scenario in the past, but it does little to give signal on how someone draws from multiple experiences to solve problems they haven’t seen before in the future. I thought about the caliber of interview questions I expected from the technology leaders in my own org, and these were nowhere close. A few of the questions I was asked have probably been in the “bad interview questions” list for a good 10 years or more. I had never considered interviewing at Amazon before because of what I had heard through the grapevine from colleagues and really only did it because the recruiter was persistent and seemed like a kind person. I regretted putting myself through it after the last interviewer seemed to talk down to me from the start of our interview. At the end, the recruiter sent an overcompensating, infantilizing email talking about how positive it was but that they are going in a different direction and that they’d be open to considering me for a NON-TECHNICAL role. It was bad form all around.

      Questions d'entretien [2]

      Question 1

      What is your favorite metric?
      Répondre à cette question

      Question 2

      What’s the biggest thing you’ve worked on?
      Répondre à cette question

      Entretien pour Director, Software Development

      27 mai 2013
      Employé (anonyme)
      Seattle, WA
      Offre acceptée
      Expérience positive
      Entretien difficile

      Candidature

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

      Entretien

      I was referred by an amazon employee. After 3 rounds of phone interviews, they invited me to onsite interviews in Seattle. Onsite interview loop was 7 people including HR. The interviews consisted of computer science questions, fun puzzles, logical and business reasoning, business strategy and experience questions. They contacted me after couple of days later after the onsite interview and offered the job.

      Questions d'entretien [1]

      Question 1

      Software architecture questions (when there were no right answers) and the interviewer struggled to prove his answer was the right one.
      Répondre à cette question
      4