Solicité el puesto a través de un captador. El proceso duró 2 meses. Acudí a una entrevista en Amazon
Entrevista
It took 2 months to setup a lot of going back and forth with coordinator since recruiter reached out with interest inquiry. I was asked to give time slots and then got response that interviewer was not available.
We have gone back and forth with this approach a couple of times and suggested that we reverse the approach to let me know when interviewer will be available so that I can make myself available. This worked!
Schedule and few links to blogs and principles etc..came out in an email.
Preguntas de entrevista [1]
Pregunta 1
Started with regular position summary (3 responsibilities (Hands on coding , Work with partners and work with clients in specific industry) nothing unusual here..
After tell me about yourself and a few regular ones about architecture solutions you delivered, Follow up always seemed to go back to coding level skills (realized its more of a senior coder on other end). Then it turned to something like this
Lets say you are hired and for some unfortunate reason, disaster strike and you are now the leader of the unit.. what services would you do to setup? and How will you go about setting up partnerships?
Few rounds of interview, mixed with behavioral and technical questions to showcase you knowledge of building system on aws. They also asked gen ai questions on how you would create these systems
Envié una solicitud electrónica. El proceso duró 1 día. Acudí a una entrevista en Amazon (Seattle, WA) en abr 2026
Entrevista
You do 4 back to back interview in 1 day. It was exhausting. Besides that really appreciated the recruiter giving out interview prep before it takes place. The good thing is there is no coding round.
The interview process was very challenging and thorough. The questions required deep technical knowledge and problem-solving under pressure. While tough, it was fair and tested real-world skills, communication, and adaptability.
Preguntas de entrevista [1]
Pregunta 1
Can you walk us through a time you solved a complex problem under tight deadlines, and how you balanced technical accuracy with speed?