Ir al contenidoIr al pie de página
  • Empleos
  • Empresas
  • Sueldos
  • Para empresas

      Impulsa tu carrera profesional

      Averigua cuánto podrías ganar, encuentra el empleo perfecto y comparte información sobre tu vida laboral y personal de forma anónima.

      employer cover photo
      employer logo
      employer logo

      Amazon

      Empresa activa

      Información
      Opiniones
      Sueldos y beneficios
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Opiniones sobre Amazon | Ofertas de empleos en Amazon | Sueldos en Amazon | Beneficios en Amazon
      Entrevistas de AmazonEntrevistas para el puesto de Software Development Engineer en AmazonEntrevista de Amazon


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empresas

      • Cuenta gratuita de empresa
      • Centro de empresas

      Información

      • Ayuda
      • Normas
      • Condiciones de uso
      • Privacidad y opciones de anuncios
      • No vender ni compartir mi información
      • Herramienta de consentimiento de cookies

      Trabaja con nosotros

      • Anunciantes
      • Empleo
      Descargar aplicación

      • Buscar por:
      • Empresas
      • Empleos
      • Ubicaciones

      Copyright © 2008-2026. Glassdoor LLC. «Glassdoor», «Worklife Pro», «Bowls» y sus logotipos son marcas comerciales registradas de Glassdoor LLC.

      Empresas seguidas

      Sigue a tus empresas favoritas para estar al tanto de las últimas oportunidades y disponer de información de primera mano.

      Búsquedas de empleo

      Recibe recomendaciones y actualizaciones personalizadas al iniciar tu búsqueda.

      Entrevista de Software Development Engineer

      21 jun 2013
      Empleado anónimo
      Oferta aceptada
      Experiencia positiva
      Entrevista fácil

      Solicitud

      Solicité el puesto a través de la escuela superior o la universidad. El proceso duró 1 semana. Acudí a una entrevista en Amazon en oct 2012

      Entrevista

      They were recruiting from my University. I submitted my resume online on Wednesday. Thursday they emailed me to set up an interview for Tuesday morning. Tuesday night they emailed me to setup 3 more interviews on Thursday. Friday I was notified I had been selected to receive a full time offer. The recruiter was a little flaky after that, missing phone appointments. Eventually he followed through and set me up with a weekend trip to Seattle to meet some potential teams. The interviews were mostly technical. Each one was 45 minutes. Each one asked two programming questions and a couple personality type small talk questions. "Why did you choose to study computer science," "what's your favorite/least favorite thing about school." I don't recall any behavior questions, you know the kind, "tell me about a time you failed miserably at something and everyone laughed at you." Only one of the interviewers tried to make me write compileable code. I tried my best, but reminded how valuable a good IDE is. Know your algorithms and their big-o. Know how to find test cases. Know recursion, dynamic programming, all of the fun stuff. Going through the interviews I made sure to constantly tell the interviewer what I my thoughts were and why. I gave a reason for everything and when suitable reasons against anything else.

      Preguntas de entrevista [1]

      Pregunta 1

      Given a stream of characters and a set of characters, find the shortest sequence in the stream containing all characters in the set.
      1 respuesta
      2

      Otras opiniones sobre las entrevistas para el puesto de Software Development Engineer en Amazon

      Entrevista de Software Development Engineer

      17 jun 2026
      Candidato de entrevista anónimo
      Oferta rechazada
      Experiencia positiva
      Entrevista fácil

      Solicitud

      Acudí a una entrevista en Amazon

      Entrevista

      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.

      Preguntas de entrevista [1]

      Pregunta 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.
      Responder pregunta

      Entrevista de Software Development Engineer

      3 jun 2026
      Candidato de entrevista anónimo
      Sin oferta
      Experiencia positiva
      Entrevista difícil

      Solicitud

      Acudí a una entrevista en Amazon

      Entrevista

      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.

      Preguntas de entrevista [1]

      Pregunta 1

      Questions related to leadership principles
      Responder pregunta

      Entrevista de Software Development Engineer

      23 jun 2026
      Candidato de entrevista anónimo
      Calgary, AB
      Sin oferta
      Experiencia positiva
      Entrevista normal

      Solicitud

      Envié una solicitud electrónica. Acudí a una entrevista en Amazon (Calgary, AB) en jun 2026

      Entrevista

      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.

      Preguntas de entrevista [1]

      Pregunta 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
      Responder pregunta