Most important take away

Your work does not speak for itself — your manager only sees about 10% of what you do, so closing that visibility gap is essential to getting fair performance reviews and promotions. Build a brag book throughout the year, learn to communicate your impact at the right altitude for each audience, and share your work openly so recency bias and poor communication don’t quietly tank your career.

Summary

Actionable insights and career advice from former Amazon Principal Engineer Steve Win:

1. Beat recency bias with a “brag book.”

• Managers forget what you shipped early in the year; work from February gets discounted by review time.
• Aggregate everything you did this year into one place: commits, docs, emails, Slack messages, meeting notes.
• Feed it into an LLM along with your company’s role/level expectations document (or use the job posting for your level / next level, or reverse-engineer from promotion announcements).
• Prompt the LLM to generate a brag document framed in the language used to evaluate performance.
• Aim to end up with 4–6 big achievements that clearly demonstrate your performance for the year.
• Do this now (review season) — don’t put it off.

2. Communicate at the right altitude.

• Highly competent + good communication = a force multiplier; competence without communication is “multiplying by zero.”
• Engineers commonly describe work at the wrong altitude (too technical for the audience).
• Example given: melatonin described as “a hormone that binds to receptors in the suprachiasmatic nucleus” vs. “a pill that helps you go to sleep.”
• Tailor altitude per audience:
  • Peers: deep technical detail
  • Manager: outcome and what it means for the team
  • Skip-level: how it connects to org priorities
  • Leaders: business impact in one sentence
• Test: “If I had 10 seconds to explain why this work matters, what would I say?”
• Practice by writing each brag-book item at multiple altitudes.

3. Stop hiding your work — visibility is not self-promotion.

• The choice isn’t “self-promoter vs. authentic,” it’s “visible vs. invisible.”
• On his promotion-to-principal project (~100 teams, billions on the line), Steve sent a daily email update to thousands of people for ~4 months. Those who didn’t care just filtered or unsubscribed; everyone else watched his role unfold in real time.
• Rule: “Never make your manager ask for your status. They have to ask, you lose.”
• If broadcasting feels gross, start by promoting others — call out teammates in public channels, message their managers about good work. It costs nothing and reframes visibility as positive.
• Once comfortable, include yourself accurately: “Raj’s testing was crucial, and I’m proud of the integration work I contributed.”

Tech / pattern callouts:

• The seat-allocation problem at Amazon Tickets (single seats stranded in otherwise full rows) — analogous to the C malloc contiguous-memory allocation problem. Lesson was about communication, not the algorithm itself.
• Use an LLM as a structured generator for brag documents by feeding it both your raw artifacts and the rubric (role expectations) — a practical applied-LLM pattern for career work.

Chapter Summaries

Intro — The visibility gap. You see 100% of your work; your manager sees ~10%. That gap is why good work gets overlooked and talented people get passed over.

Problem 1: Everyone forgets, including you. Recency bias dominates reviews. Steve shares a personal story of a major March launch at Amazon that he and his manager both forgot by review time, costing him a “Meets Expectations” rating.

Solution 1: Build a brag book with an LLM. Aggregate your year’s artifacts, feed them plus your company’s level expectations into an LLM, and produce 4–6 framed achievements in the language reviewers use.

Sponsor / Speedrun to Promotion plug. Pitch for his coaching program for engineers and scientists targeting “exceeds” ratings and faster promotions.

Problem 2: Your explanation doesn’t land. Less competent peers get more recognition because they communicate better. Story: explaining the ticket-seat allocation fix as a malloc-style CS problem got blank stares.

Solution 2: Communicate at the right altitude. Reframe work for the audience (peers, manager, skip-level, leaders). Practice multi-altitude descriptions for each brag-book item.

Problem 3: Fear of looking like a self-promoter. Staying quiet keeps you invisible — invisible is the actual problem.

Solution 3: Share publicly, start by promoting others. Daily-email example from his principal-promotion project. Begin with recognizing teammates, then naturally include your own contributions in accurate, factual reports.

Outro. Tease for a follow-up video on why hard work alone doesn’t matter as much as something else.