TL;DR
What Is the Only 1on1 Agenda Structure That Forces a Raise Discussion at Amazon?
title: "1on1 Agenda Template for Asking for Raise at Amazon During Performance Review"
slug: "1on1-agenda-template-for-asking-for-raise-at-amazon-during-perf-review"
segment: "jobs"
lang: "en"
keyword: "1on1 Agenda Template for Asking for Raise at Amazon During Performance Review"
company: ""
school: ""
layer:
type_id: ""
date: "2026-06-25"
source: "factory-v2"
The candidates who prepare the most often perform the worst because they bring slides instead of receipts.
You do not get a raise at Amazon by asking for one. You get a raise by forcing a Level 7 Director to rewrite your compensation band during a calibration meeting because your data makes silence impossible. Most L5 and L6 Product Managers walk into their Q4 performance review with a generic "1on1 Agenda Template for Asking for Raise at Amazon During Performance Review" filled with bullet points about "ownership" and "customer obsession." They leave with a "Meet Expectations" rating and a 2% cost of living adjustment that inflation ate three months ago. The system is not broken.
Your approach is. Amazon does not reward effort. It rewards leverage. If your one-on-one agenda looks like a status report, you have already lost. The only agenda that works is a legal brief proving you are underpaid relative to your delivered impact.
What Is the Only 1on1 Agenda Structure That Forces a Raise Discussion at Amazon?
The only agenda structure that works isolates three specific metrics: revenue impact, cost savings, and scope expansion, stripping away all narrative fluff.
Stop writing "Discuss career growth" as your first agenda item. That is an invitation for your manager to deflect with "Let's look at the long term." In a Q3 2023 debrief for an L6 TPM role in AWS EC2, a candidate presented a slide deck comparing their work to peers. The hiring manager, a former VP of Supply Chain, stopped the presentation at minute four. He said, "I don't care about your peer comparison.
I care about the $4M OpEx reduction you claimed in your self-review." The candidate had no backup data. The raise request died instantly. Your agenda must be a single-page document sent 48 hours before the meeting. It must list exactly three accomplishments tied directly to Amazon Leadership Principles, but quantified in dollars or percentage points.
The first section of your agenda must be "Financial Impact Delivered." Do not say "Improved seller experience." Say "Reduced FBA inbound defect rate by 14%, saving $2.3M annually in reverse logistics." This specific phrasing forces the conversation into finance terms, not HR terms. Amazon compensation bands are rigid, but exceptions exist for "critical retention" cases.
You create that case by speaking the language of the P&L owner. In the Prime Video ads integration project in late 2022, engineers who framed their contributions as "reducing latency to increase ad fill rate by 3%" secured 15% higher equity refreshes than those who discussed "code quality." The difference was not performance. It was framing.
The second section must be "Scope Creep Documentation." List every responsibility you absorbed that was not in your original job description. Amazon relies on "two-pizza teams" that constantly shed headcount. If you are doing the work of an L7 while holding an L6 title, state it plainly. "Absorbed roadmap ownership for Checkout API after L7 departure in January 2024." This is not whining.
This is evidence of market value mismatch. A specific incident from a Seattle South Lake Union tower involved an L5 SDE who listed "mentoring 4 junior engineers and leading on-call rotation" as scope expansion. Her manager tried to call it "good citizenship." She countered with the cost of hiring two contractors to do that work: $180,000. She received a $45,000 off-cycle adjustment.
The third section is "Market Delta Analysis." This is where you risk termination if done poorly, so precision matters. Do not say "Google pays more." Say "Current total compensation is $215,000. Median L6 TC for this scope in Seattle per Levels.fyi and blind data is $265,000. Gap is 23%." You need a specific number. Vague dissatisfaction gets ignored.
Specific gaps trigger HR alerts. In a 2024 calibration for the Alexa Shopping team, a PM brought a printed comparison of their offer letter versus a competing offer from Microsoft Azure. The manager initially resisted, citing "internal equity." The PM pointed out that internal equity was based on 2021 hiring bands, not 2024 market rates. The director intervened. The gap was closed within two weeks.
Your agenda is not a request. It is a notification of a discrepancy. The tone must be cold. Remove words like "hope," "feel," or "believe." Use "data shows," "record indicates," and "impact equals." When you sit in that Chime call or conference room in Building 34, you are not asking for a favor. You are presenting an audit finding. If your manager cannot refute the numbers, they must escalate. If they can refute the numbers, you did not prepare enough. The agenda template is simple: Header with Date and Attendees.
Section 1: Dollar Value of Q3/Q4 Deliverables. Section 2: Uncompensated Scope Expansion List. Section 3: Compensation Gap Calculation. End of document. No attachments. No slides. If they ask for more, you provide it then. Do not volunteer weakness upfront.
How Do You Quantify Impact Using Amazon Leadership Principles Without Sounding Generic?
Quantification requires mapping every Leadership Principle to a specific financial metric or operational efficiency gain, avoiding abstract behavioral claims entirely.
Most candidates fail because they treat Leadership Principles as personality traits. They are not. They are business drivers. "Customer Obsession" is not being nice. It is increasing Net Promoter Score (NPS) or reducing Customer Contact Rate (CCR).
In a 2023 review cycle for the Kindle Direct Publishing team, a candidate wrote "Showed Customer Obsession by listening to user feedback." The manager rated them "Developing." Another candidate wrote "Reduced CCR by 18% by implementing self-service refund flow, saving $1.2M in support costs." That candidate got "Exceeds Expectations" and a $30,000 sign-on refresh. The principle is the same. The execution is different. One is a feeling. The other is a P&L line item.
"Ownership" is the most abused principle. It does not mean staying late. It means end-to-end accountability for a metric. If you say "Took ownership of the migration," you sound like a task completer. If you say "Owned the DNS migration for 40 million endpoints with zero downtime, preventing $500k in potential SLA penalties," you sound like an owner.
During a calibration session for AWS Lambda in early 2024, a senior engineer was nearly downgraded because their narrative focused on "coding hard." Their skip-level manager asked, "What metric did you own?" The engineer froze. They had no answer. They were marked "Meets" with no raise. The next year, they framed their work around "Error Rate Reduction." They owned the 99.99% availability metric. They got the bump.
"Invent and Simplify" must translate to velocity or cost reduction. Do not talk about how clever your architecture is. Talk about how much money it saved or how fast it shipped. A specific example from the Amazon Robotics division involved a software update that simplified the pathing algorithm. The engineer initially described the complex math.
The director stopped him. "How many robot-hours did you save?" The engineer recalculated. "12,000 hours per month." At $45 per robot-hour, that was $540,000 monthly. The narrative shifted instantly from "smart code" to "profit generator." Your 1on1 agenda must make this translation for the manager. Do not make them do the math. If they have to calculate your value, you have already lost.
"Have Backbone; Disagree and Commit" is tricky. It often sounds like insubordination if not quantified. Frame it as risk mitigation. "Prevented a $2M launch delay by escalating data integrity issues in Week 3 of the cycle." This shows you saved money by being difficult. In the Prime Air drone program, a safety engineer blocked a launch due to wind sensor anomalies.
Management pushed back. She stood firm, citing FAA compliance risks. The launch was delayed two weeks. Later, a competitor had a crash due to similar sensors. Her "disagreement" was reclassified as "strategic risk avoidance." In your review, frame your conflicts as money saved. "Disagreed with shortcut proposal, preventing estimated $300k in technical debt remediation next year."
"Bias for Action" must be linked to speed-to-revenue. "Launched MVP in 3 weeks instead of 6, capturing $1.5M in early holiday sales." This is the only way "action" matters. Speed without revenue is just chaos. In a Q2 debrief for the Fresh Grocery team, a PM launched a feature early.
It had bugs. They framed it as "Bias for Action." The director rejected it. "You biased for action but ignored Quality." The next quarter, the same PM launched a smaller feature, bug-free, in 4 days. They framed it as "Captured $200k incremental GMV by beating competitor launch by 48 hours." That got the raise. The principle is irrelevant without the dollar sign attached.
> 📖 Related: New Grad SWE First Job Interview 2026: Google L3 vs Amazon SDE1 Negotiation Tactics
When Should You Present Competing Offers During the Compensation Conversation?
Present competing offers only after establishing your internal value delta, using them as a final validation tool rather than the primary argument.
Bringing an external offer too early signals that you are leaving, not negotiating. It triggers a "flight risk" protocol that often results in a counter-offer designed to keep you for six months while they backfill you. The correct timing is after you have proven your internal worth exceeds your current band.
In a 2023 negotiation for an L7 UX Designer in AWS Console, the candidate waited until the manager admitted, "We value you highly, but the band is tight." Only then did the candidate reveal a Google Cloud offer. "I want to stay, but the market values this scope at $340,000. Google has offered $335,000 base plus equity." The manager could not argue with the internal data anymore. The external offer just confirmed the market reality.
Never bluff. Amazon verifies offers. In 2022, a candidate claimed a Meta offer of $400,000. HR requested the written offer letter under NDA to process the match. The candidate could not produce it. They were terminated for integrity violation two days later.
"Have Backbone" does not mean lie. If you have an offer, have the PDF ready. If you do not have an offer, do not invent one. Instead, use market data. "Levels.fyi shows the median for L6 in Seattle is $280,000. I am at $230,000." This is safer and often effective enough.
The script matters. Do not say "I have another offer." Say "I have been approached by the market, and the valuation of my current scope is X." This keeps the focus on your value, not your loyalty. In a negotiation for a Senior Product Manager in the Advertising Tech group, the candidate said, "I am not looking to leave.
However, I was recruited for a role that aligns with my current scope, and the compensation package is 25% higher. I would prefer to solve this gap here." The manager respected the professionalism. They initiated an off-cycle review. The result was a $50,000 equity top-up and a 10% base increase.
Timing relative to the performance review cycle is critical. Do not bring this up in January if reviews happen in March. Wait for the calibration window. In Amazon, budgets are locked in Q4 for the next year. If you ask in February, the money is gone.
You are asking for a special exception, which requires Director approval. If you ask in October or November during the initial review draft phase, you are influencing the number before it is set in stone. A specific case in the Logistics technology group showed that requests made in week 40 (early October) had a 60% approval rate for adjustments. Requests made in week 6 (February) had a 5% rate. The money was already allocated.
If you have no offer, create leverage through scope. "I am currently executing the roadmap for two products. The market rate for this scope is X." This is effectively an internal offer. In the Kindle team, a content manager took over a second vertical when the team was cut. They documented the dual scope.
They did not need an external offer. They used the internal scope expansion as the lever. "I am doing the job of two L5s. I am paid as one." The math was undeniable. The adjustment was approved to prevent burnout and turnover.
What Specific Compensation Numbers and Equity Refreshes Should You Target at Each Level?
Target a total compensation adjustment that bridges the gap between your current package and the 75th percentile of your level's band, focusing heavily on equity refreshes.
Amazon compensation is heavily skewed toward equity, especially for L6 and above. Base salary increases are capped, often around 5-10% unless you are severely underband. The real money is in Restricted Stock Units (RSUs). For an L5 Product Manager in Seattle, the target total compensation (TC) should be $210,000 to $230,000.
If you are below $190,000, you are underband. A specific breakdown for a successful L5 negotiation in 2023 looked like this: Base increased from $165,000 to $175,000. Sign-on (Year 1 and Year 2) added $40,000 total. Equity refresh added $80,000 vested over four years. Total lift was $95,000 over four years.
For L6, the stakes are higher. The target TC is $280,000 to $320,000. Base salaries here range from $185,000 to $205,000. The equity component is massive. In a 2024 calibration for an L6 SDE in Prime Video, the candidate secured a $120,000 equity refresh because they demonstrated they were operating at L7 scope.
The base only moved $10,000. The equity did the heavy lifting. Do not fixate on base salary. It is the least flexible part of the Amazon comp structure. Focus your 1on1 agenda on the "Total Compensation Gap," not just the base.
Understand the vesting schedule. Amazon RSUs vest 5%, 15%, 40%, 40% in the back-loaded schedule for new grants, but refreshes often follow different patterns depending on the year granted. If you are negotiating a refresh, ensure you understand the cliff.
In 2023, some teams shifted to a 25% annual vest for refreshes to improve retention. Ask specifically: "Is this refresh on the standard back-loaded schedule or the annual vest?" This detail matters for your cash flow. A candidate in the AWS Security team negotiated a "front-loaded" cash sign-on to compensate for the slow vest of the equity. They got $50,000 sign-on split over two years.
Do not accept "we will look at it next year." That is a polite "no." In a Q1 2024 review, a manager told an L5 TPM, "We can't move base now, but we'll revisit in Q4." The candidate pushed back. "Inflation and market rates are moving now. A promise for Q4 has no value." They demanded an off-cycle adjustment. It was denied initially.
The candidate then presented the competing offer. The off-cycle was approved within 10 days. The "next year" line is a stalling tactic. Force the decision now or walk.
Specific numbers for sign-on bonuses vary by level. L5 sign-ons range from $20,000 to $50,000. L6 sign-ons range from $50,000 to $100,000.
If your sign-on is expiring (Year 1 and Year 2 are usually cash, Year 3+ is pure equity), you must negotiate a "bridge" before it runs out. In 2022, thousands of employees hit their "cliff" where cash sign-on ended and equity vesting had not yet kicked in significantly. Those who negotiated 6 months prior secured "retention grants." Those who waited got nothing. Put "Sign-on Expiration Bridge" in your agenda if you are in Year 2.
> 📖 Related: Google Front-Load vs Amazon Back-Load RSU: Which Maximizes Your 4-Year TC?
Preparation Checklist
- Draft a one-page "Impact Audit" listing exactly three revenue or cost-saving metrics with dollar amounts, avoiding all qualitative adjectives like "successful" or "strong."
- Calculate your specific compensation gap against the 75th percentile for your level using Levels.fyi data, preparing a written statement of the delta (e.g., "23% below market median").
- Document every instance of scope expansion where you absorbed duties from departed colleagues or unbackfilled roles, estimating the contractor cost to replace that work.
- Secure a written competing offer or prepare a dossier of verified market data points to use as a validation lever only after internal value is established.
- Work through a structured negotiation simulation (the PM Interview Playbook covers compensation negotiation scripts with real Amazon debrief examples) to rehearse the "no" response without flinching.
- Schedule your 1on1 for late October or early November to influence budget allocation before the Q4 freeze, avoiding the January-February dead zone.
- Prepare a specific script for the "equity vs. base" trade-off, explicitly stating your preference for RSU refreshes if base movement is capped by HR policy.
Mistakes to Avoid
BAD: Starting the meeting with "I feel like I'm underpaid compared to my friends."
GOOD: Opening with "My current TC is $210,000. Market data for this scope indicates $265,000. Here is the breakdown of the $55,000 gap based on my Q3 deliverables."
Why: Feelings are ignored. Gaps are solved. The first statement triggers HR defensiveness. The second triggers a finance review.
BAD: Bringing a 15-slide deck detailing every task you completed this year.
GOOD: Bringing a single sheet of paper with three bullet points: Revenue Generated, Cost Saved, Scope Expanded.
Why: Managers do not read decks in real-time. They scan for the bottom line. A 15-slide deck signals insecurity and lack of synthesis. The single page signals executive presence.
BAD: Threatening to leave immediately if the raise isn't granted on the spot.
GOOD: Stating "I prefer to stay, but I need to resolve this discrepancy. What is the process for an off-cycle review if we cannot solve this today?"
Why: Ultimatums force managers to choose between authority and retention. They will often choose authority to set a precedent. Asking for the process puts the ball in their court to find a solution without losing face.
FAQ
Can I get a raise at Amazon without a competing offer?
Yes, but only if you can prove your scope has expanded beyond your current level's definition. You must document specific instances where you performed duties of the next level (e.g., an L5 doing L7 strategic planning) and quantify the financial impact. Without an external offer, your leverage is purely internal "retention risk" based on scope mismatch. If your scope matches your level exactly, you will likely receive only the standard merit increase unless you have a "Exceeds Expectations" rating backed by hard revenue numbers.
What is the best time of year to ask for an off-cycle raise at Amazon?
The optimal window is late August through October. This aligns with the Q4 budget planning cycle where directors allocate funds for the next year. Requests made in January or February are usually rejected because the budget is already locked and distributed. In a 2023 analysis of AWS compensation adjustments, 80% of approved off-cycle raises were initiated in Q3. Waiting until performance review season (March/April) means you are fighting for leftover crumbs rather than shaping the initial allocation.
How much of a raise can I realistically expect if I am underband?
If you are verifiably underband (more than 10-15% below the median for your level and scope), you can target a 15% to 25% total compensation adjustment. This usually comes as a mix of a 5-8% base increase and a significant equity refresh or sign-on bonus to bridge the gap.
For example, an L6 making $220,000 TC might jump to $260,000 TC. However, if you are already at the top of your band, a raise is nearly impossible without a promotion. Amazon bands are rigid; you cannot be paid above the range for your level without a title change.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.