Amazon Engineering Manager 360 Review Template with Examples

In the Amazon S3 hiring committee on March 12 2024, the senior TPM slammed the whiteboard when the candidate spent ten minutes describing the UI of a new bucket‑lifecycle feature without mentioning latency, cost‑optimization, or the “two‑pizza team” ownership model.

The hiring manager, Maya Tran, interrupted: “You’re not evaluating the candidate’s ability to think at scale, you’re reciting design details.” The committee voted 4‑2 to reject the candidate, not because the design was flawed, but because the judgment signal—how the candidate framed impact—was missing. The lesson is that a 360 review must capture judgment, not just activity.

How should an Amazon Engineering Manager 360 review be structured?

The template must start with a one‑sentence impact summary that quantifies the manager’s contribution to business metrics, then follow a three‑column grid: Leadership Principles, concrete evidence, and reviewer rating. In the Q3 2024 Amazon Prime Video promotion cycle, the template used a header that read “Drove 15 % increase in streaming uptime for 8 M concurrent users, saving $12 M annually.” Below, the first column listed “Customer Obsession” and “Ownership,” the second column cited a specific project (the “Live‑Cache Redesign”) with a measurable KPI (99.9 % cache‑hit rate), and the third column recorded a 5‑point rating from the direct report.

The structure forces reviewers to tie every bullet to a leadership principle, preventing vague praise. Not a list of responsibilities, but a narrative of outcomes, is what senior leadership looks for when they scan a 360.

What concrete metrics do Amazon reviewers expect in a 360 review?

The review must include at least three hard numbers: a performance KPI, a cost impact, and a team‑size change, each tied to a Leadership Principle. In the Amazon Alexa Shopping debrief on May 2 2024, the EM’s 360 showed a 22 % reduction in checkout latency (Customer Obsession), a $4.3 M reduction in AWS spend (Think Big), and a growth from 10 to 14 engineers under his mentorship (Hire and Develop the Best).

The reviewers used the “Metrics Rubric” that Amazon’s internal HR portal provides, which assigns a weight of 0.4 to KPI magnitude, 0.3 to cost impact, and 0.3 to people‑development evidence. Not a vague “improved performance,” but a triple‑metric proof point, is what separates a pass from a marginal rating in the final committee vote of 5‑1.

> 📖 Related: comparison-of-tech-lead-roles-at-amazon-vs-google

Which Amazon Leadership Principles most heavily weight the 360 score?

Customer Obsession, Ownership, and Hire & Develop the Best together account for 70 % of the overall rating, according to the “Leadership Principles Scoring Matrix” used in the Seattle office during the Q2 2024 hiring cycle.

In a debrief for a senior EM overseeing the Amazon S3 lifecycle service, the hiring manager, Luis Gomez, highlighted that the candidate’s 360 earned a perfect 5 for Ownership because the reviewer cited a specific incident where the manager “took the initiative to redesign the multipart upload flow, cutting average upload time from 8 seconds to 3 seconds.” The matrix gives a 0.5 multiplier to any principle that appears in more than two reviewer comments. Not a generic “good leader,” but a demonstrated alignment with the top three principles, decides the final promotion recommendation that later translated into a $210,000 base salary plus 0.04 % RSU grant and a $30,000 sign‑on for the senior EM role.

How does the 360 review affect compensation and promotion timing?

The completed 360 feeds directly into the Amazon Compensation Calculator, which determines base, RSU, and sign‑on amounts within a 45‑day decision window after the review submission. In the Q4 2023 promotion round for a Mid‑Level EM on the Amazon Marketplace team, the calculator produced a $187,000 base, 0.03 % RSU, and $25,000 sign‑on package because the 360 earned a 4.2 average rating across all principles.

The review’s timestamp also triggers the “Promotion Eligibility Clock” that opens a six‑month promotion window; missing the window by even two days caused the candidate’s promotion to be deferred to the next cycle, a cost of roughly $15,000 in lost equity. Not a vague “good performance,” but a precise rating and timely submission, are the levers that control compensation outcomes in Amazon’s engineering ladder.

> 📖 Related: Google vs Amazon AI-Augmented Performance Reviews for IC Engineers: Key Differences and Adaptation Strategies

What are the common pitfalls that cause a 360 review to be rejected?

The most frequent rejection reason is a mismatch between evidence and the Leadership Principle it is supposed to support, as illustrated in the Amazon Robotics debrief on January 18 2024 where a reviewer attached a “team‑building lunch” anecdote to the Ownership principle and the committee voted 4‑2 to downgrade the rating. The second pitfall is over‑reliance on self‑served data; a senior EM submitted a 360 that quoted internal metrics from a private dashboard without providing the public‑facing impact, leading to a 3‑3 split vote and a “needs revision” flag.

The third pitfall is a lack of reviewer diversity; the template requires at least three distinct reviewer types (direct report, peer, skip‑level) and the absence of a skip‑level comment caused a 5‑1 rejection in the Amazon Advertising team’s Q1 2024 cycle. Not a superficial endorsement, but a rigorously mapped evidence set, determines whether the 360 survives the committee.

Preparation Checklist

  • Draft the one‑sentence impact headline using the exact wording from the quarterly business review; the PM Interview Playbook covers “Impact‑First Summaries” with real debrief examples from Amazon S3.
  • Pull three hard metrics (KPI, cost, headcount) from the last six months of CloudWatch dashboards; ensure each metric aligns with a specific Leadership Principle.
  • Secure written comments from at least one direct report, one peer, and one skip‑level manager; the reviewers must be on the official Amazon review roster.
  • Populate the three‑column grid (Principle, Evidence, Rating) using the internal “Leadership Principles Scoring Matrix” template stored in the HR portal under ID LPS‑2024‑07.
  • Review the draft with the HR Business Partner (e.g., Priya Desai) at least 48 hours before the submission deadline to catch any rubric mismatches.
  • Attach a one‑page “Risk Mitigation” addendum that quantifies the manager’s response to the “2023 AWS Outage” incident, citing the exact 2‑hour recovery time.
  • Submit the completed 360 through the Amazon Internal Review System (IRS) by the 10th of the month; late submissions are automatically downgraded by one rating point.

Mistakes to Avoid

  • BAD: Listing “Managed a team of engineers” without any metric. GOOD: “Managed a team of 12 engineers, reducing sprint cycle time from 3 weeks to 2 weeks, delivering $4 M of feature value.”
  • BAD: Attaching a generic “Great leader” comment to the Ownership principle. GOOD: “Took ownership of the “Live‑Cache Redesign” project, cutting latency by 62 % and saving $1.2 M annually.”
  • BAD: Submitting the 360 with only two reviewer types. GOOD: Including direct‑report, peer, and skip‑level comments, each referencing distinct Leadership Principles, which satisfies the three‑reviewer rule.

FAQ

  • What is the minimum rating a senior EM must achieve to be eligible for promotion? The candidate must average at least 4.0 across all Leadership Principles; a 3.9 average triggers an automatic “needs improvement” flag regardless of tenure.
  • How long does the promotion decision take after the 360 is submitted? Amazon’s promotion committee has a 45‑day decision window; extensions beyond that period are rare and require executive sponsorship.
  • Can I use a template from a different Amazon team, like Amazon Go, for my EM review? No, each product area has its own KPI set; copying a template without adapting the metrics to your team’s domain will be rejected by the reviewers.amazon.com/dp/B0GWWJQ2S3).

Related Reading

How should an Amazon Engineering Manager 360 review be structured?