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 I 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 I

      21 déc. 2014
      Employé (anonyme)
      Offre acceptée
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 1 semaine. J'ai passé un entretien chez Amazon en nov. 2014

      Entretien

      I was first contacted by an Amazon recruiter via LinkedIn. I was kind of hesitant to interview with them, since I had been rejected by them in the past. But I spoke to a manager -- I liked the stuff his team was working on, and I decided to give it another shot. The first interview was on the phone with this manager. It was behavioral in nature, but still technical. What I mean by this is that the questions all started off as "Tell me about a time when..." and finished with detailed questions about the code behind my solutions. I don't personally think what I said was THAT cool, but I must know how to sell it because I got a request for an online test and onsite interview the next day. The test was actually really hard! Maybe if I was halfway through an undergrad junior level algorithms course, it would have gone easier. But I wasn't. So I did what I could, commented on what I couldn't, and left some notes about how I would approach the problems given more time. Anyway, on to the on site interview! The interviewers were very nice, they made me feel right at home. I was asked a little bit about what kind of code I worked on at my current job and what working at Amazon would be like. I knew going in that Amazon had a reputation for being a bit of a sweat shop, but going through a bit of a workaholic phase in my life, I didn't really mind. For the most part, the questions were technical. I was given some questions on trees, graphs, distributed systems, and object oriented design. They were fairly standard questions, with slight twists as followups. Basically they'd give me a standard question and I'd give them a standard answer. Then they'd grin and change the question and make it significantly harder. Then I'd struggle, get nervous, take a deep breath and calm myself, and work through it and get to the correct answer. Being calm is just as important as having strong technical prowess in these interviews. This was a big challenge for me when I was graduating college. I got interviews from all the big tech companies: Amazon, Microsoft, Apple, Facebook, and Google. And I failed every single one of them even though the the questions were surprisingly doable, because I couldn't control my nerves. I secretly had an anxiety and panic disorder back then, so this was easier said than done.

      Questions d'entretien [1]

      Question 1

      Very standard questions. Print a family tree. BFS in a graph. Some design questions.
      Répondre à cette question
      10

      Autres retours d’entretien d’embauche pour un poste comme Software Development Engineer I 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