Real, anonymous reports from people who interviewed for Software Engineer at Amazon Services, newest first and distilled into what to expect across the loop.
Get your personalized Amazon Services Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
After a recruiter conversation, I eventually moved into the main interview loop with several interviewers. The behavioral portion was tightly connected to Amazon’s Leadership Principles, and each interviewer seemed to focus on different parts of my background. The technical discussions mixed in LeetCode-style coding and also more open-ended problem solving around how I made decisions—especially when requirements or information felt incomplete.
My loop included both writing code from scratch with hints and more design-oriented conversations. One interview asked me to walk through project experience and design decisions, including how I handled stakeholder management and tradeoffs. Another covered more classical data-structure-style coding tasks, and the way I approached the work mattered as much as the final solution. Across the loop, I was repeatedly pushed to justify my choices and connect them back to long-term thinking and root-cause analysis.
2 weeks ago
Difficult Positive Bengaluru
My process started with an online assessment. It wasn’t just coding—there were general technical scenarios and also multiple-choice behavioral questions grounded in Amazon’s values. After that, I got scheduled for a technical stage where I had to do real-time problem solving, and the experience leaned heavily on DSA-style thinking.
The next step I went through was a combination of coding and behavioral questioning. One interview felt like a LeetCode-style coding task where I had to solve the problem and then continue through follow-ups. Another interview in the sequence shifted more toward system design. The format was longer than I expected—there was at least one interview that lasted about two hours and included two different interviewers, so I had to reset my focus mid-stream and keep my reasoning tight.
2 weeks ago
Average Neutral Seattle, WA
I went through a pretty frustrating path that started with early interviews and then moved quickly toward a decision. In one of my calls, the hiring m…
3 weeks ago
Easy Positive Herndon, VA
My loop was long and felt like it ran for most of the day. I started with an HR-style screening, and once I cleared that, the remote on-site interview…
2 months ago
Average Neutral Tel Aviv-Yafo
My process stretched out longer than I expected—around two months end to end. It felt pretty standard in how it was sequenced: first an online technic…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
The Loop & Timeline
The interview process typically starts with an online assessment followed by a structured loop of interviews that can span several weeks to months. Candidates should be prepared for a mix of technical and behavioral interviews, often with multiple rounds in a single day or spread over several days.
Interview timelineStructured loopMultiple rounds
Technical / Coding Screen
Candidates can expect to face a variety of technical challenges, primarily focused on data structures and algorithms (DSA), with questions often drawn from LeetCode. The coding rounds may include both straightforward problems and more complex system design discussions, and performance under pressure is crucial.
DSALeetCodeSystem design
Behavioral & Values
Behavioral interviews are heavily tied to Amazon's Leadership Principles, with a strong emphasis on using the STAR method to articulate past experiences. Interviewers often probe deeply into responses, seeking clarity on decision-making and problem-solving approaches.
STARLeadership PrinciplesBehavioral questions
Difficulty & Outcome
The overall difficulty of the interviews is described as high, with candidates often feeling the pressure to perform well in both technical and behavioral aspects. Many candidates report that even if they feel they performed adequately, the outcome may not lead to an offer, highlighting the competitive nature of the process.
High difficultyCompetitiveOutcome uncertainty
Communication & Clarity
Throughout the interviews, clear communication is essential, both in explaining technical solutions and in behavioral responses. Candidates are encouraged to articulate their thought processes and reasoning, as interviewers value clarity as much as correctness.
CommunicationClarityThought process
What Candidates Wish They'd Done
Many candidates reflect on the importance of thorough preparation, particularly in refreshing fundamentals and practicing coding problems. Some express regret over not having a clearer understanding of the expectations or not being more proactive in seeking feedback during the process.