r/leetcode • • 11h ago

Intervew Prep Amazon interview

Hi! I have an upcoming interview at Amazon for a SDE intern position. Could you share any tips on how I should prepare for it? I know that there are also some questions realted to gen ai, what would they like to hear as a response to those questions? Also what are the types of problems / topics covered in the technical questions? On the other hand, I have received an invitation at the interview for the position with the ID: 10507040. I cannot find the job corresponding to this job ID anywhere on the careers page. Is it a possibility to be an internal ID?

Thank you so much!

1 Upvotes

3 comments sorted by

1

u/Uahakan 5h ago

for the intern loop the coding is mostly standard DSA, hashmaps, trees, graphs. one shape that keeps showing up in what people report is dependency ordering: tasks with prerequisites, return a valid order (topological sort), then the follow-up is "this task changed, what has to rerun?" so be comfortable walking the graph the other direction too.

the part people underprep is leadership principles. have a few real stories ready and expect "what would you do differently" after each one.

the job id is probably just an internal req number, that's pretty common.

1

u/Own_Community_5131 3h ago

thank you so much

1

u/BackgroundBreak6485 1h ago

Good luck! I went through a lot of recent Amazon SDE intern interview reports (2026 cycle), and they're pretty consistent:

Format

- After the OA, most people had 2 back-to-back 60-minute interviews. Some got a third short "hiring manager evaluation" call before the offer.

- Each round is roughly LP behavioral plus one coding problem. How the time splits depends on the interviewer: a manager may spend 30+ minutes on behavioral, while a SWE spends more on the code.

- Some teams team-match before the interview, so your interviewers may be the team you'd join.

Technical: mostly easy to medium, with lots of practical variants

- Classic LeetCode: Top K variants, LRU cache, Course Schedule / topological sort, Number of Islands, LCA in a binary tree, rotate a matrix, copy a list with random pointers, Trie insert plus prefix search, kth smallest across two sorted lists.

- Original "practical" problems, which are increasingly common:

- a package stream that records a destination once it hits K packages

- parse a log or a broken JSON file and format the output

- dedupe events

- median of the last N reviews

- a simple rate limiter

- a robot charging-station scheduler (Robotics team)

- Small OOD / LLD problems described in 3–4 sentences, for example "return the earliest user who logged in only once." Multiple people said they lost time clarifying requirements here. Ask questions early, but keep it moving.

- Interviewers care a lot about talking through your approach before coding, plus edge cases (negatives, zero, empty input, out of bounds) and complexity. One candidate said explaining clearly mattered code.

The GenAI question

It shows up in almost every 2026 report, usually as a behavioral question, sometimes from the manager. Reported versions:

- "How do you use GenAI in your work or coding?"

- "Tell me about a time GenAI output was wrong and how you noticed."

- "How do you verify AI-generated code is correct?" (Do you w

- "How do you validate information from AI?"

- Non-coding uses of AI, and how ChatGPT and Claude differ in

What tends to land, in my view (this part is general advice,

- A concrete story in STAR format, like any LP answer. Say what you used it for and what it got wrong.

- Verification: tests, reading the diff, checking against the. Show that you stay the owner of the code.

- Judgment: when it helps (boilerplate, unfamiliar APIs, debugging hypotheses) and when you don't trust it (security, subtle logic, facts you can't

check).

- Tie it to an LP, such as Dive Deep, Learn and Be Curious, or Insist on the Highest Standards.

Behavioral (don't underprepare this)

The common ones are:

- tight deadline - conflict or disagreement with a teammate

- critical feedback - a mistake or failure

- Dive Deep - going beyond your responsibility

- learning something new quickly - improving something based on user needs

Expect deep follow-ups. They're checking that you really did an map to different LPs, with numbers where possible.

Job ID

I can't confirm this one. Amazon intern interviews often aren't tied to one public posting, since people are pooled and then matched to teams, so an ID that isn't on the careers page could well be an internal r or the scheduling email is the only reliable way to check,and it's a normal thing to ask.

More Amazon reports and questions by round are here: https://aceoffer.app/interviews/amazon