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

      6 mars 2015
      Employé (anonyme)
      Offre acceptée
      Expérience positive
      Entretien difficile

      Candidature

      J'ai postulé via un établissement d'enseignement supérieur ou universitaire. J'ai passé un entretien chez Amazon

      Entretien

      I applied through my school's job board (JobMine, University of Waterloo). I received an on-site interview in Waterloo on a Wednesday morning. All interviews were done at the Tatham Centre on the University of Waterloo Main Campus. This interview was focused on both - I timed 10 minutes on behavioural / past projects / "talk about yourself", 25 minutes for the coding problem, and another 10 minutes on "do you have any questions for me", all time which I felt I was using well. This first coding question was riveting. (NDA, can't say what they are) I got stuck in some places, but I wrote down the pseudocode, stated my assumptions, got the green light, and started coding. I got stuck in some areas, (since I was using a Java HashMap and its entrySet() method, which I confused with keySet()) but eventually had about 90% of the code done (with test cases written off on the side, and the expected result given my initial pseudocode) before I asked him questions about what his thoughts on Amazon were. I was driving back to Toronto (where I'm from) when I got the call from Amazon for a follow-up "second round" of interviews, of which it would be three back-to-back interviews at a certain time. Since my time schedule was really weirdly limiting (a fault of my own), I took the three earliest ones - 9:00am, 9:45am, and 10:45am (15 minute break between 10:30am - 10:45am). The first interview of "round two" was with a hiring manager. He was quite friendly, and did a great job explaining his role and what his progression was through Amazon as well as Waterloo (all Waterloo interviewers from Amazon are alumni, from what I could tell, and had at least a few years of experience at Amazon under their belts). I talked really in-depth about the last intern project I worked on, and he was really intrigued, so kept probing me on details. Eventually, I'd sketched out the entirety of the systems' design, which I was (mostly) responsible for integrating & implementing. This interview felt really good in my book. The second interview of "round two" was an object-oriented design problem. I felt I was bombing this, but I think I specified what I was thinking and what my goals were at every stage, and never sought to waste time or "pander" to a specific approach. Every time I deviated from what the original assumptions I'd made (that were correct, or at least, not corrected by the interviewer), I would be shepherded back to the correct path (which I felt was bad, since then I'm getting too much guidance, or something). I wrote the required interfaces, designed the classes of objects, as well as their relationships, then wrote pseudocode for the required interface methods, and implemented it. I was able to get through it all and have just under five minutes to spare for questions (40 minute problem!). The third interview of "round two" was an algorithms problem, but phrased in a way that made it seem like implementation was important. As usual, I set up and framed the question, solving the ambiguities where necessary, and began to design approaches to solving the problem. The only issue was, none of them worked. At each of the instances I suggested something, the interviewer would question them, which would make me clarify assumptions, which would invalidate that approach. We approached the 20 minute mark before I believed that I had come up with something relatively reasonable, until I was about to implement it and realized it was inefficient, which the interviewer noted "good work". It took another ten minutes to reason out a solution that also looked viable, until he gave me a suggestion to spark a data structure that would work perfectly (it was a heap). I didn't have enough time to finish the implementation (pseudocode and test cases checked out), but the interviewer explained that he was looking at the way I approached problems, rather than what the code was supposed to look like. And that was it for my interviews. I left the TC at 11:30am really scared of what would happen. I was really (silently) self-critical when in the interviews, and I was fearful that it either showed, or that I had failed. One went decent (first), one went "ok" (last), and one went "oh man why did i do that" (second, but i guess the interviewer didn't think so?). I got an email roughly two weeks later extending me an offer; it was the happiest day of my life so far.

      Questions d'entretien [2]

      Question 1

      What was your most favourite project that you worked on, and what was your role in that project?
      Répondre à cette question

      Question 2

      Design a library system for checking out and checking in items.
      Répondre à cette question

      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

      Entretien pour Software Development Engineer

      28 juin 2026
      Candidat à l'entretien anonyme
      Santa Clara, CA
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez Amazon (Santa Clara, CA) en juin 2026

      Entretien

      Recruiter reached out and set up an onsite loop after the initial steps. Four back to back rounds in one day. Two coding heavy rounds run by senior engineers, one round with the hiring manager, and one behavioral round with a bar raiser. Mix of leadership principles and data structures throughout. Heard back within a week.

      Questions d'entretien [1]

      Question 1

      Standard BFS grid problem. Given a grid, find the time for all cells to reach a target state where the spread happens one layer at a time. How did you answer: Clarified the constraints, walked through the approach, then coded a clean BFS from all starting points at once. Tracked the number of layers until everything was covered.
      1 réponse