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

      30 août 2013
      Candidat à l'entretien anonyme
      Seattle, WA
      Aucune offre
      Expérience neutre
      Entretien difficile

      Candidature

      J'ai postulé en ligne. Le processus a pris 4 semaines. J'ai passé un entretien chez Amazon (Seattle, WA) en août 2013

      Entretien

      Submitted my resume to their job application website after seeing a listing on a hiring board. Was contacted a couple days later by an enthusiastic recruiter. A day or two after that, the recruiter contacted me again and said that I was up for consideration and would be moving to the next step, online interview questions. After buying a webcam, I visited the interview website, recorded some responses to some general questions (career aspirations, interest in Amazon), then started with the two technical, problem solving questions. After typing, compiling, correcting, and submitting my answers (all via the website), I recorded short descriptions regarding my choice of solution and what my thought process was. After waiting a week to get a response (apparently the manager they tasked to review my responses was sick) they called me and told me they would like to fly me in to Seattle to conduct some 1:1 interviews. I was scheduled for a date 2-weeks out, set up my reservations with the travel agent, and started reviewing different Computer Science topics to refresh myself. Flew in to Seattle, walked to the office building (so I knew where it would be the next day), then settled down to relax before the interview. The day-of, arrived at the building the requested 15-minutes early, signed in at the front desk, and waited 10 minutes for the recruiter. Was escorted upstairs with one additional applicant. I did get a brief look at the office setting. Dress code was casual, there were common-areas and a kitchenette where employees were hanging out and conversing. After a short lunch/meet and greet with the interviewers and another HR staffer, we were split into separate meeting rooms and had 4 1-hour interview sessions. The questions were difficult, but nothing unexpected if you've interviewed at a software-focused company before. The process seemed to go well, but in retrospect I was probably just too stressed to notice any subtle hints from the interviewers that I was not impressing them. The interviewers were nice, asked probing and sometimes guiding questions. They take lots of notes, they are constantly typing your responses, and the code you write, into their laptops. After the interviews, the recruiter told us they'd probably be able to let us know within a couple days. I sent an email after a week, never got any response. I've heard some companies refuse to contact people they don't want to hire out of some sort of lawsuit fears, and apparently Amazon is one of those companies. I did get my travel expense reimbursement, so at least I know the company is still around. The lack of any response was really the only part of the experience that was not friendly. Considering I'm not applying for jobs because I'm bored, I would have appreciated a response of some sort. I don't know how I would have felt if I had lost another job opportunity because I wanted to wait one extra day for them to get back to me. As for the trip: Amazon did not provide a rental car (not that I'd want to drive in downtown Seattle during rush-hour). I should have familiarized myself with public transportation options. The light-rail to the airport to a block from the hotel they reserved for me was less than $3, though I took a $47 taxi ride TO the hotel. If you take a Taxi, make sure to ask the driver for a receipt (and make sure they fill it out to avoid any hassles).

      Questions d'entretien [1]

      Question 1

      Was asked to design a system (from user interface to underlying components and classes) to accommodate a specific customer service business scenario.
      1 réponse
      1

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

      Entretien pour Software Engineer

      19 juin 2026
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Amazon

      Entretien

      Great interview process with three rounds, including a technical assessment and a technical interview. The interviewers were professional and supportive throughout the process. The questions mainly focused on DSA, problem-solving, and core technical concepts. The discussions were engaging and provided a good opportunity to demonstrate technical skills. Overall, the process was well-structured, smooth, transparent, and a very positive experience.

      Questions d'entretien [1]

      Question 1

      DSA type related question and system design
      Répondre à cette question

      Entretien pour Software Engineer

      19 juin 2026
      Candidat à l'entretien anonyme
      Dublin, Dublin
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

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

      Entretien

      Online techincal assessment. Had to screen share and complete basic coding tasks similar to Leet Code. Could choose a language of your choice. Overall a very fair system and judged based on merit.

      Questions d'entretien [1]

      Question 1

      Technical assessment so a basic leet code style question about reversing the orders of long numerical strings.
      Répondre à cette question

      Entretien pour Software Engineer

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

      Candidature

      J'ai passé un entretien chez Amazon

      Entretien

      Loop — 4 rounds, all on the same day Round 1 — Coding (DSA) Interviewer was a senior SDE, very friendly. Warm-up + behavioral: "Tell me about a time you took ownership of something outside your responsibilities." Main question: Given a list of meeting intervals, find the minimum number of conference rooms required. I used a heap. He then asked a follow-up: what if meetings could be reassigned to minimize total idle time? We discussed approaches but didn't fully code it. He cared a lot about how I talked through edge cases out loud. Round 2 — Coding + Problem Solving LP question: "Describe a situation where you disagreed with a teammate." Coding: LRU Cache implementation from scratch. I used a hashmap + doubly linked list. He pushed on thread-safety and what happens at capacity 0. Round 3 — Behavioral (Bar Raiser) This was the toughest round — no coding, all Leadership Principles, very deep STAR-format probing. Questions I got: "Tell me about a time you failed and what you learned." "A time you had to deliver something with a tight deadline and limited information." The bar raiser kept drilling: "What was your specific contribution?" "What would you do differently?" "What data did you use?" Have 6–8 strong stories ready with metrics. Round 4 — Low-Level Design Design: Design a parking lot system (classes, vehicle types, spot allocation, pricing). Then he asked me to code the findSpot() and releaseSpot() methods.

      Questions d'entretien [1]

      Question 1

      Most coding questions were LeetCode Medium. Common themes: graphs, heaps, sliding window, hashmaps, and LRU/design., system design,
      Répondre à cette question