Company questionsGroundworkAmazon

Global · interview process

Amazon

Amazon SDE hiring is an online assessment, then a loop of back-to-back interviews that each blend coding or design with Leadership Principle questions, including one Bar Raiser from outside the team. Design depth is light or absent in SDE-1 reports; the one SDE-2 report had separate LLD and HLD rounds.

  • 8 rounds
  • new-grad loops took roughly 3-4 months from OA to decision in 2025 per one guide; times are uneven
  • 3 design answers
  • 3 coding answers
  • 6 well-reported rounds
Start with round 1 Browse every question
  1. OA
  2. Screen
  3. DSA
  4. LLD
  5. System design
  6. Behavioural
  7. Bar raiser
  8. HR
  9. People rounds

The process, round by round

Reported by candidates and, where we found one, the company itself. Each round shows how well it is reported. Processes change by team, level and year.

  1. Online assessment

    Online assessmentabout 70-80 min coding, whole OA 2-3.5 hours

    Several reports

    Two coding problems, plus a work-simulation section (email-style prioritisation and debugging a business scenario) and a short work-style questionnaire pairing situations with most/least-fitting responses. One guide says the invitation link usually expires after about 7 days.

    • coding fundamentals
    • prioritisation and decision-making
    • alignment with Leadership Principles

    Varies: Reports mainly cover new-grad and SDE-1; experienced hires may differ. Section lengths vary by cycle and region.

    What can be asked in a online assessment round

    A timed test on a coding platform, taken alone. Usually two or three coding problems, sometimes with multiple-choice questions on CS basics, aptitude or SQL.

    • Array and string problems that need a hash map, two pointers or a sliding window

      Read the constraints first, because they point to the technique. If n is 100,000, an O(n^2) scan will time out, so look for a hash map, two pointers on a sorted array, or a window that moves forward only. Sketch the brute force, find the repeated work, then remove it. For two-sum style pairs you might say: I store each value's index as I scan, so the complement lookup is O(1) and the whole pass is O(n).

      DSA course →
    • Greedy and sorting problems with a catch in the constraints

      Greedy problems hide behind a sort. Ask what ordering makes the locally best choice safe, then try to argue why swapping two adjacent choices never helps. Interval scheduling is the classic case: sort by end time and take every interval that starts after the last chosen one. Check the catch in the constraints, such as overflow, ties or equal values, and test a tiny case by hand before submitting.

      DSA course →
    • A medium dynamic programming or graph-on-a-grid problem

      Decide whether the problem is a graph walk or a recurrence. On a grid, a shortest path with equal step cost is breadth-first search from the start, with a visited set so each cell is processed once, giving O(rows x cols). For dynamic programming, define the state in one sentence, write the transition, set the base cases, then see if only the previous row is needed to save space.

      DSA course →
    • SQL queries with joins and group by

      Start from the table that holds the thing being counted, join the others on their keys, filter rows with WHERE, group, then filter groups with HAVING. Remember that WHERE runs before grouping and HAVING after. Use LEFT JOIN when rows with no match must still appear, and COUNT of a column rather than star when nulls matter. Example: customers with more than three orders is GROUP BY customer_id HAVING COUNT(*) > 3.

      Databases →
    • Multiple-choice questions on OOP, operating systems, databases and networks

      These reward quick, accurate recall rather than long reasoning, so revise the short list of definitions that recur. Know the difference between a process and a thread, the four ACID properties, what an index trades for faster reads, TCP against UDP, and the four pillars of OOP. Eliminate two wrong options first, then choose. Do not spend more than a minute on any single question, and flag it to return to if time remains.

      Mock interviews →

    Prepare with: Book · Online assessmentDSA course

    4 sources for this round

  2. Technical phone screen

    Recruiter or phone screen45-60 min

    One report

    One guide describes a 45-60 minute call with an engineer: about 5 minutes of introduction, 35 on a coding problem and 10 on follow-ups. Amazon's page lists a phone screening stage without details, and the candidate reports I read for SDE-1 jump from the OA straight to the interview rounds.

    • problem solving
    • complexity analysis
    • edge cases

    Varies: Amazon says the process differs from role to role; the SDE-1 candidate reports read here did not include a phone screen.

    What can be asked in a recruiter or phone screen round

    A short call that decides whether you move on. Part resume and motivation, sometimes one easy coding or fundamentals question in a shared editor.

    • Walk me through your resume and your best project

      Give a two minute spine, not a life story: who you are now, the one or two projects that matter most, and why this role is the next step. Pick the best project and state the problem, your part, the technology and one measurable result. Keep every claim something you can defend if the next question digs in. You could open with: I am a backend engineer, and the project I am proudest of is the one where I cut checkout latency.

      Screening call chapter →
    • Why this company and why now

      The listener wants to know whether your reason is specific and sincere, not flattery. Name one or two real things about the product, the engineering problems or the team that you have looked at, then connect them to something you have done or want to learn. Why now should be about your growth, not escaping your current job. An opening could be: I have used the product, and the scaling problem it describes is the kind I want to work on.

      Screening call chapter →
    • Notice period, location and compensation expectations

      Give the facts that are true and keep the negotiation for later. State your notice period exactly as your contract says, and mention whether it can be shortened or bought out only if that is real. For compensation, say you would like to understand the role and level first, or give a researched range rather than a single anchor. Never invent a current figure. If you are asked directly, answer honestly and calmly.

      HR and the number chapter →
    • One easy or medium coding question, or a language fundamentals question

      Treat it as a short version of the full coding round. Repeat the problem back, ask about input size and edge cases, state a plan before typing, and talk while you code. For a language question, such as what a closure is or how a hash map handles collisions, give a one line definition and a tiny example. A good line is: first I will do the simple approach so we have something correct, then improve it.

      Tech phone screen chapter →

    Prepare with: Book · Screening callBook · Tech phone screen

    2 sources for this round

  3. Coding rounds in the loop

    Data structures and algorithms60 min each

    Several reports

    Often two problems per round (three of the four candidate reports; the fourth describes one problem per round), around medium difficulty (trees, strings, arrays, hash maps, graphs, sliding window). One guide says you write full programs including input parsing, and edge-case follow-ups are common. Reports often pair a coding round with a behavioural question.

    • data structures and algorithms
    • complete working code
    • optimising after a first solution
    • edge cases

    Varies: The single SDE-2 report shows one coding round with an optimisation follow-up plus separate design rounds; SDE-1 reports show one to three coding rounds.

    Practise for this round

    What can be asked in a data structures and algorithms round

    A live coding round of 45 to 60 minutes with one or two problems. You are judged on how you clarify, reason, code, test and state the complexity, not on the answer alone.

    • Arrays, strings and hashing: pairs, windows, frequency counts, prefix sums

      Name the pattern from the shape of the question. Pairs with a target use a hash map of seen values. A contiguous range with a condition uses a sliding window that grows on the right and shrinks on the left, so each element enters and leaves once, giving O(n). Range sums over many queries use a prefix sum array so each query is O(1) after O(n) setup. Count characters with a fixed-size array or map.

      DSA course →
    • Linked lists, stacks and queues, including design-a-structure problems such as an LRU cache

      For an LRU cache, combine a hash map from key to node with a doubly linked list ordered by recency. Get moves the node to the front, put inserts at the front, and when over capacity you remove the tail node and its map entry. Both operations are O(1), and you say why: the map finds the node, the list reorders it without a scan. For stacks, mention a monotonic stack for next greater element.

      DSA course →
    • Trees and BSTs, graphs (BFS, DFS, topological sort, shortest paths) and grids

      Decide the traversal from what is asked. Level by level or shortest path in an unweighted graph is BFS with a queue. Exploring all paths, components or cycles is DFS. A dependency order is topological sort: Kahn's algorithm repeatedly removes nodes with in-degree zero, and leftover nodes mean a cycle. Weighted shortest path with non-negative edges is Dijkstra with a heap, O((V + E) log V). On a BST, an in-order walk is sorted.

      DSA course →
    • Heaps and top-K, intervals, binary search on the answer

      For the K largest items keep a min-heap of size K: push each element and pop the smallest when the heap exceeds K, so the cost is O(n log K) and memory is O(K). For intervals, sort by start, then merge by comparing the next start with the current end. For binary search on the answer, define a yes or no check that is monotonic, such as can ship within D days, and search the capacity range.

      DSA course →
    • Dynamic programming from one dimension up to knapsack and string DP

      Define the state in a sentence, write the recurrence, fix the base cases, and decide the order of filling. Start with the recursive version with memoisation, then convert to a table. For 0/1 knapsack, dp[w] is the best value at capacity w, and in the one dimensional form you loop capacity downward so each item is used once. For string problems such as edit distance, the state is a pair of prefix lengths.

      DSA course →
    • Follow-ups: optimise space, handle streaming input, make it thread-safe

      Treat follow-ups as a chance to show depth, and answer in the same calm order each time. To save space, ask which previous rows or values the recurrence actually reads and keep only those. For streaming input, say what summary you can keep, such as a heap of size K or a running count. For thread safety, name the shared state, guard it with a lock, and keep the critical section short.

    Prepare with: Book · DSA roundDSA course

    4 sources for this round

  4. Low-level / object-oriented design

    Low-level designabout 60 min

    Several reports

    Design a small real-world system with classes and public methods, for example a parking lot or an elevator controller, then extend it with a new requirement such as priority scheduling. One fresher was rejected after this round and blamed limited OOP preparation.

    • object-oriented modelling
    • class and API design
    • extensibility

    Varies: Not guaranteed at SDE-1 (some candidates got none); clearly present in SDE-2 loops.

    Practise for this round

    What can be asked in a low-level design round

    An object-oriented design discussion: classes, interfaces, relationships and the patterns that keep them flexible. Often combined with machine coding.

    • Class design for a booking system, a notification service or a payment module

      Begin by listing the nouns and verbs from the requirements, then turn nouns into classes and group verbs by who owns the data. For a booking system you might have Resource, Booking, User and a BookingService, with a rule that two bookings for one resource cannot overlap. Draw relationships clearly: composition when a part cannot exist alone, an interface when behaviour varies. Say which classes you would write first and why.

      Whiteboard →
    • SOLID principles applied to your own classes

      Tie each principle to a concrete choice in your design rather than reciting the acronym. Single responsibility: the invoice class does not also send email. Open and closed: add a new payment method by adding a class, not editing a switch. Liskov: a subclass must honour the parent's contract. Interface segregation: small interfaces. Dependency inversion: the service depends on a notifier interface, not on an SMS client.

    • Strategy, observer, factory, state and builder patterns, and when each helps

      Know the problem each pattern solves. Strategy swaps an algorithm, such as pricing or routing. Observer lets many listeners react to one event, as in notifications. Factory hides which concrete class is created. State moves behaviour into a class per state, as in an order lifecycle. Builder assembles an object with many optional fields. Say when not to use one: a pattern with a single implementation is usually noise.

    • Concurrency inside the design: locks, thread-safe collections, idempotent operations

      Identify what is shared and mutable, then choose the smallest protection that works. Use a lock around a compound check-then-act, a concurrent map for independent keys, and atomic counters for simple tallies. For operations that may be retried, make them idempotent by carrying a request id and ignoring a repeat. Example: charging a booking twice is prevented by storing the request id with the result and returning it again.

    • Extending the design for a new requirement without breaking old code

      Show the design absorbing change. When a new requirement arrives, say which existing abstraction already covers it and which new class you add. If a discount rule appears, add a new implementation of the discount interface and register it. If you must change old code, explain why the original split was wrong and how you would limit the edit. Mention tests: existing tests should still pass unchanged after the extension.

    4 sources for this round

  5. High-level system design

    System designabout 60 min

    Several reports

    Design with no code required. The SDE-2 report covered a locker-based delivery system (locker status sync, location prioritisation, fail-safes, full lockers). An SDE-1 report was a bookstore service that counts word occurrences across many books, framed around classes and methods, followed by project discussion. A guide says SDE-1 design is basic if present.

    • component design
    • scalability and trade-offs
    • discussing past projects

    Varies: The one SDE-2 report had a dedicated round; at SDE-1 it is basic or absent in the reports and guides read.

    Practise for this round

    What can be asked in a system design round

    A 45 to 60 minute discussion of how to build a system at scale: requirements, numbers, APIs, data model, components, bottlenecks and trade-offs.

    • Short links, chat, news feed, notifications, search, rate limiting

      Use one repeatable path: clarify scope and scale, estimate load, define the API, sketch the data model, draw the main components, then probe bottlenecks. For short links, store a mapping from a generated short id to the long url, generate ids with a counter encoded in base 62, cache hot links, and note reads far outnumber writes. For chat, mention persistent connections and a store ordered per conversation.

      System design course →
    • Payments, wallets and ledgers where money must never be lost or doubled

      Money systems put correctness before speed. Use a double-entry ledger where entries are append-only and every transfer writes a debit and an equal credit in one transaction. Protect against doubled charges with an idempotency key stored with the result, so a retry returns the original outcome. For lost updates use a database transaction, and reconcile with the payment provider's records on a schedule.

      System design course →
    • Ride matching, maps and anything with live location

      Split the problem into location ingestion, a geospatial index and matching. Drivers send updates every few seconds to a write-optimised store, often in memory, keyed by a grid cell such as a geohash or S2 cell. To find nearby drivers, query the rider's cell and its neighbours, then rank by distance and estimated time. Say how you handle a stale location and a driver who accepts two rides.

      System design course →
    • File storage and sync, video streaming and content delivery

      For file sync, split files into chunks, hash each chunk and upload only chunks the server lacks, so a small edit transfers a small amount. Keep metadata in a database and chunks in object storage. For video, upload the original, transcode into several resolutions, store segments and serve them through a content delivery network with adaptive bitrate streaming, so the player switches quality as bandwidth changes.

      System design course →
    • Fundamentals: caching, sharding, replication, queues, consistency, failure handling

      Treat each as a tool with a cost. A cache cuts read latency but adds staleness and invalidation. Sharding spreads write load but makes cross-shard queries hard. Replication gives availability and read scale but introduces lag. Queues smooth spikes and decouple services but require idempotent consumers. For failures, name timeouts, retries with backoff and a fallback. State what you give up whenever you choose.

      System design course →
    • Back-of-envelope estimates and what they decide

      Estimates are there to choose a design, so finish each one with a decision. Use round numbers: a day has about 100,000 seconds, so 10 million requests a day is roughly 100 per second on average, with a peak of a few times that. Multiply object size by count for storage, and compare against one machine's capacity. If one database handles the load, say so and avoid sharding.

      Capacity estimation →

    Prepare with: Book · System designSystem design course

    3 sources for this round

  6. Leadership Principles behavioural questions

    Behavioural roundwoven into the other rounds

    Several reports

    One guide says each loop interviewer is assigned particular Leadership Principles. Candidate reports mention questions on pressure, missed deadlines, tight timelines, unclear requirements, doing something extraordinary for the team and acting against organisational standards. The same guide advises preparing about eight STAR stories.

    • ownership
    • customer obsession
    • dealing with conflict and deadlines
    • evidence of impact

    Practise for this round

    What can be asked in a behavioural round round

    Story-based questions about how you work. Prepare a few real stories you can reshape: the situation, your action and the result, with numbers where you have them.

    • A conflict, a failure, a deadline you missed and what you changed

      Use situation, task, action and result, spending most of the time on what you did. For a failure, own your part, say what you learned and show a concrete change that you kept, such as a checklist or a test. For a conflict, show you listened and focused on the goal. The listener checks honesty and growth. Start plainly: the situation was a release that slipped, and my part in it was an estimate I did not revisit.

      Behavioural chapter →
    • Leading without authority, mentoring, raising a hard issue

      The theme is influence without a title. Pick a real example where you persuaded others, taught a teammate or raised a risk early. Describe how you built agreement, with data, a small proof or a one page proposal, and what changed afterwards. Raising a hard issue means doing it early, privately where fitting, and with a suggested fix. Do not present someone else's work as your own.

      Behavioural chapter →
    • Ambiguity: a time you had to decide with little information

      Interviewers check how you decide when facts are missing. Describe how you reduced the unknowns: asked who could answer, ran a small experiment, chose the reversible option, and set a point to review. Explain what you decided, what risk you accepted, and the outcome, including if it turned out wrong. A fitting opening: nobody could tell us the real traffic, so I proposed a two week trial before committing.

      Behavioural chapter →
    • Customer or user focus, and an example of going beyond the brief

      Show that you understand who uses the work. Pick a real example where you looked at user feedback, support tickets or usage data and changed what you built, even when the ticket asked for something narrower. Describe the extra step you took, why it mattered to the user, and the result. The listener checks initiative and that it is grounded in evidence, not just effort.

      Leadership principles chapter →

    Prepare with: Book · BehaviouralBook · Leadership Principles

    4 sources for this round

  7. Bar Raiser

    Bar raiserabout 60 min

    Several reports

    An outside interviewer who combines behavioural scoring with a technical problem. In the one SDE-2 report the behavioural part probed ethical and organisational conflicts, and the coding part was a binary-tree bottom-view problem. A guide says some 2025 SDE-1 candidates got a basic design prompt here.

    • standards and judgement
    • depth on Leadership Principles
    • coding under follow-ups

    Varies: Amazon's page names Bar Raisers without describing the role. The SDE-1 candidate reports I read did not single one out.

    Practise for this round

    What can be asked in a bar raiser round

    An independent interviewer from outside the hiring team who judges you against the company's leadership principles, with the power to hold the bar.

    • Stories mapped to leadership principles such as ownership and customer obsession

      Prepare a handful of real stories and be ready to map each to more than one principle. Choose the story that fits the principle being probed. Use situation, task, action and result, speak in the first person about what you did, and include a measurable result where you have one. The listener checks that your behaviour matches the principle, not that you know its name.

      Leadership principles chapter →
    • Deep follow-ups on every claim in a story: what exactly you did, what the numbers were

      Expect repeated why and how questions on one story, to separate your own work from the team's. Know the details: the dates, the numbers, the alternatives you rejected, and who disagreed. Say we only when it is true, and I when it is you. If you do not remember a figure, say so and give your best estimate. Consistent detail is persuasive; invented detail collapses under the next question.

      Leadership principles chapter →
    • A technical or design question to confirm the level

      This is a shorter check that your technical level is real. Treat it like any design or coding question: clarify, state assumptions, give a simple solution first, then discuss trade-offs and failure cases. The listener looks for judgement, such as knowing what to leave out and when to be careful. Explaining your reasoning aloud matters more than a perfect final design.

      System design course →

    Prepare with: Book · Leadership PrinciplesBook · Behavioural

    3 sources for this round

  8. Recruiter follow-up and offer

    HR and offer

    One report

    Updates come by automated email or a scheduling tool, and one SDE-1 candidate learned of the result in a later HR call. Amazon's page also mentions a 'Candid Chat' with a member of an employee-led group during the process.

    • how updates are communicated
    • candid chat with employee group

    Varies: One 2025 SDE-1 report says no updates followed the final round until a later HR call.

    Practise for this round

    What can be asked in a hr and offer round

    The closing conversation: motivation, expectations, notice period, compensation and how the offer is structured. Prepared answers and a clear number help here.

    • Current and expected compensation, and how to answer without boxing yourself in

      Be honest and avoid giving a single number too early. Share your current pay only if you are comfortable, and make clear what is fixed and what is variable. For expectations, say you are flexible for the right role, and offer a researched range based on level and market. If pushed, state a figure you can justify. Never state a number you cannot support, because offers are often checked.

      HR and the number chapter →
    • Notice period, joining date and relocation

      Give the facts exactly as they are in your contract. State the notice period, whether early release or a buy-out is truly possible, and the earliest honest joining date. Do not promise a date your employer has not agreed to. For relocation, say whether you can move, how soon, and whether you would need support. Clear, early information helps the recruiter plan and shows you are reliable.

      HR and the number chapter →
    • Why you are leaving and what you are looking for

      Keep it positive and forward looking. Talk about what you want more of, such as larger scale, ownership or a stronger team, rather than criticising your current employer. The listener checks that you will not leave this job for the same reason. Opening line: I have learned a lot in the current role, and I now want to work on problems at a bigger scale.

    • Levels, equity and how the offer is built

      Ask for the structure rather than only the total. Find out the level and title, base salary, bonus and whether it is guaranteed, equity amount, vesting schedule and cliff, joining bonus and any clawback. Compare offers on a yearly total with the same assumptions. If equity is in a private company, ask how it is valued and what happens on leaving. Asking calmly is normal and expected.

      Levels and equity chapter →

    Prepare with: Book · HR & the numberBook · Levels & equity

    2 sources for this round

