Real, anonymous reports from people who interviewed for Software Engineer at Amazon Web Services, newest first and distilled into what to expect across the loop.
The first thing I did was a phone screen that lasted about an hour, and it was mostly technical with the feel of it being run by my future manager. The overall plan moved quickly from there into an LP-focused loop. What stood out to me was that the process felt very structured around Amazon-style leadership thinking, even when the technical portion didn’t seem extremely hard.
My process started with an online assessment that felt like a mix of pure coding and “how you work” evaluation. I had to complete a couple of different sections that included one or two LeetCode-style coding problems, plus a work simulation element and a behavioral/leadership-style survey. Time pressure showed up fast—around the 2-hour mark—so even when I felt okay about the logic, I still had to move quickly. I ran out on one of the questions but still managed to get partial progress and keep moving forward.
Candidates typically start with an online assessment that includes coding problems, leadership principles, and sometimes work simulations. Time management is crucial, as the assessments are often timed and can be challenging, requiring candidates to balance speed with accuracy.
The technical interviews generally focus on data structures and algorithms, with questions often modeled after LeetCode problems at a medium difficulty level. Candidates should be prepared to explain their thought process and optimize their solutions, as interviewers emphasize clarity and efficiency.
Behavioral interviews heavily incorporate Amazon's Leadership Principles, requiring candidates to provide STAR-style responses that demonstrate their decision-making and problem-solving skills. It's important to connect past experiences to these principles clearly and effectively.
Some candidates encounter a system design interview that requires them to discuss architectural trade-offs and design patterns. This round assesses not just coding skills but also the ability to think critically about system functionality and scalability.
The interview process is often structured with multiple back-to-back rounds, which can create a fast-paced environment. Candidates should be ready to switch between technical and behavioral topics quickly, maintaining focus throughout the process.
Candidates report a generally professional and organized interview experience, though some noted frustrations with communication and follow-up. Clarity in reasoning and effective communication throughout the interviews are critical for success.