Amazon interview questions

Tech / SWE · 10 questions · last reported May 2026
Report an interview →

Browse 10 Amazon interview questions for software engineering and software development interview preparation. Questions in this collection are tagged for internship, new graduate, full-time roles. Explore the topics and stages below and filter the collection to plan your practice.

Interview stages in this collection
Onsite, Phone screen, Online assessment (OA)
Practice topics
coding (4), system-design (3), behavioral (2), binary-search (2), low-level-design (2), oop (2), ads (1), ai (1)

Questions come from candidate contributions and online research. Reports reflect past experiences and do not guarantee what Amazon will ask. Locked question details require points. Public examples below are free to read.

Read 3 free Amazon interview question examples

Browse all Amazon questions

10 questions

Free Amazon interview question examples

Read the full problem statements and use the links to revisit or share a specific example.

Insert Random

Medium · Onsite · Internship

After my project discussion, they gave me a data structure design problem. I had to support insert, delete, and getRandom in O(1). The interviewer cared about how I handled deletes without making random retrieval slower. I talked through the tradeoff between a list and a hashmap, then dry ran a few operations to make sure the indices stayed correct.

Binary Search

Medium · Online assessment (OA) · Onsite · Internship

I had two in-person interviews, each around 60 minutes. Both mixed Leadership Principle questions with technical questions, and one of the coding problems was a pretty standard medium binary search. They also asked some low-level memory questions near the beginning, which caught me a bit off guard. The interviewer pushed on edge cases and wanted me to clearly explain why the search bounds moved the way they did.

Robot Path

Medium · Online assessment (OA) · Internship

The technical problem was about a robot moving around a grid based on a vector of directions. I had to return whether the robot had ever visited the same point before. The interview was a single one-hour round, with about half the time on coding and the rest on my projects and how I approached decisions in them. It wasn't super tricky, but there were edge cases around returning to the origin and tracking positions correctly.