I was contacted by a recruiter and flown to Seattle. After a couple of hours of talking to engineers and asking questions, I spent the rest of the day doing a group programming problem. I can't go into detail about the question, but it was such that every member of the group could work on a seperate part. I thought I did pretty well, but I guess they were looking for something else, or maybe I didn't give the right impression during the 30 minute 1 on 1 interview in which we discussed the code I had written so far and talked about what I wanted to do at Amazon.
Other Software Development Engineer I Interview Reviews for Amazon
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.
Interview questions [1]
Question 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.
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.
Um teste de código online, se aprovado, vai para o loop. O loop é 4 entrevistas seguidas, duas em inglês e duas em português. 3 entrevistas técnicas de código, todas as 4 têm pergunta de liderança.
Interview questions [1]
Question 1
Pergunta historicas baseada nos principios de lideranca da amazon.
