1p3a Experience · May 2026

amazon fulltime software engineer tech phone screen experience

SWE Phone Screen newgrad
1 upvote 5 replies

Interview Experience

sde2 BQ:tight deadline。讲了个项目经历,面试官直接开始追细节,先问在里面具体做了什么,然后资源不够的情况下优先级是怎么排的。感觉亚麻 BQ 每一层都要想清楚,随时可能被深挖 以下内容需要积分高于 120 您已经可以浏览 Coding:一道偏难的BFS,类似这道 2d matrix ,面试的时候简化了一点,主要考 minimum steps 那块。

Full Details

🔒

Unlock all Amazon questions

Full insider details, leaked discussions, and candidate experiences.

Get full access — from $50/mo

About This Question

This is a candidate experience report from a amazon interview for a swe role (newgrad level) during the phone screen round reported in 2026.

It covers the following topics: Matrix .

Topics

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.