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

      21 janv. 2012
      Candidat à l'entretien anonyme
      Seattle, WA
      Aucune offre
      Expérience positive
      Entretien facile

      Candidature

      J'ai postulé en ligne. Le processus a pris 1 jour. J'ai passé un entretien chez Amazon (Seattle, WA) en déc. 2011

      Entretien

      Applied online and got call immediately after 5 days. Given 2 date to choose for an onsite interview in Seattle. They took care of almost everything travel-stay-food. I had 15 days to prepare for interview. The day started with lunch at start then 4 interview one by one continuously by different people, I was bit impressed by all. They all started with inquiring about my work experience, why amazon, most interesting or recent projects, etc. Interview tech. questions were not hard to understand but requires lot of thinking and to come up with best solution in terms of space-time complexities, they more concentrated on using best suited data structure for given problem and algorithm to solve it. Also, they check if you considered all cases. They keep on noting everything you say and things you write on board. Less time and detailed thinking of problem is a big pain, you have to stress your brain for next 4 hours nonstop. I was able to answer all tech questions with best solution and they were all very impressed by my solutions, it showed on their face, I met there expectations, but I m sure I messed up Object-oriented question, I was bit disappointed for solution I gave, when I thought about it after coming at hotel, I come with composite design pattern that best suited and was expected. I didn't at all think about any design pattern for object oriented question, I m sure this was the point where I was out. My advice before going for interview is to go through 2 books: programming interviews exposed and cracking the coding interviews.

      Questions d'entretien [3]

      Question 1

      Distribute numbers starting from 1 to infinite, give out minimum number available and take in already given numbers.
      1 réponse

      Question 2

      Words representation of number.
      1 réponse

      Question 3

      Design File system
      Répondre à cette question

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

      Entretien pour Software Engineer

      30 juin 2026
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Amazon

      Entretien

      Interviewed for silicon team. Have only been asked about the domain specific knowledge in 1st round and system design in 2nd round and C coding in 3rd round. The interviews were 50 mins each.

      Questions d'entretien [1]

      Question 1

      Difference between igpu and dgpu
      Répondre à cette question

      Entretien pour Software Engineer

      30 juin 2026
      Candidat à l'entretien anonyme
      Toronto, ON
      Offre refusée
      Expérience positive
      Entretien facile

      Candidature

      J'ai passé un entretien chez Amazon (Toronto, ON)

      Entretien

      First round with hr screening - 2 leetcode questions then hr manager screening then the loop which consists of 4 interviews each an hour long. The 4 interview questions they asked where three medium leetcode questions. And one system design interview question about how to shadow deploy a test software to millions of users.

      Questions d'entretien [1]

      Question 1

      What projects did you work on
      Répondre à cette question

      Entretien pour Software Engineer

      28 juin 2026
      Candidat à l'entretien anonyme
      Offre refusée
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Amazon

      Entretien

      The phone screen went longer than expected, focusing heavily on implementation details. The interviewer really grilled me on my approach to a Least Recently Used (LRU) cache, asking how I'd combine a hashmap with a doubly linked list. I felt well-prepared since I had gone through system design examples on PracHub, which made me comfortable discussing eviction policies. The later rounds included more technical questions and behavioral interviews, but in the end, I received an offer, though I ultimately decided to decline. Overall, I’d say the process was average, with solid questions.

      Questions d'entretien [1]

      Question 1

      Design and implement a Least Recently Used (LRU) cache supporting get(key) and put(key, value) in O(1) average time. Walk through combining a hashmap with a doubly linked list, eviction policy when capacity is exceeded, and how you'd extend it to handle thread-safe concurrent access.
      Répondre à cette question