I was contacted via recruiter on LinkedIn. Had a couple of technical phone interviews.
First was about 30-40 minutes, was asked resume related questions and a couple of usual algo questions with coding on paper and reading it out.
Second was longer, about 50-60 minutes, more focused on databases and querying.
Preguntas de entrevista [1]
Pregunta 1
All questions were decent, not too simple but not overtly tough either. However, key is talking though the entire process even during phone interviews while working on a problem.
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.
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.
Preguntas de entrevista [1]
Pregunta 1
Pergunta historicas baseada nos principios de lideranca da amazon.
