Updated by Amazon candidates
Software Development Engineer, Level 4 Interview Experience
It was the usual four-round AWS loop, but the HM actually spent time on how I use GenAI to fast track my workflow, and the Bar Raiser was basically all LPs with tons of follow-ups.
Interview process
I went through the usual four-round AWS loop and finished my last round in October. The first round mixed LPs and experience with coding, then the HM round was LPs plus a GenAI fluency conversation about how I use it to speed up my workflow. After that I had another LP plus coding round, this time a string parsing question, and the last round was the Bar Raiser. That BR was basically all LPs and they kept deep diving with a lot of follow-ups. Nothing about the format felt especially unusual to me.
- Technical interview
- Final round
Interview rounds
7 questions across 4 roundsTechnical interview (1)
2 questionsOverview
They split this one between LPs/experience and a pretty simple coding question in a LeetCode-style editor, and I just had to dry run it and explain TC/SC.
Question types asked
Specific questions asked
Tell me about your experience and walk through examples tied to Leadership Principles like Customer Obsession, Learn and Be Curious, and Ownership.
Solve this coding problem in the editor.
Can you dry run your solution?
What are the time and space complexities?
I solved a very simple DSA question. I can't share the exact prompt because of the NDA, but it was basic enough that anyone who's done even basic DSA could handle it. I wrote it directly in a LeetCode-style editor, then dry ran it and explained the time and space complexity.
Final round (1)
2 questionsOverview
The hiring manager round was mostly LPs, and then they switched into a practical GenAI fluency discussion about how I use it in my workflow.
Question types asked
Specific questions asked
Can you give concrete examples?
They were looking for practical usage, not theory. I talked about how I use GenAI to speed up my general workflow, and they wanted concrete examples, the same way they did for the LP answers.
Technical interview (2)
2 questionsOverview
This was another LP plus coding round, and the coding part was a string parsing problem with constraints and conditions.
Question types asked
Specific questions asked
Tell me about past situations that map to Leadership Principles.
Solve this string parsing problem with constraints and conditions.
The coding part was a string parsing question with some constraints and conditions. I can't share the exact question, but it was still in the basic DSA range rather than anything especially hard.
Final round (2)
1 questionOverview
The Bar Raiser was all LPs, and they kept deep diving on every story with a lot of follow-ups.
Question types asked
Specific questions asked
Walk me through stories that show different Amazon Leadership Principles.
Can you go deeper on that example?
Give me more specifics.
This round was basically all LPs. They did deep dives on the stories and kept pushing for specifics, so it felt like the whole point was to really test how solid and detailed my examples were.
Interview tips
I'd prep every LP, not just the common ones, because what you get asked feels pretty random. They wanted concrete examples for everything, even the GenAI part, so I wouldn't go in with high-level answers. For coding, I'd just be comfortable solving basic DSA in a LeetCode-style editor, then dry running it and explaining time and space complexity cleanly. I wouldn't over-rotate on super hard problems for this one.
Company culture
The big thing I noticed is the bar felt much higher on LPs than on technical. The technical side and even the overall feel can vary a lot by team and interviewer, so two AWS candidates can have very different experiences. Aside from that, the process itself felt pretty straightforward and it's already well documented online.
Get full access with a membership, or share your experience to try it free.
More Amazon interview experiences
“They brought up on-call in multiple conversations, so that was the culture signal I actually believed. Then the hiring manager had me design a package tracker that could survive duplicate, out-of-order updates during Prime Day.”
“I went in expecting the usual behavioral-first format, but in my loop they flipped it and opened with the coding question. The behavioral part still mattered, they just used the follow-ups to see if I actually knew my own work in detail.”
