I applied through a recruiter. The process took 1+ week. I interviewed at Amazon (Seattle, WA) in Nov 2016
Interview
They found me on linkedin- many calls and many interviews stage one a recruiter will call you to explain they are hiring 400 new architect in California, then a sales manager will call to ask genera; questions - what is cloud IaaS, PaaS Amazon services - SQL load balancing and then you will be scheduled to visit their office in Seattle which is a big warehouse! comparing to Microsoft is it a dump! they you will spend 5-6 hours talking about their 10 leadership BS - memorize it and rehearse it they are currently hiring almost every body so wont be stressed!
Interview questions [2]
Question 1
will be conducted that make very much no real sense! questions were mostly to hire somebody that can convince Microsoft customer host their enterprise application on AWS - they were mostly disgruntled Microsoft employee trying to get back at the company that filed them or didn't provide them proper salary - so dont defend Microsoft !
What is difference between cluster and mirroring
How many nodes a SQL 2016 can support
MS SharePoint Farm topology
How to host SQL 2015 nodes on AWS
Machine learning models and currently which locations support it ?
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
I applied online. The process took 1 day. I interviewed at Amazon (Seattle, WA) in Apr 2026
Interview
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.
Interview questions [1]
Question 1
Can you walk us through a time you solved a complex problem under tight deadlines, and how you balanced technical accuracy with speed?