1p3a Experience · May 2026

amazon software engineer intern tech phone screen experience

SWE Phone Screen Intern
1 upvote

Interview Experience

最近刚通过的amazon phone screen,主要是做题,之前亚麻的面经可以参考 BQ 处理和同事之间的矛盾。注意earn trust —> 方案需要重做怎么办?会和manager同步吗? Challenge project,回答时要想到正式实现前有没有考虑其他方法?有没有和别人讨论过方案? Coding:并查集经典题, 给定若干节点和边,判断图里有多少个连通分量。intern考这个说真心话很多同学都没咋复习这块。当时用了最优解法:带路径压缩 + 按秩合并,实现 find、union 两个核心函数。初始化每个节点自己是父节点。遍历每条边,把两个节点合并。合并前检查是否已经连通,用来判断环。最后统计连通分量数量。

Full Details

🔒

Unlock all Amazon questions

Full insider details, leaked discussions, and candidate experiences.

Get full access — from $50/mo

About Amazon Interview Reports

This question was reported by a candidate who interviewed at Amazon. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.

Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Amazon are the higher-signal extractions to take from this report.

For broader preparation context, the Amazon interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.

How To Practice This Type of Question

Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.

Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Amazon reports consistently are the ones worth investing in; one-off niche problems are not.

During Your Amazon Round

Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.

The single most predictive failure mode in Amazon reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.