The Forte writing exercise is not evaluating your storytelling ability — it’s a proxy for judgment under ambiguity. Candidates who treat it as a narrative test fail; those who use it to signal decision-making rigor pass. Your document must reflect forward-looking leadership, not past execution.
Amazon Forte Writing for IC to Manager Transition
TL;DR
The Forte writing exercise is not evaluating your storytelling ability — it’s a proxy for judgment under ambiguity. Candidates who treat it as a narrative test fail; those who use it to signal decision-making rigor pass. Your document must reflect forward-looking leadership, not past execution.
Running effective 1:1s is a system, not a talent. The Resume Starter Templates includes agenda templates and question banks for every scenario.
Who This Is For
You are a high-performing individual contributor (IC) at Amazon, likely at L5 or L6, preparing to interview for your first manager role (typically L6 or L7). You’ve led projects, mentored juniors, and delivered results — but you’ve never owned team outcomes through others. This guide targets your specific blind spot: translating IC competence into managerial judgment in the Forte writing sample.
How is the Forte writing exercise scored at Amazon?
Amazon evaluates Forte documents through three lenses: context-setting precision, decision logic transparency, and leadership principle alignment. In a debrief last year, a hiring committee split on a candidate who had strong metrics but failed to articulate trade-offs — the HC chair killed the packet with: “He executed well, but I don’t believe he chose well.”
Scoring isn’t about volume of content. It’s about signal density. Each paragraph must answer: What did you decide? Why then? What did you deprioritize?
Not “I led a migration,” but “I delayed the migration by two weeks to preserve Q3 availability targets because customer trust was at risk.” The problem isn’t your action — it’s your framing of ownership.
One L6-to-L7 candidate passed despite modest metrics because her document showed she killed a pet project after discovering a regulatory risk. The HC noted: “She protected the business when no one was looking.” That’s the signal Amazon wants: proactive stewardship, not task completion.
Leadership principles aren’t checkboxes. They’re behavioral evidence. Writing “I delivered results” with no tension is useless. Writing “I escalated a resourcing conflict to my manager after two failed alignment attempts” demonstrates Earn Trust and Dive Deep — without naming them.
> 📖 Related: Self-Review vs Peer Review for Amazon Promotion: Which Matters More?
What structure should I use for the Forte writing sample?
Use the STAR-R format: Situation, Task, Action, Result — plus Reflection. The Reflection is where ICs fail. Most stop at Result. Managers reflect on trade-offs, scalability, and team impact.
In a Q3 debrief, a candidate described launching a feature two weeks early. Strong result. But when asked in the interview, “What broke as a result?” he couldn’t answer. The HC rejected him: “He shipped fast, but didn’t own the aftermath.”
Your structure:
- Situation (1-2 sentences): Define stakes. Not “We had low retention” but “Retention dropped 18% in two months, risking Q4 NPS targets.”
- Task (1 sentence): Your unique accountability. “I owned the diagnosis and turnaround plan.”
- Action (3-4 sentences): Decisions, not tasks. “I deprioritized roadmap items A and B to reallocate two engineers to root cause analysis.”
- Result (1-2 sentences): Quantified outcome. “Retention recovered to baseline in 6 weeks.”
- Reflection (2 sentences): What you’d do differently, and what it taught you about leading through others. “I now involve support teams earlier — we missed early signals because we operated in silos.”
Not “I worked hard,” but “I changed how the team allocates capacity during crises.” The shift isn’t in performance — it’s in perspective. You’re not proving you can deliver. You’re proving you can lead when delivery fails.
How long should my Forte writing sample be?
One page. No more. Amazon reviewers spend 90 seconds on average reading each document. In a 2023 HC calibration, a candidate submitted a 3-page Forte. The bar raiser skimmed the first third, then said: “If he can’t summarize his best leadership moment in one page, he can’t prioritize.” Rejected.
Margins: 0.75 inches. Font: 11pt Arial or 12pt Times New Roman. No graphics. No bullet points.
ICs often overwrite to prove complexity. Managers distill. Your constraint isn’t space — it’s discipline. Every sentence must answer: Does this show judgment, or just effort?
During a hiring committee for an L6 Ops Manager role, two candidates wrote about the same outage. One used 800 words. The other used 550. The shorter one passed. Why? It opened with: “We lost 4 hours of delivery capacity during peak. I froze feature deployments and redirected three teams to recovery — delaying two launches.” Clarity of trade-off. The longer version buried the decision in timeline detail.
One page forces triage. That’s the test.
> 📖 Related: Meta vs Amazon PM Interview
What’s the difference between IC and manager-level writing in Forte?
IC writing proves: “I did the work.” Manager writing proves: “I decided what work mattered — and what didn’t.”
Last year, two L5 SDEs applied for the same L6 TPM role. Both wrote about incident response.
Candidate A: “I led debugging, identified the memory leak, and deployed the fix within 3 hours.”
Candidate B: “I handed debugging to a senior engineer, escalated staffing gaps to my manager, and initiated a post-mortem process redesign — knowing the fix was temporary.”
Candidate B passed. Not because the action was bigger, but because the scope of ownership was broader.
Not “I solved a problem,” but “I changed the system that created the problem.”
ICs focus on inputs: hours worked, code written, meetings run. Managers focus on outputs: risk mitigated, team capability built, precedent set.
In a debrief for a Marketplace team, an HC member said: “She didn’t just fix the bug — she renegotiated the SLA with the dependency team. That’s managerial leverage.”
Your language must shift from execution to governance. Not “I trained the new hire,” but “I adjusted onboarding bandwidth across the team to absorb ramp-up cost.” You’re no longer optimizing your time. You’re optimizing team throughput.
How do I choose the right story for my Forte?
Pick a story where you exercised discretion without authority. Amazon wants evidence you led before the title.
Not “My manager asked me to lead a project,” but “I stepped in when no one else did — despite lacking formal authority.”
In a recent HC for an L7 UX Manager role, a candidate wrote about stepping up during a product lead departure. She didn’t wait for assignment. She convened the team, set a 30-day stabilization plan, and negotiated scope cuts with product. The bar raiser said: “She created leadership where there was a vacuum.”
Avoid stories where you were explicitly delegated. Delegation shows trust, but not initiative. Amazon wants proof you’ll lead when no one is watching.
Ideal triggers:
- A metric trending negative
- A team conflict unaddressed
- A customer escalation ignored
- A process breaking silently
One L6 IC wrote about noticing junior engineers were burning out. He didn’t complain. He redesigned the on-call rotation, socialized it with peers, and got buy-in before proposing it to his manager. Result: 40% drop in after-hours pages. The HC approved him unanimously: “He improved team health without a mandate.”
Not “I followed process,” but “I changed process when it failed the team.” That’s managerial instinct.
Preparation Checklist
- Draft your Forte story using STAR-R, with emphasis on Reflection
- Trim to one page — aim for 500-600 words
- Remove all passive language — every sentence must show agency
- Align decisions to leadership principles without naming them explicitly
- Get feedback from a current Amazon manager, not an IC
- Work through a structured preparation system (the PM Interview Playbook covers Amazon Forte evaluation with real debrief examples from L6–L7 transitions)
- Practice verbal walkthroughs — your writing must sync with interview responses
Mistakes to Avoid
BAD: “I collaborated with multiple teams to deliver the project on time.”
This is activity without ownership. It implies shared accountability — the opposite of leadership.
GOOD: “I broke a deadlock between teams by committing my engineer to the critical path, delaying my Q2 goal.”
Shows trade-off, ownership, and sacrifice.
BAD: “I mentored a junior engineer who later got promoted.”
Correlation is not causation. This implies credit without proof of intent.
GOOD: “I identified high potential early, created a stretch assignment, and shielded time for development — resulting in their promotion six months later.”
Demonstrates intentionality and investment.
BAD: Using leadership principle names as headers (e.g., “Customer Obsession”).
Amazon penalizes checklist thinking. Principles must be demonstrated, not declared.
GOOD: Writing, “We delayed the launch to fix a privacy flaw customers hadn’t reported — knowing a breach would cost more long-term,” which embodies Customer Obsession and Think Big without naming them.
FAQ
Is it okay to write about a failure in my Forte?
Yes, if you owned the recovery. In a 2022 HC, a candidate wrote about a failed launch. He passed because he detailed how he restructured team incentives to prevent recurrence. Amazon wants learning, not perfection. Not “I failed,” but “I changed the system because of it.”
Can I use the same Forte story for multiple interviews?
Only if the role demands similar leadership scope. For an L6 Ops Manager and L7 Product Manager, use different stories — one showing operational rigor, the other strategic influence. Reusing stories signals limited range. Adapt to the role’s primary tension: scale, ambiguity, or innovation.
Should I include metrics in my Forte?
Only if they prove impact, not activity. “Reduced latency by 40%” is weak. “Reduced latency by 40%, restoring SLA compliance and preventing $2.3M in expected churn” shows business ownership. Metrics must trace to outcomes Amazon measures: cost, quality, speed, or risk.
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.