Find a lesson, question or project

Start typing to search published content and planned structures.

↑ ↓ moveEnter openEsc close

Amazon / AWS interview research

Candidate accounts · 3 scoped accounts · 12 reported questions/topics

Snapshot: 1 October 2026 · Software/backend focus · No live fetching

Self-reported accounts, not employer-confirmed. Preserve the stated role, team and location; this sample does not establish company-wide patterns or question frequency.

Questions people reported

Named problems, reported variants and broad topics are different kinds of evidence. Related practice links are not proof that the exact problem was asked. Some prompts were withheld; we do not invent their details.

Topics in these accounts: Coding · Design · Practical coding

SDE II; Bengaluru, India

Aug 2026 · Interview date · Month only

Read the original candidate account

A candidate described graph follow-ups, low-level design, configuration-sync design and Leadership Principles throughout the loop.

Scope and source limitations

Keep this employer-specific role, date and region scope. Candidate reports are self-reported, not employer-confirmed.

This account was retained from the existing reviewed dataset and was not fully reread in the 1 October research pass.

  • BFS problem extended to multiple starting points

    Coding · Reported topic

    A custom problem gained multi-source traversal requirements.

  • Find the Safest Path in a Grid variant

    Coding · Reported variant

    The author compared the problem with this LeetCode question.

    Related practice: Find the Safest Path in a Grid

  • Package-return drop-store booking

    Design · Reported topic

    Model return slots and discuss finding a nearby drop location.

  • Synchronize configuration across devices

    Design · Reported topic

    A custom system-design discussion; full requirements were not published.

SDE II / L5; Location not stated

Feb 2026 · Interview date · Month only

Read the original candidate account

The report combines interval/range-update coding, systems design, object-oriented design and detailed behavioral follow-ups.

Scope and source limitations

Keep this employer-specific role, date and region scope. Candidate reports are self-reported, not employer-confirmed.

This account was retained from the existing reviewed dataset and was not fully reread in the 1 October research pass.

  • Car Pooling variant

    Coding · Reported variant

    The follow-up asked for a faster range-update solution.

    Related practice: Car Pooling

  • Real-time error-log monitoring

    Design · Reported topic

    Discuss ingestion, alerting and backpressure.

  • Vending-machine leasing system

    Design · Reported topic

    Model responsibilities and machine states.

  • Distributed rate limiter

    Design · Reported topic

    The discussion included token buckets and concurrent updates.

SDE II; Redmond, United States

27 Jun 2026 · Publication date; interview date not confirmed

Read the original candidate account

A US candidate reported practical coding, a storage-system design round, behavioral questions and an AI-assisted refactoring assessment.

Scope and source limitations

Keep this employer-specific role, date and region scope. Candidate reports are self-reported, not employer-confirmed.

This account was retained from the existing reviewed dataset and was not fully reread in the 1 October research pass.

  • Binary-tree inorder traversal

    Coding · Reported topic

    A phone-screen traversal question.

    Related practice: Binary Tree Inorder Traversal

  • Inventory stock management

    Practical coding · Reported topic

    Object-oriented code, corner cases and telemetry were discussed.

  • Object storage like Amazon S3

    Design · Reported topic

    The author described a whiteboard discussion of read/write flows.

  • Decode strings and handle follow-ups

    Coding · Reported topic

    Exact input constraints were not supplied.

    Related practice: Decode String

Additional independent, matching role/level/region reports are needed before claiming recurring patterns.

A suggested 14-day preparation plan

Authored practice, not the company’s syllabus. This general track is an editorial starting point, not a pattern inferred from all these reports. Confirm the format with your recruiter and adapt it to your actual level.

Backend correctness and Java/SQL depth

Balance DSA with transactions, indexes, API contracts, Java fundamentals, concurrency and failure recovery.

  • Days 1–2: hashing, prefix sums and interval/window exercises.
  • Days 3–4: Java collections, object contracts and concurrency tests.
  • Days 5–6: SQL joins/indexes; transaction isolation and locking examples.
  • Days 7–8: implement a reservation, ledger or workflow service.
  • Days 9–10: design retries, idempotency and asynchronous failure recovery.
  • Days 11–14: design mock, project debugging story and mixed final mock.
Practise an original design exercise

Design an order-processing service with safe retries.

This exercise is written for practice, not reported by a candidate. Define requirements, implement the smallest useful version, then test concurrency, retries and failure recovery where relevant.

Customize a timed role/level prep brief

The timed brief uses a narrower, date/level-filtered dataset. Broader accounts on this page are deliberately not substituted into those filters.

How this research was collected

Public candidate accounts, official guides and original editorial practice are kept separate. We did not copy paid question banks or scrape all of the internet. Cross-posts are not independent evidence; one source can describe more than one company. Unknown or index-only dates are not used to claim recency. Future expansion needs permitted fetching, deduplication and metadata review; this version remains a static snapshot.