Interview Experience of Software Development Engineer in Amazon For Freshers

 

RECRUITMENT Still Going On For This Role. CLICK HERE for Job Details

Real Candidate Interview Experiences (India)

1. Reddit – Amazon India SDE‑1 Full-Time New Grad
A candidate shared:

“Medium problem was similar to group-anagrams… Easy problem was sum-nodes-binary-tree…”
“Second round… one leetcode style problem… LFU Cache… LLD… maintainable cache.”

 CLICK HERE to check Review

This matches typical SDE‑1 patterns: a medium + easy coding question in Round 1; Round 2 includes a LeetCode-style problem plus a low-level design (LLD) for cache.

2. Reddit – Amazon India SDE‑1 (r/leetcode)
Shared:

“Two questions were asked — one based on Binary Search and the other on Complete Binary Trees.” 

 CLICK HERE to check Review 

So Amazon often pairs a data-structures problem with recursion/tree or binary search.

3. Glassdoor – Amazon Chennai Applications Engineer
Another mention:

“Interview consists of 4 rounds. Each round consists of 1 coding (Basic arrays) and either SQL or UNIX related.”

CLICK HERE to check Review  

Though for a different engineer level, it shows diversity of topics.

---

Interview Structure & Pattern

Round	Focus Area	Details
OA (Online Assessment)	2 coding problems + coding style questions, timed ~60 min
Interview 1	DSA (medium + easy) + brief LP (Leadership Principles)
Interview 2	DSA (medium/hard) + LLD system question
Interview 3	Bar‑raiser: LP behavioral + 1 coding/optimization question
Optional rounds	SQL/UNIX or high-level system design (HLD) for experienced roles

Panel size: 1–2 interviewers per round; format: video/virtual. Wait times between rounds vary (1 week–1 month).

---

SDE Interview for This Chennai Role

Based on JD (eBook checkout, Java/C++, algorithms, distributed systems):

OA:

• Question 1: Given list of transactions, calculate max transaction within sliding window K. (Java/C++)

• Question 2: Write function to validate eBook URL list sorted by timestamps (binary search + string processing).

• Coding style: Format code with consistent naming, comments.

Round 1 – DSA + LP (60 min):

• Intro (~5 min)

• DSA Medium: "Group Anagrams" / "Min platforms for ebook requests"

• DSA Easy: Sum of leaf nodes in tree or validate parentheses in ebook metadata

• LP: "Tell me about a time you solved a tricky bug."

Round 2 – DSA + LLD (60 min):

• Coding: Implement LFU Cache or transaction cache.

• LLD: Extend LFU design to support multi-instance sync across services.

Round 3 – Bar Raiser (LP + Code) (60 min):

• LP: Deep-dive questions about ownership, customer obsession, innovation.

• Coding: Optimize eBook purchase list using WF algorithm or sliding window for concurrency.

(Optional) Round 4 – HLD / SQL / UNIX:

• HLD: Design scalable eBook checkout microservice (API, DB partitioning).

• SQL/UNIX: Simple SQL queries on transaction audit table or describe Linux® service deployment.

Common Tips:

• Explain time & space complexity

• Write clean code in object‑oriented Java/C++

• Ask clarifying questions

• Use STAR format for behavioral

• Prepare Amazon Leadership Principles with examples