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 Solutions Architect 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 Solutions Architect

      28 mars 2018
      Candidat à l'entretien anonyme
      San Francisco, CA

      Autres retours d’entretien d’embauche pour un poste comme Solutions Architect chez Amazon

      Entretien pour Solutions Architect

      1 mai 2026
      Candidat à l'entretien anonyme
      Offre refusée
      Expérience positive
      Entretien difficile
      Aucune offre
      Expérience neutre
      Entretien difficile

      Candidature

      J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez Amazon (San Francisco, CA) en mars 2018

      Entretien

      It seems to be quite popular for folks to vent about the AWS SA interview process on GD after the fact, and I did find it difficult and awkward, but not in the ways I was expecting. I only made it to the initial 90 minute phone screen, and did not get selected for the full onsite loop. First off, the good things: 1. Recruitment team were really helpful and professional 2. Overall it is a fair process, and definitely gives you an insight in to how the group operates. 3. Reinforced my belief that you would be joining a high performing team. Not-so-good things: 1. Phone screen with team is done on an awful in-house tele-conferencing line with poor audio. I couldn't always hear what they were saying, and vice versa. This definitely a barrier to proper communication and not in the candidate's favor. Make sure you're in a quiet space with excellent phone hardware :-) 2. I spent lot of hours/days/weeks prepping for the interview, but I spent far too much time on organizing my answers to the behavioral dimension of the expected question set ("Tell me about a time" etc) and not enough on the base AWS capabilities. For the initial tech screen with the hiring team, it is very important to be able to virtually whiteboard (ie, describe) how to build a scalable and secure architecture on AWS. This is on me, my judgement was way off here, and I should have spent more time rehearsing this aspect, and left the 14 principles to the onsite loop (I did get asked 1 or 2 behavioral Q's on my phone screen, but they were almost after-thoughts). 3. There are some open-ended questions centered on industry buzz-words that are, perhaps deliberately, ambiguous, but when pressed for specifics, it seemed the interviewer could not provide actual details. I am not totally sure they always knew exactly what they were asking, and were working from a script. For example, there is a fair few questions about distributed architecture with no actual specifics around scale or business problem. Whether a computing system can be labelled "distributed" is very much in the eye of the beholder, in my experience. Scalability or elasticity does not imply true distribution.

      Questions d'entretien [1]

      Question 1

      How do you write performant Java code?
      3 réponse(s)
      3

      Candidature

      J'ai passé un entretien chez Amazon en mai 2026

      Entretien

      Few rounds of interview, mixed with behavioral and technical questions to showcase you knowledge of building system on aws. They also asked gen ai questions on how you would create these systems
      1

      Entretien pour Solutions Architect

      29 avr. 2026
      Candidat à l'entretien anonyme
      Seattle, WA
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

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

      Entretien

      You do 4 back to back interview in 1 day. It was exhausting. Besides that really appreciated the recruiter giving out interview prep before it takes place. The good thing is there is no coding round.

      Entretien pour Solutions Architect

      23 sept. 2025
      Candidat à l'entretien anonyme
      Berlin
      Aucune offre
      Expérience négative
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Amazon (Berlin)

      Entretien

      The interview process was very challenging and thorough. The questions required deep technical knowledge and problem-solving under pressure. While tough, it was fair and tested real-world skills, communication, and adaptability.

      Questions d'entretien [1]

      Question 1

      Can you walk us through a time you solved a complex problem under tight deadlines, and how you balanced technical accuracy with speed?
      Répondre à cette question