Passa al contenutoPassa al piè di pagina
  • Lavori
  • Aziende
  • Stipendi
  • Per le aziende

      Migliora la tua carriera

      Scopri le tue potenzialità di guadagno, trova lavori da sogno e condividi approfondimenti su lavoro e vita privata in forma anonima.

      employer cover photo
      employer logo
      employer logo

      Amazon

      Azienda coinvolta

      Chi siamo
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su Amazon | Offerte di lavoro di Amazon | Stipendi di Amazon | Benefit di Amazon
      Colloqui di AmazonColloqui per Software Development Engineer presso AmazonColloquio di Amazon


      Glassdoor

      • Chi siamo
      • Contattaci

      Aziende

      • Account Business gratuito
      • Spazio per le aziende
      • Blog per le aziende

      Informazioni

      • Aiuto
      • Linee guida
      • Condizioni d'uso
      • Privacy e scelte pubblicitarie
      • Non vendere né condividere le mie informazioni
      • Strumento per l'accettazione dei cookie

      Lavora con noi

      • Inserzionisti
      • Carriere
      Scarica l'app

      • Cerca:
      • Aziende
      • Lavori
      • Località

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" e il relativo logo sono marchi registrati di Glassdoor LLC.

      Aziende seguite

      Non lasciarti sfuggire opportunità e informazioni privilegiate seguendo le aziende dove vorresti lavorare.

      Ricerche di lavoro

      Ricevi suggerimenti e aggiornamenti personalizzati avviando le tue ricerche.

      Colloquio per Software Development Engineer

      25 nov 2014
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza positiva
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 5 settimane. Ho sostenuto un colloquio presso Amazon nel mese di nov 2014

      Colloquio

      This is the story of how I Bombed That Interview but had a pleasant time doing it. I was initially contacted by a recruiter through LinkedIn. They were interviewing for one or more positions in Seattle, USA, but for some reason they were traveling all the way to my part of the world (hint: Not USA) and making a big hiring event. Apparently, "new talent" is hard to come by in Seattle these days. After sending the recruiter my CV, I was directed to a website to do a coding exercise that took about two hours to finish. A few days later, I was invited to an "on-site" interview at the recruiting event. At this point, the event was about three weeks away. The interview event consisted of two interviews with a possible third or fourth interview "if we need to know more". Each interview was 50 minutes with a 10 minute break in between. The first interviewer was a Software Engineer and after a short chat about my work experience, I was given a code exercise and asked to write my solution on the whiteboard. Several days of preparation doing Codewars problems and trying my luck with paper and pencil coding did not prepare me for my biggest enemy: Complete Nuclear Meltdown (in the brain). I simply could not think straight in the situation so although I eventually arrived at something that worked, it was not pretty and it took too much time. The second interview was identical to the first but the interviewer was a Manager with a background in coding. Once again, the coding exercise made me pretty flustered. As an example, I realized a few days later that I had created an endless loop even after going over the code two times on the whiteboard. Whoops. After the first two interviews, I was told that my interview was over which was a pretty clear message that things had not gone right because they had mentioned the possibility of three and four interviews. A week later, I was called by the recruiter who confirmed what I already knew: No offer for me. To be fair, there could have been other things contributing to their decision than my coding abilities but unfortunately, they have a policy of not providing feedback to candidates, so I will never know if they also thought I was lacking in other areas. Overall, the communication was very smooth and professional and all the people I interacted with were very nice so the experience was pleasant. Biggest takeaway from all this: Practice more and try and keep a cool head.

      Domande di colloquio [1]

      Domanda 1

      In what situation has "an acquired skill" helped you in a way you didn't expect.
      Rispondi alla domanda
      1

      Altre recensioni di colloqui per Software Development Engineer presso Amazon

      Colloquio per Software Development Engineer

      17 giu 2026
      Candidato anonimo a colloquio
      Offerta rifiutata
      Esperienza positiva
      Colloquio facile

      Candidatura

      Ho sostenuto un colloquio presso Amazon

      Colloquio

      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.

      Domande di colloquio [1]

      Domanda 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.
      Rispondi alla domanda

      Colloquio per Software Development Engineer

      3 giu 2026
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza positiva
      Colloquio difficile

      Candidatura

      Ho sostenuto un colloquio presso Amazon

      Colloquio

      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.

      Domande di colloquio [1]

      Domanda 1

      Questions related to leadership principles
      Rispondi alla domanda

      Colloquio per Software Development Engineer

      23 giu 2026
      Candidato anonimo a colloquio
      Calgary, AB
      Nessuna offerta
      Esperienza positiva
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Amazon (Calgary, AB) nel mese di giu 2026

      Colloquio

      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.

      Domande di colloquio [1]

      Domanda 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
      Rispondi alla domanda