← Amazon Interview Insights

Amazon·Software Engineer·Onsite - Multi Round·Junior

JuniorPrefer not to say
Apr 2026

Summary

Did Amazon, Meta, and Microsoft internship interviews this year and Amazon was by far the most brutal despite its reputation for being the easiest. Three 60-minute rounds with LP deep dives and two LC hard problems threw me off completely.

Questions Asked (3)

Q1

Solve a graph problem involving topological sort (LC hard difficulty).

Algorithms & Data Structures
Author's notes

Two of the three technical rounds had hard-level problems and this was one of them.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Clarify the problem constraints and edge cases, then identify it as a topological sort problem (likely requiring cycle detection). Discuss both Kahn's algorithm (BFS) and DFS-based approaches, explaining trade-offs, and implement the most suitable one with clear time/space complexity analysis.

Pro tip: Amazon values customer obsession and ownership: after solving, discuss how you'd handle large-scale inputs (e.g., streaming graph updates) and mention potential optimizations like parallel processing or early cycle detection to prevent downstream failures.

1. Understand and Clarify

Restate the problem in your own words, ask clarifying questions about input size, graph representation, and expected output (e.g., any valid order or lexicographically smallest).

2. Identify Approach

Recognize it as a topological sort problem; decide between Kahn's algorithm (BFS) and DFS-based topological sort, considering cycle detection and constraints.

3. Design and Analyze

Outline the algorithm step-by-step, including data structures (adjacency list, indegree array, queue/stack), and analyze time and space complexity.

4. Implement and Test

Write clean, modular code with meaningful variable names; walk through a small example and test edge cases like empty graph, single node, and cycles.

5. Optimize and Discuss Trade-offs

Discuss potential optimizations (e.g., using a priority queue for lexicographical order) and trade-offs between BFS and DFS approaches in terms of readability and performance.

Key Points to Mention

  • Topological sort is only possible for Directed Acyclic Graphs (DAGs); cycle detection is crucial.
  • Kahn's algorithm uses indegree and a queue; DFS uses recursion stack and post-order traversal.
  • Time complexity: O(V + E) for both approaches; space complexity: O(V + E) for adjacency list.
  • Edge cases: empty graph, disconnected components, self-loops, and multiple valid topological orders.
  • Amazon leadership principles: customer obsession (robustness), ownership (handling edge cases), and insist on highest standards (code quality).
  • Real-world applications: build systems, task scheduling, dependency resolution.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.

Q2

Solve a dynamic programming problem (LC medium difficulty).

Algorithms & Data Structures
Author's notes

The one medium in the bunch.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying the problem and constraints, then define the state and recurrence relation before coding. Implement the DP iteratively with optimizations, and test with edge cases while explaining time and space complexity.

Pro tip: Amazon values customer obsession and ownership; relate your DP solution to real-world scalability and efficiency, and proactively discuss trade-offs like space optimization to show you think beyond just passing tests.

1. Understand the problem

Ask clarifying questions to confirm input/output, constraints, and edge cases. Restate the problem in your own words to ensure alignment.

2. Define the DP state

Identify what each state represents (e.g., dp[i] = max profit up to i) and how it captures subproblems. Explain why this state is sufficient.

3. Derive recurrence relation

Formulate how to compute a state from previous states. Discuss base cases and initialization.

4. Implement and optimize

Code the solution iteratively, using memoization or tabulation. Consider space optimization if applicable (e.g., rolling array).

5. Analyze and test

Walk through time and space complexity, then test with provided examples and edge cases. Discuss potential improvements or alternative approaches.

Key Points to Mention

  • Optimal substructure and overlapping subproblems
  • State definition and recurrence relation
  • Time and space complexity analysis
  • Edge cases and constraints handling
  • Space optimization techniques (e.g., 1D array)
  • Trade-offs between top-down and bottom-up approaches

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.

Q3

Deep dive behavioral questions tied to Amazon's leadership principles, across all three interview rounds.

Adaptability & AmbiguityStakeholder Management
Author's notes

Every single round had these, not just one.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Prepare 6-8 STAR stories that map to Amazon's Leadership Principles, focusing on Adaptability & Ambiguity and Stakeholder Management. For each story, explicitly name the LP it demonstrates and quantify the impact. Practice delivering these stories concisely (2-3 minutes) and be ready to dive deep into any aspect.

Pro tip: Amazon interviewers are trained to probe for specifics—be ready to answer follow-up questions about your exact actions, metrics, and what you would do differently. Use the 'I' not 'we' to highlight your individual contribution.

1. Map stories to LPs

Identify 6-8 diverse experiences that showcase different Leadership Principles, especially Adaptability & Ambiguity and Stakeholder Management. Ensure each story has a clear Situation, Task, Action, and Result.

2. Structure with STAR

For each story, succinctly describe the situation and task, then spend most time on your specific actions and the measurable results. Highlight how you navigated ambiguity or managed stakeholders.

3. Quantify impact

Include metrics (e.g., % improvement, time saved, revenue impact) to make your results concrete. If exact numbers are unavailable, use reasonable estimates and explain how you measured success.

4. Practice deep dives

Anticipate follow-up questions that probe deeper into your actions, decisions, and learnings. Rehearse concise answers that provide additional detail without rambling.

5. Align with Amazon culture

Emphasize customer obsession, ownership, and bias for action in your stories. Show how you embody Amazon's peculiar ways of thinking and working.

Key Points to Mention

  • Specific examples of navigating ambiguous situations with incomplete information
  • How you identified and managed key stakeholders, including conflicting priorities
  • Quantifiable results and business impact of your actions
  • Lessons learned and how you applied them to future projects
  • Alignment with Amazon Leadership Principles, such as Customer Obsession, Ownership, and Bias for Action
  • Your individual contribution versus team effort, using 'I' statements

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.