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

      24 ott 2014
      Candidato anonimo a colloquio
      Seattle, WA
      Nessuna offerta
      Esperienza negativa
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura tramite un'altra fonte. La procedura ha richiesto 4 settimane. Ho sostenuto un colloquio presso Amazon (Seattle, WA) nel mese di set 2014

      Colloquio

      I got an email out of the blue asking me if I wanted to fly to Seattle and interview. I still don't know where they got my resume; but I assume it was from when I applied for a co-op position a year before. I was excited to go, but from the very start I got the impression it was going to be tough. I got an email about a week beforehand with about 8 attachments containing literature about the company. I was informed that I would be doing a programming problem for most of the day, and I would have my choice of language, compiler, and OS. When I arrived on campus, we were given visitor badges and told to wait until someone came to get us. I felt weird that the majority (at least 75%) of interviewees were foreign students. It made me feel like I was out of my league. We were taken upstairs to a conference room where HR gave a speech about how great the company is. We were then assigned to a table, and given a laptop and packet describing the programming challenge. The challenge was supposed to be team-based (with the people at your table), but it turned out to be more individual that I anticipated. The problem broke into three pieces, and each person picked a part to do. You didn't have to use the same language. The parts were basically independent, but I could see where sharing code between teammates could be helpful. We were given 6 hours to complete the task. After about half an hour, an engineer came to gauge our understanding of the problem, and clarified anything we didn't know. We then worked for about an hour, and an engineer pulled each of us out for a personal "interview". It was the least personal interview I have ever had. The engineer was all business, and we just talked about my approach to the problem. When I got back, I had about 4 more hours to complete the assignment. Half an hour before the deadline, we were individually interviewed again. Pretty much the same type of thing, just talked about my approach. The interviewers were always interested in efficiency. They asked questions like "how could you make this better/faster", and "why did you use this data structure". I really got bit in the butt because I was forced to use C++, instead of C (which I am much more familiar with). I was unfamiliar with the C++ libraries, and I had to waist a lot of time looking at documentation. BIG TIP: be very familiar with your language before you go! My solution was incomplete, and I knew this when I turned in. I was encouraged to write a README file which explained my shortcomings, and any ideas I had to make the code more efficient. At the end of the interview, we had a group Q&A with a developer. I got the impression that this was a very stressful job with poor work/life balance. I love the area, so if I had gotten an offer it would have been a tough decision weather I was willing to sacrifice a stressful job for my dream city.

      Domande di colloquio [1]

      Domanda 1

      Questions are covered by a non-disclosure agreement
      Rispondi alla domanda

      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