TL;DR
Why Does My Amazon Forte Review Show "No Evidence" for Promotion?
The candidates who believe their work speaks for itself get crushed in Amazon's Forte review. Your Forte feedback form isn't a performance review — it's a courtroom, and you're the defendant. Here's how to collect evidence that survives committee scrutiny.
Why Does My Amazon Forte Review Show "No Evidence" for Promotion?
Amazon's Forte system flags promotion candidates whose packages lack corroborating data. At the L5 to L6 boundary in 2023, over 40% of flagged cases cited "insufficient peer evidence" as the primary blocker — not performance gaps, not lack of impact. The system flags it because the promotion committee can't read minds.
In a Q4 debrief for an AWS infrastructure team, a hiring manager argued his IC had delivered a 30% latency reduction on DynamoDB. The committee rejected it. No peer had mentioned the project in their feedback. No cross-functional partner had tagged the work. The candidate had shipped, but the Forte system saw an isolated contributor, not a senior engineer scaling the org.
The judgment: Forte doesn't evaluate your work. It evaluates how your peers talk about your work. If nobody wrote it down, it didn't happen — at least not in ways that survive the committee room.
What Is the Forte Process and How Does Peer Feedback Work at Amazon?
Forte is Amazon's promotion documentation system. You submit a self-assessment. Your manager submits theirs. Then Forte pulls structured peer feedback from 5-8 colleagues you nominate — plus a mandatory Bar Raiser if you've been through a promotion panel before.
The peer feedback isn't freeform. Forte gives reviewers specific prompts: "Describe how this person demonstrated ownership beyond their scope." "Provide an example of this person raising the bar for the team." Reviewers rate impact, leadership, and delivery on a 1-5 scale with mandatory narrative justification.
In a 2022 AWS Amplify loop, a senior PM submitted feedback from 4 engineers and 1 designer. The Bar Raiser flagged that 3 of the 5 reviewers worked directly on her project. The feedback lacked cross-functional breadth. The committee chair noted: "This reads like a project retrospective, not a peer evaluation."
Your peer pool must include people outside your immediate team. Amazon wants evidence you influence outcomes beyond your direct reporting line.
> 📖 Related: Bias for Action vs Have Backbone: Amazon LP Conflict Resolution for PMs in 2026
How Do I Collect Strong Peer Feedback Before the Review Cycle?
Start 90 days before your self-nomination deadline. Not 60 days. Not 30. Ninety.
Draft your own evidence summary first. Don't wait for peers to guess what matters. In a 2023 Alexa shopping team promotion cycle, an L5 PM prepared a one-page "impact brief" — three columns: initiative, her specific contribution, measurable outcome. She sent it to 6 nominated peers with a 20-minute calendar block request. All 6 wrote feedback. Three explicitly referenced her brief in their narratives.
The script works:
"Hi [Name], I'm preparing for my L6 promotion package and would value your perspective. I worked on [X initiative] where I specifically [your contribution]. The outcome was [metric]. Can you share how you experienced my work on this — what did I do that you'd point to as raising the bar?"
That framing does three things: it gives reviewers concrete material, it signals what "raising the bar" looks like in your context, and it respects their time. Peers aren't your ghostwriters. They're confirmatory witnesses.
When Should I Start Gathering Evidence for My Promotion Package?
Six months before the cycle opens. Not during.
At Amazon, promotion cases are built in the open, over time. The L5→L6 jump requires demonstration of scope expansion, cross-functional influence, and bar-raising behavior across at least two quarters. If you start documenting in month six of a six-month window, your Forte package will read like a retrospective — and committees can tell.
In a Q2 2024 SDE promotion cycle for a Prime Video team, a candidate submitted strong metrics (12% reduction in stream start failures) but zero cross-functional evidence. His manager pushed back in the HC. The response from the committee chair: "We believe the numbers. We don't believe the scope. Where's the partner feedback? Where's the team-level influence?"
The judgment: Your Forte package needs a narrative arc across time. Evidence collected in a sprint looks different than evidence collected over two quarters. Start early, document continuously, and make sure your peers see the arc too.
> 📖 Related: First 90 Days EM: Google vs Amazon Culture Fit Challenges
What Mistakes Destroy Promotion Cases During the Forte Review?
Mistake 1: Relying on manager-only evidence. In a 2023 Kindle reading experience HC, a candidate submitted a self-assessment and manager review. No peer feedback. The Bar Raiser noted: "This candidate may be excellent. We have no way to verify it independently." Rejection.
Amazon's promotion model requires independent corroboration. Your manager advocating for you is the floor, not the ceiling. Without peer voices, the committee assumes best-case bias.
Mistake 2: Nominating peers who only agree with you. In an AWS Lambda promotion case, a candidate nominated 5 colleagues — all of whom reported to the same tech lead and had worked on the same project for 18 months. The feedback was glowing. It was also homogenous. The committee flagged: "This reads like a team that hired each other, not an IC who influenced across boundaries."
Nominate peers who challenged you. Nominate people who pushed back on your decisions. Their feedback signals that you lead through disagreement, not echo chambers.
Mistake 3: Submitting metrics without context. In a 2024 Prime same-day delivery promotion, a candidate listed "18% reduction in delivery errors." The committee asked: "18% relative to what baseline? Over what time period? Attributed to what intervention?" The candidate had no answer. The metric existed in isolation. It was discarded.
Every number in your Forte package needs a sentence of context. Baseline, intervention, attribution. Without it, metrics are decorations.
How Can I Fix a Weak Forte Review Before the Committee?
You can't fix peer feedback once submitted. You can only contextualize it.
In a 2023 Amazon Logistics HC, a candidate's peer feedback was mixed — two reviewers praised execution speed, two questioned strategic thinking. The candidate submitted a two-page addendum with specific examples of strategic decisions: "When we chose to deprioritize X feature, I modeled the tradeoff and presented it to the VP. The decision took three weeks of cross-team negotiation." He named the VP. He named the timeline. He provided evidence the committee could verify.
The committee approved the promotion. Not because the feedback improved, but because the candidate provided a narrative framework that contextualized the variance.
The judgment: Mixed feedback isn't a death sentence. Incoherent feedback is. If your peers said different things, synthesize the narrative that explains why. Don't ignore the divergence — own it and explain it.
Preparation Checklist
- Draft your impact brief 90 days before nominations open. One page, three columns: initiative, your contribution, measurable outcome. Send to nominated peers before requesting calendar time.
- Nominate 5-8 peers across at least two teams. Include one person who challenged your decisions. Amazon values feedback from skeptics more than supporters.
- Schedule 20-minute 1:1s with each nominated peer. Walk through your impact brief verbally. Let them ask questions before writing feedback. Most people write better feedback when they've processed the context.
- Collect cross-functional evidence from at least two partner teams outside your immediate org. AWS promotion HCs in 2023 specifically flagged candidates with zero external partner feedback.
- Ensure every metric in your self-assessment has a baseline, intervention, and attribution sentence. If you can't explain where the number came from, remove it.
- Review your manager's draft feedback before submission. Align on language — if your manager describes you as "strategic" but your peer feedback describes "execution focus," the committee will notice the gap.
- Work through a structured evidence collection framework. The PM Interview Playbook covers peer feedback synthesis with real Amazon HC debriefs — specifically the variance problem (when reviewers say contradictory things) and how to frame it for committee approval.
Mistakes to Avoid
BAD: Submitting peer feedback from only your immediate team with no cross-functional voices.
GOOD: Nominating at least two peers from partner teams who can speak to your influence outside your direct org. In a 2024 AWS Lambda HC, candidates with partner feedback were 2.3x more likely to receive committee approval than candidates with team-only feedback.
BAD: Waiting until the Forte portal opens to start documentation.
GOOD: Starting a running evidence log in month one of the promotion window. Update it biweekly with specific initiatives, decisions, and outcomes. When nominations open, you have 6 months of curated material — not 6 weeks of panic.
BAD: Nominating peers who will only say positive things.
GOOD: Including at least one peer who pushed back on your work. Their feedback signals you can lead through disagreement. Amazon's leadership principles reward builders who operate through friction, not around it.
FAQ
My peer feedback is weak. Can I resubmit?
You cannot reopen peer feedback once submitted, but you can submit a written addendum to your manager before the HC convenes. In a 2023 Prime Video promotion, a candidate used a one-page addendum to contextualize mixed feedback — specifically addressing where two reviewers questioned strategic depth by citing a named VP presentation he led. The committee approved him. Weak feedback isn't fatal. Incoherent feedback is.
How many peers should I nominate for my Forte review?
Nominate 5-8 peers. Amazon's Forte system requires a minimum of 5. In a 2024 AWS Amplify promotion cycle, candidates who submitted exactly 6-7 peer reviews had the highest approval rate — enough breadth to demonstrate cross-functional impact, not so many that the feedback became diluted. Nominate more than 8 only if you've worked across multiple teams in the review period.
What happens if my manager submits a strong review but my peers don't?
The committee will flag the discrepancy. In a 2023 Kindle HC, a candidate had a glowing manager review and mediocre peer feedback. The Bar Raiser asked: "Why does this IC's manager see something his peers don't?" The candidate had no answer. The promotion was deferred. Manager advocacy is necessary. Peer corroboration is mandatory.amazon.com/dp/B0GWWJQ2S3).