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

      24 oct. 2014
      Candidat à l'entretien anonyme
      Seattle, WA
      Aucune offre
      Expérience négative
      Entretien difficile

      Candidature

      J'ai postulé via une autre source. Le processus a pris 4 semaines. J'ai passé un entretien chez Amazon (Seattle, WA) en sept. 2014

      Entretien

      I got an email out of the blue asking me if I wanted to fly to Seattle and interview. I still don't know where they got my resume; but I assume it was from when I applied for a co-op position a year before. I was excited to go, but from the very start I got the impression it was going to be tough. I got an email about a week beforehand with about 8 attachments containing literature about the company. I was informed that I would be doing a programming problem for most of the day, and I would have my choice of language, compiler, and OS. When I arrived on campus, we were given visitor badges and told to wait until someone came to get us. I felt weird that the majority (at least 75%) of interviewees were foreign students. It made me feel like I was out of my league. We were taken upstairs to a conference room where HR gave a speech about how great the company is. We were then assigned to a table, and given a laptop and packet describing the programming challenge. The challenge was supposed to be team-based (with the people at your table), but it turned out to be more individual that I anticipated. The problem broke into three pieces, and each person picked a part to do. You didn't have to use the same language. The parts were basically independent, but I could see where sharing code between teammates could be helpful. We were given 6 hours to complete the task. After about half an hour, an engineer came to gauge our understanding of the problem, and clarified anything we didn't know. We then worked for about an hour, and an engineer pulled each of us out for a personal "interview". It was the least personal interview I have ever had. The engineer was all business, and we just talked about my approach to the problem. When I got back, I had about 4 more hours to complete the assignment. Half an hour before the deadline, we were individually interviewed again. Pretty much the same type of thing, just talked about my approach. The interviewers were always interested in efficiency. They asked questions like "how could you make this better/faster", and "why did you use this data structure". I really got bit in the butt because I was forced to use C++, instead of C (which I am much more familiar with). I was unfamiliar with the C++ libraries, and I had to waist a lot of time looking at documentation. BIG TIP: be very familiar with your language before you go! My solution was incomplete, and I knew this when I turned in. I was encouraged to write a README file which explained my shortcomings, and any ideas I had to make the code more efficient. At the end of the interview, we had a group Q&A with a developer. I got the impression that this was a very stressful job with poor work/life balance. I love the area, so if I had gotten an offer it would have been a tough decision weather I was willing to sacrifice a stressful job for my dream city.

      Questions d'entretien [1]

      Question 1

      Questions are covered by a non-disclosure agreement
      Répondre à cette question

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

      Entretien pour Software Development Engineer

      17 juin 2026
      Candidat à l'entretien anonyme
      Offre refusée
      Expérience positive
      Entretien facile

      Candidature

      J'ai passé un entretien chez Amazon

      Entretien

      Surprisingly easy — I expected tougher questions, but the coding round felt more like a warm-up. The main challenge was a DSA problem about counting islands in a 2D grid, which led to a discussion on DFS versus BFS and handling large grids. Funny enough, I had revisited that exact type of question while prepping on PracHub, which made me feel more confident. The interview wrapped up with a behavioral round, and I accepted an offer, but ultimately decided to decline it for another opportunity. Overall, it was a smooth experience.

      Questions d'entretien [1]

      Question 1

      Number of Islands — given a 2D grid of '1's (land) and '0's (water), count the number of connected islands. Walk through DFS vs BFS, and discuss how to avoid revisiting cells (in-place mutation vs visited set) and what changes if the grid is huge and must stream from disk.
      Répondre à cette question

      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