Amazon AI Engineer candidates report a multi-stage process combining an online assessment, DSA coding rounds, generative AI/ML questions, and Amazon's leadership principles, with most reported outcomes ending in rejection.
$168K
Avg. Base Comp
$210K
Avg. Total Comp
3-5 rounds
Typical Rounds
4-5 weeks
Process Length
Amazon's AI Engineer loop typically opens with an online assessment—candidates report a stack-based coding problem in the style of Valid Parentheses, though one applicant for a closely related AI role instead got a multiple-choice aptitude test with little ML content, so the format isn't fully consistent. From there, most candidates describe a multi-round loop pairing classic coding rounds with AI-specific technical questions. Medium-to-hard LeetCode problems show up across nearly every report, often testing core data structure fundamentals like stacks rather than ML-specific algorithms.
The ML and generative AI questions are where preparation matters most: candidates mention being asked about CLIP, GRPO, RoPE embeddings, LLM benchmarks, and transformer architectures, alongside a deep dive into their own technical project where interviewers probe the reasoning behind specific architectural choices rather than just the outcome. Amazon's leadership principles are woven throughout—one candidate faced two LP questions in every single round of a five-round loop, while another described a dedicated bar raiser round built entirely around Amazon's leadership principles.
Not every stage is deeply technical: one candidate noted the person running their 'HM interview' wasn't actually their hiring manager and couldn't assess their AI/ML background in depth. Reported outcomes skew toward rejection, though at least one candidate in a similar cycle did receive an offer, so a well-reasoned technical narrative combined with sharp leadership-principle stories appears to matter more than any single question.
Synthesized from 5 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Amazon process.
My experience started with an online assessment that was relatively straightforward, followed by a three-round interview loop. Behavioral questions showed up in every round, and the technical bar included medium-to-hard LeetCode problems. The recruiters were genuinely friendly and responsive throughout, which was a refreshing part of the process.
The screening rounds focused on my project experience and the reasoning behind my architectural choices. I was asked to walk through the most technical project I'd done and explain why I'd picked specific approaches. The interviewers wanted to understand my decision-making process, not just whether I knew the right answer. There was also an emphasis on basic generative AI concepts and model names—nothing obscure, but enough to show I keep up with the field.
What bothered me most was that the hiring manager didn't actually conduct the HM interview; someone else stepped in who lacked the depth to really assess my AI/ML background. That round felt like checking boxes rather than having a genuine technical conversation. The overall tone was transactional. I got the sense that they were going through a scripted process and I was one of many candidates being filtered through it. I didn't advance, and frankly, after seeing how mechanical it all felt, I wasn't disappointed. One candidate in a similar timeline did get an offer, though, so there's clearly a path through—it likely just requires aligning perfectly with whatever checklist they're using that cycle.
Prep tip from this candidate
Have a crisp narrative for your most technical project with clear reasoning for each major decision—they drill into 'why' extensively. Brush up on current generative AI model names and capabilities, and practice medium-hard LeetCode regularly. Be aware that the HM interview may not actually involve your hiring manager, so don't expect deep technical vetting at that stage.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Amazon
Write a query that returns all neighborhoods that have 0 users.
| Question | |
|---|---|
| 2nd Highest Salary | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Upsell Transactions | |
| Paired Products | |
| Merge Sorted Lists | |
| Compute Deviation | |
| Download Facts | |
| Average Quantity | |
| Random SQL Sample | |
| Manager Team Sizes | |
| Size of Joins | |
| Month Over Month | |
| Flight Records | |
| Get Top N Frequent Words | |
| Prime to N | |
| Top 3 Users | |
| Recurring Character | |
| Longest Streak Users | |
| Jars and Coins | |
| Bank Fraud Model | |
| Project Pairs | |
| Always Excited Users | |
| Longest Increasing Subsequence |
Synthesized from candidate reports. Individual experiences may vary.
Most candidates report starting with an online assessment. One AI Engineer candidate described a stack-based coding problem similar to Valid Parentheses, while an applicant for a related AI role instead received a multiple-choice test covering aptitude, logical reasoning, and grammar rather than ML content. A separate candidate began with a live phone screening before moving into the main loop, so the exact first-step format may vary.
Candidates consistently report facing **medium-to-hard LeetCode problems** in dedicated coding rounds—one AI Engineer candidate described two coding rounds within a five-round loop, and another described two rounds focused specifically on data structures and algorithms. These rounds emphasize core CS fundamentals like stacks and pattern recognition rather than ML-specific optimization.
This stage covers ML breadth and depth. Candidates report being asked about CLIP, GRPO, RoPE embeddings, and LLM benchmarks, as well as transformer architectures and how they've applied AI in real projects. One related-role candidate also fielded questions on NLP and LLM fundamentals; the exact topic mix appears to vary by interviewer and team.
Interviewers ask candidates to walk through their most technical project in detail, focusing heavily on the reasoning behind architectural decisions rather than just the final outcome. Expect follow-up questions probing why specific approaches were chosen over alternatives; one candidate described this as the core of the evaluation.
Amazon's leadership principles show up repeatedly. One candidate reported two leadership-principle questions embedded in every single round of a five-round loop, while another described a dedicated final bar raiser round built around Amazon's leadership principles and tenets. Candidates typically prepare specific STAR-format stories rather than generic answers.
In at least one reported case, the person conducting the 'HM interview' was not actually the hiring manager and lacked the depth to evaluate the candidate's AI/ML background, making that round feel more like a formality than deep technical vetting. Candidates may want to temper expectations for how technical this final stage will be.
