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 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. Indeed, Inc. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Indeed, Inc.

      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

      12 nov. 2022
      Candidat à l'entretien anonyme
      New York, NY
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 4 semaines. J'ai passé un entretien chez Amazon (New York, NY)

      Entretien

      Initial phone screen, followed by an online assessment and a final round of four interviews. The self-administered, online assessment consisted of two easy to medium algorithmic coding problems (like on HackerRank), systems design scenarios with high-level, relatively easy multiple choice questions, and personality/behavioral questions. The coding and systems design part was nice but I really disliked the personality section. That contained maybe 40 questions with forced choice between two alternative statements at a time. That included no-win pairs like (roughly) "I need to be told what to do in order to work" vs. "Sometimes I work hard, sometimes I hardly work". I really question the scientific validity of this sort of test, including its test-retest reliability. For several questions I answered mostly randomly (because I really wanted to say "neither!" or "both!" but couldn't) and would probably not be able to reproduce my own answers even half an hour later. Passing the online assessment resulted in a final round of four live, online interviews. Three around coding, one systems design. The technical questions were fine and not too hard, except for one that seemed really weird to me. That one related to OO data modelling for a problem that I would never, ever model statically in code, but definitely represent dynamically in a database schema. It's possible that I don't know enough about OO design but several friends I asked were also confused by this question. In addition, about half the time during the online interviews was spent on Amazon's "Leadership Principles", leaving little time for tech. I actually closely identify with several of them but I feel it is almost impossible to accurately represent that with the most recent background being in academia, not customer-focused work in industry. Also, some of the questions get so specific that even with preparation of multiple responses per principle, you might get stuck.

      Questions d'entretien [5]

      Question 1

      Numerical optimization problem with one-dimensional data
      Répondre à cette question

      Question 2

      Graph traversal
      Répondre à cette question

      Question 3

      Log processing algorithm
      Répondre à cette question

      Question 4

      Data modelling (question seemed very weird to me)
      Répondre à cette question

      Question 5

      Systems design question relating to social media user activity
      Répondre à cette question
      1

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

      Entretien pour Software Development Engineer

      3 juin 2026
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience positive
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Amazon

      Entretien

      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.

      Questions d'entretien [1]

      Question 1

      Questions related to leadership principles
      Répondre à cette question

      Entretien pour Software Development Engineer

      23 juin 2026
      Candidat à l'entretien anonyme
      Calgary, AB
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez Amazon (Calgary, AB) en juin 2026

      Entretien

      Online Assessment is the first step in the process. I didn’t have an HR phone screening and went straight to the OA after applying. It was sent to me about a week after I submitted my application.

      Questions d'entretien [1]

      Question 1

      The first question is LeetCode style algorithms question, and the second question gives a full stack repo (choice of Java, NodeJS, or Django) and asks to solve a backend issue which is causing a bug in the frontend. Unit tests must pass to pass the second question. You can run both backend/frontend indivdually or together
      Répondre à cette question