The IC5 to IC6 promotion at Amazon hinges on proving sustained impact, not reciting achievements. Most IC5s fail because they write Fortés like performance reviews — listing tasks — instead of framing leadership as leverage. The difference between approval and rejection is not volume of content, but clarity of judgment: showing how you changed the trajectory of a problem, team, or business. Fortés that win embed the Leadership Principles in decision-making, not decoration.
TL;DR
The IC5 to IC6 promotion at Amazon hinges on proving sustained impact, not reciting achievements. Most IC5s fail because they write Fortés like performance reviews — listing tasks — instead of framing leadership as leverage. The difference between approval and rejection is not volume of content, but clarity of judgment: showing how you changed the trajectory of a problem, team, or business. Fortés that win embed the Leadership Principles in decision-making, not decoration.
Not sure what to bring up in your next 1:1? The 0→1 SWE Interview Playbook (2026 Edition) has 30+ high-signal questions organized by goal.
Who This Is For
This is for Amazon IC5 Product Managers with 12–24 months in role, targeting promotion within the next 6 months, who have led at least one major project end-to-end and interacted with senior stakeholders. It is not for engineers, non-technical program managers, or those without ownership of product outcomes. If your scope has been limited to backlog grooming or feature execution without cross-functional influence, this framework will expose gaps — not patch them.
How is the IC5 to IC6 Forté evaluated at Amazon?
The Forté is not assessed for completeness — it’s judged for leadership signal. In a Q3 2023 HC (Hiring Committee) for Devices, two candidates had shipped major OS updates. One was approved; one was rejected. The difference? One wrote: “Led OS latency reduction project,” followed by metrics. The other opened with: “Recognized that customer churn in Device X correlated with boot time above 8 seconds — a threshold invisible to the team. Drove cross-org alignment to treat it as a P0, overruling roadmap priorities.” Same outcome, different judgment narrative.
At IC6, Amazon expects you to set the direction, not follow it. The Forté is the only artifact that proves you did.
Your writing must answer three silent questions:
- Did you identify the right problem? (not just a problem)
- Did you make hard calls with incomplete data?
- Did you scale your impact beyond your direct control?
Not “what you did,” but “why you did it, and why it mattered.”
The Leadership Principles are not bullet points to check — they are inference engines. Interviewers use them to reverse-engineer your decision logic. If your Forté doesn’t embed Dive Deep in how you diagnosed the problem, or Ownership in who you pulled into the fight, the committee assumes those behaviors didn’t happen.
One debrief I sat on collapsed into a 20-minute argument over whether a candidate “owned” a supply chain redesign. The data showed cost savings, but the Forté said “collaborated with Ops.” That passive framing implied coordination, not leadership. The HC concluded: “No evidence they drove it.” Rejected.
> 📖 Related: 1on1 Cheatsheet vs Lattice: Which Better for Amazon PM Feedback?
What should the Forte structure look like for IC6 promotion?
Lead with judgment, not chronology. The standard “Situation, Action, Result” template fails at IC6 because it flattens causality. It encourages: “There was a problem. I fixed it.” Amazon wants: “I saw a problem no one else saw, and I changed the organization’s behavior to solve it.”
The winning structure is: Problem Framing → Strategic Choice → Leverage → Outcome.
In a recent successful Forté, a PM opened:
“By Q4 2022, Delivery Speed for Prime Now was declining despite increased investment. Leadership assumed capacity was the bottleneck. We proved the real constraint was rebalancing logic in the dispatch algorithm — a second-order effect no team owned.”
That’s Problem Framing: reframing the narrative. Not “delivery was slow,” but “the diagnosis was wrong.”
Next line: “I paused two roadmap initiatives to redirect my team toward simulation modeling, betting that algorithmic inefficiency outweighed hardware scaling.”
That’s Strategic Choice: trade-off + conviction.
Then: “Convinced Transportation Science to co-own the model, and Scaled Ops to run A/B tests in three metro zones despite holiday season risk.”
That’s Leverage: influence without authority.
Finally: “Reduced average dispatch time by 18%, saving $22M annually — now the standard for all urban zones.”
That’s Outcome — but notice it’s not just metric. It’s scale and adoption.
Most IC5s reverse this. They start with “I led a project to improve dispatch logic,” burying the insight. The structure becomes a log, not a claim.
Not “I did X,” but “I saw X when others saw Y, chose Z when others would have chosen A, and moved people who didn’t report to me.” That’s IC6.
Which Leadership Principles matter most in the Forte?
In 73 IC6 promotions I’ve reviewed, only four Leadership Principles consistently separate approved from rejected candidates: Ownership, Dive Deep, Are Right A Lot, and Bias for Action. The others appear as context, not proof.
Ownership is not “I owned the roadmap.” It’s “I took accountability for an outcome no one else claimed.” In a 2022 HC for Supply Chain, a candidate wrote: “When inventory accuracy dropped post-migration, the blame shifted between Data, Ops, and Eng. I froze feature work and ran a root cause sprint, even though my charter was demand forecasting.” That’s ownership — stepping into the gap.
Dive Deep is not “I looked at dashboards.” It’s “I found the right data when the obvious metrics were misleading.” One PM noticed customer return rates spiked not after delivery, but 48 hours before. He pulled warehouse audio logs and found couriers were marking deliveries as complete early. That wasn’t in any KPI. Dive Deep means going below the dashboard.
Are Right A Lot shows up in counter-consensus decisions. Not “I agreed with my boss,” but “I pushed back on my VP because the data showed lower returns on the new feature despite higher engagement.” One candidate wrote: “Leadership wanted to expand to Tier 2 cities. I modeled CAC payback and projected 14-month cycles — unsustainable. I proposed focusing on retention in Tier 1 instead. We hit 8-month payback.” That’s being right, not just being loud.
Bias for Action is often misused. It’s not “I moved fast.” It’s “I acted when waiting was safer.” A PM killed a $3M committed roadmap item two weeks before launch because a beta test showed 40% usability failure. His Forté said: “I escalated to the EU GM with a recommendation to delay, knowing it risked my credibility. We redirected engineering to fix core flows.” That’s bias — with consequence.
Not “I used LPs,” but “I made hard calls, and the LPs explain why they were right.”
> 📖 Related: Google PM vs Amazon PM Interview: Different Approaches for Each Culture
How long should my Forte be and how many projects should I include?
Your Forté must fit on one page — 450 to 550 words. Amazon’s internal guidelines state: “If it needs two pages, the thinking isn’t sharp enough.” Most rejected Fortés exceed 700 words. They’re not rejected for length — they’re rejected for lack of editing, which signals lack of clarity.
You need one deep project and one secondary example — no more. The deep project must span at least six months and involve cross-functional teams (Eng, UX, Ops, or external partners). The secondary example can be shorter but must showcase a different leadership behavior.
In a 2023 HC for AWS, a candidate included three projects: two feature launches and a migration. All were solid. But none showed different dimensions of leadership. The debrief concluded: “This is excellent IC5 work — consistent execution — but no evidence of elevated scope.” Rejected.
Contrast that with a winning Forté:
- Deep project: rebuilt pricing engine after audit revealed $18M in revenue leakage (Ownership + Dive Deep)
- Secondary: led incident response during a 12-hour outage, restructured escalation protocol (Bias for Action + Earn Trust)
Two stories. One about fixing a broken system. One about leading under fire. Together, they show range.
Do not list more than two. More than that, and you signal you can’t prioritize. You’re not applying for “most projects done.” You’re applying for “person we trust with bigger problems.”
Edit ruthlessly. Every sentence must answer: “Does this prove I think like an IC6?” If not, cut it.
How do I write about impact without sounding arrogant?
Arrogance isn’t caused by claiming impact — it’s caused by separating yourself from the team. The problem isn’t “I drove,” it’s “I drove while implying no one else could have.”
The fix is inclusive ownership — using “I” to claim judgment, and “we” to credit execution.
BAD: “I identified the latency bottleneck and directed the team to fix it. My redesign reduced load time by 40%.”
This frames the team as execution robots. It triggers skepticism: “Did they really need this person to act?”
GOOD: “I recognized the customer drop-off at 4-second load was tied to third-party script bloat — a blind spot in our performance reviews. I led the team to prototype a lazy-loading framework, and we shipped it across 12 core pages.”
Here, “I” owns the insight and leadership. “We” owns the build. The distinction is critical.
Another technique: attribute insight to data, not ego.
Not: “I knew the checkout flow was broken.”
But: “Cohort analysis showed 68% of mobile users abandoned at the OTP step — a signal the team had normalized. I proposed A/B testing a biometric alternative.”
Let the data explain why you acted. That way, the judgment is defensible, not self-aggrandizing.
One HC rejected a candidate who wrote: “My strategy doubled engagement.” The chair said: “Where’s the doubt? Where’s the alternative path considered? This reads like a press release.”
Humility at Amazon isn’t about downplaying results — it’s about showing you understand complexity. Say what you bet on, what you gave up, and what you learned.
Preparation Checklist
- Write your Forté in Google Docs — not Word — to enable real-time feedback from peers
- Run it by two IC6+ PMs who’ve been through HC, not just managers who like your work
- Remove all adjectives like “successful,” “effective,” or “seamless” — they signal vagueness
- Replace passive verbs (“supported,” “collaborated on”) with active leadership verbs (“drove,” “challenged,” “restructured”)
- Quantify outcomes in dollars, time, or percentage — never “improved,” “increased,” or “optimized”
- Work through a structured preparation system (the PM Interview Playbook covers Amazon Forté writing with real HC debrief examples from 2022–2023 cycles)
- Print it out and read it aloud — if any sentence feels like fluff, delete it
Mistakes to Avoid
BAD: “Led a team of 5 engineers to deliver the new search filter ahead of schedule.”
This is IC5 execution. It says nothing about problem selection, trade-offs, or extended impact.
GOOD: “Noticed search conversion dropped 12% after personalization launched. Suspected overfitting. Paused roadmap, ran A/B tests on filter visibility, and redesigned the ranking model with Science. Recovery in 6 weeks; now the filter logic is used in 3 other verticals.”
This shows problem detection, decisive action, cross-functional leverage, and reusability.
BAD: “Collaborated with UX to improve onboarding flow.”
“Collaborated” is a red flag. It implies equality of effort, not leadership. IC6s don’t collaborate — they align, direct, or unblock.
GOOD: “Identified that 53% of new users never reached core features. I broke the stalemate between UX and Eng on modal vs. progressive onboarding by proposing a staged rollout with telemetry. We landed on progressive, adoption rose 38%.”
This shows diagnosis, breaking deadlock, and evidence-based decision-making.
BAD: “My initiative increased NPS by 10 points.”
This omits how you knew it was your initiative, not market noise.
GOOD: “After NPS dipped post-launch, I isolated the driver to post-purchase confusion. I led a cross-functional fix — adding status visuals and ETA updates — and NPS recovered within one cycle. The pattern informed the new customer communication framework.”
This shows causality, ownership beyond launch, and lasting influence.
FAQ
What if I don’t have dollar impact for my project?
Not all IC6 work has direct revenue ties — but you must show proxied business impact. Time saved at scale, risk mitigated, or decision velocity improved count. One PM calculated that reducing PR/FAQ review time from 3 days to 4 hours saved 1,200 engineer-hours annually. That’s leverage. The problem isn’t missing dollars — it’s missing translation.
Should I include feedback from my manager in the Forté?
No. The Forté is your narrative, not a compilation of praise. Manager quotes belong in the endorsement, not the document. Including feedback (“My director said I led well”) signals insecurity. Prove it through action and outcome. Leadership is demonstrated, not endorsed.
How far back can my examples go?
Focus on the last 18 months. Amazon values recency and sustained performance. A five-year-old project, even if major, won’t carry weight unless it’s the foundation of current influence. One candidate referenced a system he built three years ago that was still the org’s standard — that counted. But only because he showed ongoing relevance, not past glory.
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.