How Amazon’s SDE interviews actually run, based on aggregated candidate reports (Blind, Glassdoor, GeeksforGeeks, 1Point3Acres). Amazon runs large-scale campus and off-campus SDE-1 drives in India, so this loop is common, not a rare, boutique process.
Reported total compensation for an India-based SDE-1 fresher hire is in the ₹26-32 LPA range (Levels.fyi median ~₹26L; base commonly ₹18-22L plus sign-on bonus and RSUs), though offers vary by college tier and location - treat this as a reported range, not a guarantee.
Coding: maximum sum subarray with at most k elements, and cloning a graph with random pointers. Both needed all test cases passing, not just a partial solution.
Work-simulation module: email-style prompts on prioritizing conflicting tasks and responding to a customer escalation.
Behavioural MCQs framed around ownership and customer obsession - no free text, just scenario choices.
Virtual onsite - coding
Design a data structure supporting insert/delete/getRandom in O(1) - hashmap + array-list approach.
Longest substring with at most k distinct characters (sliding window), with a follow-up on optimising space.
A Leadership Principle question slipped in mid-round: “Tell me about a time you went above and beyond for a customer.”
Virtual onsite - design
Design a bookstore system (OOD): classes, relationships, methods, then a follow-up on handling concurrent orders.
Bar Raiser
Design an LRU cache (medium-hard), then “How would you scale this bookstore system to millions of users?”
Multiple deep follow-ups on a “took ownership of a project” story - the interviewer kept asking “what else did you consider, and why not that instead?”
Result: Selected
What helped: A distinct story for each Leadership Principle question rather than recycling the same “led a project” anecdote across rounds.
OA coding leaned harder on graphs: Word Ladder-style shortest transformation, and merging k sorted lists.
The design round asked for a simplified Twitter-style feed instead of a bookstore - same OOD depth, different domain.
The Bar Raiser mixed one graph problem with unusually deep behavioural probing on a single “disagreed with a decision” story - three separate follow-up questions on that one answer.
Mistakes that hurt other candidates in the same drive
Treating Leadership Principle questions as filler instead of real evaluation criteria in the technical rounds
Reusing the same STAR story across two different rounds - Bar Raisers can see prior interviewer feedback
Jumping into the design round without asking about scale or constraints first
Result: Selected
Takeaway: Amazon’s technical bar is real, but a thin, memorized Leadership Principles story falls apart faster here than a slightly rougher technical answer with a clear thought process.
Solve the OA’s coding problems for all test cases, not just the visible ones - partial credit is less forgiving here.
Treat the work-simulation module as a real evaluation, not a formality - it’s scored against the Leadership Principles too.
Prepare a different STAR story for each Leadership Principle you’re likely to be asked about, and never repeat one across rounds.
For design rounds, ask about scale and constraints before sketching a solution - Amazon interviewers note candidates who jump straight to an answer.
In the Bar Raiser, expect the interviewer to keep pulling on one story with “what else did you consider” - have real alternatives ready, not just the option you picked.
Amazon doesn’t run a separate generic HR round - Leadership Principles evaluation is spread across every stage, and the Bar Raiser doubles as the deepest behavioural check. Prepare STAR frameworks for the Leadership Principles on the dedicated page.