Just finished my Amazon TPM loop in March 2026. Six rounds total: phone screen with the recruiter, then a hiring manager conversation, then four onsite rounds with a mix of TPMs, an SDE, and a senior PM. No system design round in the traditional SWE sense, but one round was explicitly 'technical depth' and they wanted me to go deep on a past system I'd built or managed.
The behavioral side is all LP (Leadership Principles), as expected. What surprised me: they weren't satisfied with STAR stories that ended neatly. Every interviewer dug in with 'what would you have done differently' or 'how did you know that was the right tradeoff.' The ones where I got caught flat-footed were the ones where I'd wrapped my story up too tidily.
For the technical depth round, I walked through a cross-team platform migration I'd owned. They wanted: scope, dependencies, how I built the schedule, how I handled slippage, what data I used to make tradeoff calls. The SDE in the room asked clarifying questions about the architecture. It's not a coding interview, but if you can't discuss your system's tradeoffs at an L5-SDE level you will lose credibility fast.
A few specifics on what landed: Concrete numbers in every story. Not 'we reduced latency' but 'we reduced p99 from 800ms to 140ms over 8 weeks.' Calling out where you specifically drove something vs. where you facilitated. Amazon TPMs own outcomes, not just coordination. 'Working backwards' framing actually matters here. I got asked explicitly 'how do you start a new program' and the answer they want is: start from the customer/stakeholder goal, not from the engineering constraints.
Where I saw the line between pass and borderline: ambiguity handling. Got asked something like 'product team wants to ship in 6 weeks, engineering says 14 weeks minimum, and you have no authority over either team.' The answer is not 'escalate to manager.' They want to hear how you gather data, run a structured tradeoff, and build alignment from the bottom up.
Loop to offer was about 3 weeks. Recruiter communication was decent, not great. Happy to answer specifics in the replies.