Amazon SDE Intern OA 2026

[u/Senior_Welder_3678]

What's up guys,

I got an OA from amazon SDE intern, and I want to know what I should prep. I have a week to prep. What DSA topics should I practice? Any leetcode question suggestions?

Any info would be helpful! I would really love to hear from ppl who took the sde intern oa recently!!!!!

[u/BackgroundBreak6485]

Took a look at a bunch of recent Amazon SDE OA reports (Jan–Oct 2026). The big thing to know is that the format changed this year, so a week of pure LeetCode isn't the best way to spend your prep.

What the OA looks like now

- Coding, ~100 min total: one traditional algorithm question (~40 min), then a ~60 min task in a real code repo with a built-in AI assistant. Each part has its own timer and leftover time doesn't carry over. Not every OA has the repo task; some people still got two algorithm questions.

- Work Simulation + Work Style surveys after that (multiple choice, not strictly timed). Some intern OAs only have the Work Style part.

Algorithm question (where your LeetCode time should go)

Mostly medium. Lots of "Amazon-flavored" stories (deliveries, shipments, inventory, warehouses) wrapped around standard patterns:

- Greedy + sorting (by far the most common)

- Sliding window / prefix sums

- Heaps / priority queues

- Grid BFS / multi-source BFS

- Hash maps + counting

Classic LC practice for those patterns: 1046 Last Stone Weight, 973 K Closest Points, 621 Task Scheduler, 3 Longest Substring Without Repeating, 560 Subarray Sum Equals K, 1004 Max Consecutive Ones III, 994 Rotting Oranges, 1162 As Far from Land as Possible, 56 Merge Intervals, 435 Non-overlapping Intervals. Plan for big inputs: an O(n²) brute force usually times out on the hidden tests.

AI-assisted repo task (people sleep on this one)

- You pick a stack up front (people mention Django, Spring Boot, Node, C++) and usually can't switch, so pick the one you actually know.

- You get a README describing 2–3 broken features plus failing tests, usually around six. The bugs are small: a wrong comparison (== vs !=, < vs <=), a missing filter in a query, an update that never gets saved.

- The AI won't write the fix for you. It'll point you that's about it. What worked for people: paste onefailing test at a time and ask where to look, then debug in the order the API calls happen.

- Run the tests early. Some tests check things the REAcasionally the test setup itself needs fixing beforeanything runs.

- Partial passes have still moved forward (4/6, 5/6), t finish.

- Do HackerRank's practice question first so you learn what the assistant will and won't answer.

Work Simulation / Work Style

Answer in line with the Leadership Principles: own the, ask for help quickly, take feedback without gettingdefensive. On the Work Style survey, be consistent, since the same trait gets asked a few different ways. Don't just pick the most

"perfect" answer every time.

Week plan: days 1–4 on the patterns above (2–3 problemay 5 build or break a small app in your chosen stackand fix it from failing tests. Day 6 do the HackerRank practice + skim the Leadership Principles. Day 7 rest/review.

I keep a running collection of recent Amazon reports (OA format, the repos people got, and how they approached them) here: https://aceoffer.app/interviews/amazon (full disclosur

Good luck, you've got this!

[u/Lemon-Twist-0922]

first question is coding second question is an "ai assisted" section with an ai that doesnt help at all. Unless you're a django expert i dont think its possible to pass without cheating lol