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

      1 abr 2013
      Empleado anónimo
      Seattle, WA
      Oferta aceptada
      Experiencia neutra
      Entrevista difícil

      Solicitud

      Me postulé a través de una facultad o universidad. El proceso tomó 2 semanas. Acudí a una entrevista en Amazon (Seattle, WA) en oct 2010

      Entrevista

      Amazon held a tech-talk on campus, which I attended. Afterwards, there were recruiters collecting resumes. I gave the recruiter my resume and waited to hear back. I heard back about one month later, and scheduled an on-campus interview. There were 3 back-to-back 45 minute interviews, which both involved coding with a pen and paper. During the first interview, we talked a bit about my resume, then got into some tech questions. Nothing too difficult, just practice what you learned in class. Bit-shifting and data structures, mostly. Also, KNOW YOUR TIME/SPACE COMPLEXITIES. Seriously. Before you offer a solution, know what its time/space complexity is, because they will ask for it. Lastly, there was a general logic question, which I didn't have time to answer, but I emailed the interviewer the answer later. Then, I was able to ask the interviewer some questions. The second interview wasn't very hard, just two slightly longer questions. The solutions weren't difficult, but they had a lot of corner cases that you needed to watch out for. Be very cognoscenti of that: If a question seems really easy, watch for corner cases. After that, same story, asked the interviewer some questions. Got the offer four days after the interview. Some tips/notes: 1) Be yourself! Be friendly and nice. Don't be afraid to make a joke. Don't be awkward or nervous. Just relax. You've got this. It's very important to be well-spoken. 2) Know your time/space complexities. 3) Go over your data structures. Know them better than you know yourself. 4) Watch for corner cases. 5) If you slip up, just explain yourself and your mistake. They'll understand, we all do it. 6) Be VERY vocal about what you're thinking about. They care about how you arrive at the answer. 7) If they give you a question that you have heard before, tell them. They appreciate the honesty, and then you get a chance to talk a bit about the answer. I was given one question that I already knew the answer to, I simply told the interviewer that I was already familiar with this question, and gave him my solution. We talked about it, and then I was asked to come up with a different solution to the same problem. 8) Probably not something to stress about, but it probably helps to dress nice. Nothing amazing, I just wore a button-up and nice jeans. The point is, don't show up in a T-shirt and daisy dukes, or something. Dress like you care. You should care, after all. 9) If you've got an interview scheduled and you're reading this, like I was reading all of these before mine, you're probably stressing out like I was. Just calm down. Relax. Everything is going to be okay. You got the interview because they saw something in you. YOU'RE GOING TO DO FANTASTIC. I believe in you.

      Preguntas de entrevista [1]

      Pregunta 1

      Nothing was too difficult. Bit-shifting, data structures, efficiency. Finding phone numbers of a given format inside large number of different HTML files.
      Responder pregunta
      15

      Otras evaluaciones sobre las entrevistas para el cargo de Software Development Engineer I 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

      Las mejores empresas en cuanto a "Remuneración y prestaciones" cerca de ti

      avatar
      Maze
      4.5★Remuneración y prestaciones