Preparing for the people rounds at Amazon

The hiring manager, behavioural and offer conversations. Candidate reports shape the themes; the answers and frames are written for this site, so use them as a structure and bring your own stories.

What Amazon says it valuesOfficial ↗

  • Customer ObsessionStart from the customer's need and work backwards; trust matters more than watching competitors.
  • OwnershipAct like an owner, favour long-term value, and answer for outcomes beyond your own team.
  • Invent and SimplifyLook for new and simpler answers, borrow ideas from outside, and accept being misunderstood for a while.
  • Are Right, A LotMake sound calls with judgement, seek views that contradict yours, and test your own beliefs.
  • Learn and Be CuriousKeep growing and follow your curiosity toward new possibilities.
  • Hire and Develop the BestRaise the bar with each hire and promotion, coach others, and help strong people move on.
  • Insist on the Highest StandardsHold demanding standards, keep raising quality, and fix defects at the root.
  • Think BigSet a bold direction that inspires people, since thinking small limits the result.
  • Bias for ActionSpeed matters and many decisions can be reversed, so take calculated risks without exhaustive study.
  • FrugalityDo more with less and treat constraints as a prompt for inventiveness, not a case for more budget.
  • Earn TrustListen, speak candidly, treat people with respect, own your flaws openly, and compare yourself with the best.
  • Dive DeepStay close to the detail, audit often, and question metrics or stories that disagree; no task is beneath you.
  • Have Backbone; Disagree and CommitChallenge decisions you doubt even when it is uncomfortable, then back the final call fully.
  • Deliver ResultsFocus on the inputs that drive the business, finish on time with quality, and keep going through setbacks.
  • Strive to be Earth's Best EmployerMake the workplace safer, more diverse and more equitable, lead with empathy, and support growth.
  • Success and Scale Bring Broad ResponsibilityWeigh the wider and second-order effects of a large company's actions and aim to do better.

