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

      20 giu 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 3 mesi. Ho sostenuto un colloquio presso Amazon nel mese di mag 2014

      Colloquio

      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.

      Domande di colloquio [1]

      Domanda 1

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

      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