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

      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

      Empleador activo

      Información
      Evaluaciones
      Pago y prestaciones
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Evaluaciones de Amazon | Empleos en Amazon | Sueldos en Amazon | Prestaciones en Amazon
      Entrevistas en AmazonEntrevistas para el cargo de Software Development Engineer en AmazonEntrevista en Amazon


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empleadores

      • Cuenta de empleador gratuita
      • Centro de empleador

      Información

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

      Trabaja con nosotros

      • Anunciantes
      • Oportunidades laborales
      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 desde adentro.

      Búsquedas de empleo

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

      Entrevista para Software Development Engineer

      20 jun 2014
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia positiva
      Entrevista promedio

      Solicitud

      Me postulé a través de un reclutador. El proceso tomó 3 meses. Acudí a una entrevista en Amazon en may 2014

      Entrevista

      I am from Madrid, Spain and the position was for Seattle, WA. I contacted a recruiter via email. The whole process took 3 months. They sent me a link to do an online test, through interviewzen. It consisted in two parts: - Java coding. It was about binary trees and recursion. - OOP question. It was about inheritance and polymorphism. I passed the test so they scheduled a technical phone interview with an engineer few weeks later. This was the script: 1) Questions: - First question apart of “Is this a good moment?”: Why do you want to work here? => You better be ready for this. - Which projects of your career are you proud of? - Which languages are you familiar with? - Why? => I didn’t expect this question. - Are you familiar with trees? - Really? What is a tree? 2) Technical part, coding. - We used collabedit. - It was about binary trees and recursion again. - It’s not worth it to put the question itself, just be ready to be asked about data structures, recursion and efficiency in terms of Big O. 3) Interviewing the interviewer. - You should have 3-5 questions for them. It took one hour and one minute. They sent an email 3 days later saying "we have decided to move forward with the search process in order to target the candidate…”. Looking backwards I don’t think it was difficult. I wasn’t ready enough. They were very kind with me all the time and I learnt a lot during the process.

      Preguntas de entrevista [1]

      Pregunta 1

      It was simply unexpected, why do you use Java?
      1 respuesta
      3

      Otras evaluaciones sobre las entrevistas para el cargo de Software Development Engineer en Amazon

      Entrevista para 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 para Software Development Engineer

      3 jun 2026
      Candidato de entrevista anónimo
      Sin ofertas
      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 para Software Development Engineer

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

      Solicitud

      Me postulé en línea. 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