Themes candidates report being probed

  • Ownership and going beyond the brief
  • Working under pressure
  • Missed deadlines and commitments
  • Unclear or changing requirements
  • Conflict with a coworker
  • Failure and how it was handled
  • Going above and beyond for a customer
  • Acting against organisational norms

Questions to rehearse

  1. Tell me about a time the requirements were unclear or kept changing, and what you did.Several reports

    What is being checked. Reported by a candidate (as an unclear requirement) and two guides (as changing requirements). It tests Bias for Action and Are Right, A Lot: whether you can decide and move with partial information, and learn from how it turned out.

    How to frame it. Use the situation, task, action, result structure, but spend most time on the actions: how you clarified what you could, what you decided without full information, and the result. Say "I" for your own steps. Opening to adapt: "The spec for [project] changed twice, so I wrote down my assumptions and confirmed them with [owner] before building."

    Candidate write-up ↗Prep guide ↗Prep guide ↗

  2. Tell me about a time you missed a deadline or could not meet a commitment.Several reports

    What is being checked. Reported by a candidate, and a guide lists the close prompt of a missed commitment. It tests Deliver Results and Earn Trust: whether you own a miss, say what it cost, and change your approach.

    How to frame it. Do not invent a save. State the commitment, why you missed it, when you told people, the business impact, and the specific practice you changed. Opening to adapt: "I committed to [date] for [deliverable], and I missed it because [reason], which cost [impact]."

    Candidate write-up ↗Prep guide ↗

  3. What is something you did for your team that went beyond your role?One report

    What is being checked. Reported by an SDE-2 candidate. It tests Ownership: whether you acted on a problem outside your remit and cared about the long-term result, not only your own tasks.

    How to frame it. Pick a problem nobody owned, explain why you acted, what you did beyond your job description, and what changed for the team afterwards, with a number if possible. Opening to adapt: "Nobody owned [problem] and it was costing [cost], so I took it on by [action]."

    Worked example in the Interview book →Candidate write-up ↗

  4. Tell me about a time you went against an organisational standard, and why.One report

    What is being checked. Reported by an SDE-2 candidate as a Bar Raiser-style probe. It tests Have Backbone, Disagree and Commit and Earn Trust: your judgement on when a rule should bend and how you handled the consequences.

    How to frame it. Choose a case where you raised the issue openly, had a clear reason (customer impact, a risk), and took responsibility for the result. Avoid stories that look like bypassing safety or ethics. Opening to adapt: "The standard said [rule], but I believed it would harm [customer], so I escalated to [person] and proposed an exception."

    Candidate write-up ↗

  5. Describe a conflict with a coworker and how you resolved it.Prep guides

    What is being checked. Two guides list it. It tests Earn Trust and Have Backbone: whether you can be candid and respectful and keep the relationship working after the disagreement.

    How to frame it. Describe the actual disagreement about the work, what you said directly to the person, what you changed in your own behaviour, and where you both ended up. Opening to adapt: "[Colleague] and I disagreed about [decision], so I asked to talk it through and brought [data]."

    Worked example in the Interview book →Prep guide ↗Prep guide ↗

  6. Tell me about a time you dug deep to find the real cause of a problem.Prep guides

    What is being checked. A guide lists a root-cause question. It tests Dive Deep and Insist on the Highest Standards: whether you went past symptoms, checked the data, and fixed the cause.

    How to frame it. Give the symptom, the first wrong theory, how you narrowed it (logs, metrics, reproduction), the cause, and the fix plus a check that it stays fixed. Include numbers. Opening to adapt: "The alert said [symptom], and the obvious fix did not hold, so I traced [metric] back to [cause]."

    Worked example in the Interview book →Prep guide ↗

  7. Tell me about a time you went out of your way for a customer.Prep guides

    What is being checked. A guide lists it, and Customer Obsession is the first principle. The listener checks whether you start from the customer's real need, even at some cost to your own plan.

    How to frame it. Name the customer (internal or external) and their actual problem, what you did that was not required, and how you knew they were better off. Avoid describing only a favour. Opening to adapt: "A customer was blocked on [problem] and the process would have taken [time], so I [action]."

    Prep guide ↗Official ↗

  8. Tell me about a failure and how you handled it.Prep guides

    What is being checked. A guide lists it. It tests Ownership and Learn and Be Curious: whether you take the blame, repair the damage, and change something lasting.

    How to frame it. Give a real failure with real consequences. Say what you owned, how you limited the damage, what you learned, and the mechanism you added so it cannot repeat. Opening to adapt: "I made the call to [action], and it failed because [reason], so I [recovery]."

    Worked example in the Interview book →Prep guide ↗

The offer conversation

  • Two guides describe the Bar Raiser, an interviewer from outside the hiring team, as able to veto a hire even when other interviewers back you, so the behavioural stories carry real weight.
  • One guide says most candidates finish the earlier steps in three to six weeks and that team matching after the loop can extend the total to about eight weeks; another gives four to eight weeks from first contact to offer.
  • General advice: ask which level is being offered, get the base, sign-on and stock breakdown in writing, and check your notice period and any buy-out before agreeing a start date.

What we could not verify. Amazon's own page does not map principles to rounds or give round counts. Most principle-level prompts come from guide lists rather than first-hand reports, the two first-hand reports are undated beyond their posting dates, and no compensation, India-specific HR or notice-period report was found.

What we could not verify. Amazon's role-specific SDE prep page returned 404. The Amazon Jobs page I read has no durations or round counts and no year. Medium posts and dsaprep.dev were unreadable. Loop size reports conflict (2 to 5 interviews). Only one SDE-2 candidate report was found, so SDE-2 claims are thin. No candidate source gave offer-stage mechanics or real timeline other than one guide's estimate.