1on1 at Amazon: How to Navigate Perf Review and Feedback

The moment the manager opened the calendar invite and said “let’s talk about your FY23 review,” the room felt less like a conversation and more like a forensic audit. In that three‑minute opening, I realized the 1on1 was the final gate for my rating, compensation band, and future project allocations.

What should I focus on during a 1on1 performance review at Amazon?

The answer is to align every anecdote you share with the specific Amazon Leadership Principle that the reviewer is scoring. In a Q2 review, my manager asked why my “customer obsession” score was low; I answered by mapping three concrete metrics—order‑to‑delivery latency, NPS improvement, and a cost‑avoidance initiative—that directly demonstrated the principle. The framework is simple: pick the principle, list the metric, describe the impact, and tie it to the Narrative.

During the debrief, the senior PM on the hiring committee reminded me that the written Narrative is the only artifact the Compensation Committee sees. The judgment was clear: if the Narrative does not quantify impact, the rating defaults to “Meets Expectations.” The consequence is a 5‑10 % lower base salary range, often $150,000 instead of $165,000 for a senior PM in Seattle.

Not a casual chat, but a data‑driven audit, the 1on1 forces you to surface the numbers you usually keep in a spreadsheet. Prepare a one‑page table that shows date, principle, metric, and outcome before the meeting; it will survive the manager’s “any other highlights?” question without you scrambling.

How does Amazon’s feedback loop differ from other tech firms?

The answer is that Amazon embeds feedback into a four‑stage loop that terminates in a written Narrative, whereas most firms rely on verbal summaries that never become part of the compensation record. In my experience, the loop begins with a “mid‑cycle check‑in” 90 days after the last review, proceeds to a “peer calibration” meeting with three peers, moves to a “manager synthesis” on day 150, and ends with a “final Narrative sign‑off” on day 180.

The counter‑intuitive truth is that the mid‑cycle check‑in is not a performance improvement plan; it is a data‑collection sprint. During my check‑in, the manager asked for a “single metric that best illustrates your contribution.” I delivered a 2.3 % reduction in cart abandonment, which later became the headline of my Narrative.

Not a vague “how are you doing?” but a structured request for a quantifiable story, the loop makes every 1on1 a milestone rather than a catch‑up. If you treat it as the latter, you will leave the Narrative empty, and the Compensation Committee will interpret the silence as risk, often capping you at the lower end of the band ($140,000 for a senior engineer).

When is the right time to raise concerns about my rating?

The answer is to raise concerns immediately after the manager’s “rating justification” email, not after the final Narrative is locked. In the Q3 cycle, my manager emailed me a rating of “Meets Expectations” on day 165. I replied within two hours, citing two missed projects that had delivered $1.2 million in incremental revenue. The senior director, who reviews the Narrative on day 175, escalated my case to the Compensation Committee because the objection was timely.

The insight is that Amazon’s internal policy treats any rating dispute filed after day 180 as “post‑review,” which automatically disqualifies you from compensation adjustments. The policy is not a procedural hurdle; it is a strategic deadline that aligns with the quarterly budget cycle.

Not a polite after‑thought, but a deadline‑driven escalation, the timing determines whether you can shift from a 5 % to a 12 % salary increase (e.g., $158,000 to $177,000 for a mid‑level PM). Miss the window, and you settle for the default band.

Why does the written Narrative outweigh verbal praise in Amazon reviews?

The answer is that the Narrative is the only document that the Compensation Committee, the Board, and future hiring managers will ever read. In a recent debrief, the hiring manager pushed back because the manager’s verbal praise was not reflected in the Narrative; the manager’s “great teamwork” comment never appeared in the written section, and the rating was downgraded to “Weakly Meets.”

The organizational‑psychology principle at play is “recorded accountability”: when a statement is recorded, it becomes a binding contract. Verbal praise can be forgotten or reinterpreted, but the Narrative is immutable. That is why Amazon requires the manager to sign off on a five‑page document that includes a “Calibrated Rating” table and a “Future Potential” paragraph.

