Amazon Full Stack Engineer Interview Questions (2026)

1. 1Online Assessment (SDE OA)60 minMedium

   Two timed coding problems plus a workplace-simulation and logic section; the main gate for freshers and India volume hiring.

2. 2Phone screen45 minMedium

   One coding problem plus 1-2 Leadership Principle STAR questions with an SDE.

3. 3Coding loop round60 minMedium

   DSA problem to working code, followed by assigned-LP behavioral questions in STAR format.

4. 4System design loop round60 minHard

   Design an Amazon-scale service with capacity math, plus LPs; low-level/OOD design substitutes for junior candidates.

5. 5Hiring Manager round45 minMedium

   Team fit, project deep dives, and Deliver Results/Bias for Action stories with the manager you would report to.

6. 6Bar Raiser60 minHard

   An interviewer from outside the team stress-tests LP stories and overall bar with the hardest cross-examination of the loop; holds veto.

1. Q1

   You're building a returns API. How should a public API paginate large collections?

   IntermediateOnsite Loop — API/System DesignAPI Design

   How to answer: Use cursor pagination with deterministic ordering, page limits, next cursors, and documented consistency expectations. Validate with metrics and customer impact and operational excellence.

2. Q2

   You're building a inventory availability API. How would you design filtering and sorting without creating an unmaintainable API?

   IntermediateTechnical Screen — Integration DesignAPI Design

   How to answer: Expose a small supported filter set, validate sort fields, document indexes, and reject unsupported combinations clearly.

3. Q3

   You're building a order status API. When should you introduce a new API version?

   IntermediateBar Raiser Loop — Customer Contract TradeoffsAPI Design

   How to answer: Version only for breaking semantic changes; prefer additive fields and compatibility flags for nonbreaking evolution.

4. Q4

   You're building a seller catalog API. How would you design webhook delivery for external developers?

   IntermediateOnsite Loop — API/System DesignAPI Design

   How to answer: Sign payloads, retry with backoff, include event IDs, expose delivery logs, and make event payloads replayable.

5. Q5

   You're building a delivery estimate API. What should a consistent API error schema include?

   IntermediateTechnical Screen — Integration DesignAPI Design

   How to answer: Include stable error type, message, affected field, request ID, retryability, and links to docs when helpful.

6. Q6

   You're building a returns API. Which status codes would you use for validation, auth, conflicts, and rate limits?

   IntermediateBar Raiser Loop — Customer Contract TradeoffsAPI Design

   How to answer: Use 400/422 for validation, 401 unauthenticated, 403 unauthorized, 409 conflict, and 429 rate limit with retry metadata.

7. Q7

   You're building a inventory availability API. How would you communicate rate limits to API clients?

   IntermediateOnsite Loop — API/System DesignAPI Design

   How to answer: Return limit headers, reset windows, 429 bodies, retry-after hints, and separate quotas by client, token, and endpoint risk.

8. Q8

   You're building a order status API. How would an API handle a long-running export request?

   IntermediateTechnical Screen — Integration DesignAPI Design

   How to answer: Return 202 with an operation ID, expose status and result endpoints, emit webhooks, and make cancellation explicit. Validate with metrics and customer impact and operational excellence.

9. Q9

   You're building a seller catalog API. How would you define partial updates safely?

   SeniorBar Raiser Loop — Customer Contract TradeoffsAPI Design

   How to answer: Choose JSON Merge Patch or explicit fields, distinguish null from missing, validate transitions, and document idempotency.

10. Q10

    You're building a delivery estimate API. How would you design a bulk create endpoint?

    SeniorOnsite Loop — API/System DesignAPI Design

    How to answer: Accept bounded batches, return per-item results, support idempotency, handle partial failures, and document ordering guarantees.

11. Q11

    You're building a returns API. How would you keep API documentation accurate?

    SeniorTechnical Screen — Integration DesignAPI Design

    How to answer: Generate docs and SDKs from versioned OpenAPI specs, validate examples in CI, and require schema review for changes.

12. Q12

    You're building a inventory availability API. What changes are safe for existing API clients?

    SeniorBar Raiser Loop — Customer Contract TradeoffsAPI Design

    How to answer: Adding optional response fields is usually safe; changing types, meanings, required fields, or error behavior is breaking. Keep the design simple enough to operate and debug.

13. Q13

    You're building a order status API. What should live in an API gateway versus a service?

    SeniorOnsite Loop — API/System DesignAPI Design

    How to answer: Put cross-cutting concerns like routing, auth checks, rate limits, and request IDs at the gateway; keep business rules in services.

14. Q14

    You're building a seller catalog API. How would you model permissions for API clients?

    SeniorTechnical Screen — Integration DesignAPI Design

    How to answer: Use least-privilege scopes, tenant boundaries, explicit resource checks, and separate user-delegated tokens from machine credentials.

15. Q15

    You're building a delivery estimate API. How do you make every API request tenant-safe?

    SeniorBar Raiser Loop — Customer Contract TradeoffsAPI Design

    How to answer: Derive tenant from trusted auth context, never request body alone, enforce scoping in queries, and test cross-tenant denial. Validate with metrics and customer impact and operational excellence.

Practice these with instant AI feedback in a live mock interview → Start a Amazon Full Stack Engineer mock

Prepare 8-12 STAR stories mapped to Leadership Principles; expect a Bar Raiser; quantify impact

Other roles at Amazon

Full Stack Engineer interviews at other companies