Not a fleeting compliment, but a permanent record, the Narrative drives both promotion eligibility and equity grant size. Senior engineers who secure a Narrative that cites a $3 million cost‑savings project often receive an equity award of 0.03 % of the company, translating to $70,000 in value at the time of grant.

How can I leverage the 1on1 to influence my next compensation band?

The answer is to treat the 1on1 as a negotiation touchpoint where you explicitly connect your impact metrics to the band’s upper range. In my FY23 review, I presented a three‑slide deck: slide one showed a 15 % increase in feature adoption, slide two quantified a $2.5 million revenue uplift, and slide three mapped those outcomes to the “Deliver Results” principle, which directly correlates with the “High Performer” band ($170,000–$190,000).

The framework is the “Impact‑Band Alignment Matrix”: list the band range, identify the top three principles for that band, and match each principle with a metric you own. The matrix forces the manager to see the logical path from impact to compensation.

Not a vague request for a raise, but a data‑backed case that the manager must justify, the 1on1 becomes the moment you secure the narrative language that triggers the higher band. The result in my case was a promotion to “Senior PM” with a base of $182,000 and a 0.04 % equity grant, rather than staying at $165,000.

Preparation Checklist

Draft a one‑page table that links each Amazon Leadership Principle you plan to discuss with a concrete metric and the resulting business impact.
Review the manager’s last Narrative and note any missing principles; prepare a brief “fill‑in” story for each gap.
Practice a three‑sentence script that starts with the principle, follows with the metric, and ends with the impact (“Leadership Principle X, Y metric, Z outcome”).
Align your impact stories with the upcoming compensation band ranges ($150,000–$180,000 for mid‑level PMs, $170,000–$200,000 for senior PMs).
Anticipate the manager’s “any other highlights?” question and have a backup story ready that demonstrates cross‑functional influence.
Work through a structured preparation system (the PM Interview Playbook covers the “Impact‑Band Alignment Matrix” with real debrief examples).
Schedule a 30‑minute rehearsal with a peer who can role‑play the manager’s objections and enforce the data‑first approach.

Mistakes to Avoid

BAD: Treating the 1on1 as a casual check‑in and speaking in anecdotes without metrics. GOOD: Opening with a quantified statement (“Reduced checkout latency by 12 %”) and then mapping it to the relevant principle.

BAD: Waiting until after the Narrative is locked to raise a rating dispute, which the policy treats as “post‑review.” GOOD: Responding within 24 hours of the rating email, citing specific deliverables and their dollar impact, forcing a re‑calibration before day 180.

BAD: Relying on verbal praise from peers that never appears in the written Narrative, leading to a lower compensation band. GOOD: Ensuring every piece of peer feedback is captured in the Narrative’s “Collaboration” paragraph, complete with a metric (e.g., “Co‑led a cross‑team effort that delivered $800 k of incremental revenue”).

FAQ

What if my manager refuses to update the Narrative after I present my metrics?

The judgment is to escalate to the senior director within the 10‑day window after the manager’s rating email; the senior director has authority to override the Narrative if the data is solid.

Can I request a higher compensation band if my impact is above the typical range for my level?

Yes, but you must embed the higher‑band justification in the “Future Potential” paragraph of the Narrative; otherwise the Compensation Committee will default to the standard band for your title.

Is it worth bringing up a missed project that was delayed due to external factors?

Only if you can quantify the eventual value once the project resumes; the judgment is to frame the delay as a risk mitigation story, not an excuse, and tie it to the “Bias for Action” principle.amazon.com/dp/B0GWWJQ2S3).

Your next 1:1 doesn't have to be awkward.

Get the 1:1 Meeting Cheatsheet → — scripts for tough conversations, promotion asks, and managing up when your manager isn't great.