ReviewReady

Senior Engineer Self-Review Template + Brag Doc

Free from ReviewReady · by Shaan, Senior Tech Lead

How to use this: Make a copy (Google Doc / Notion). Spend 10 minutes every Friday on Part A. When review season comes, Part B takes 1 hour instead of a whole weekend.


PART A — Brag Doc (fill in weekly)

Rule: write it down the week it happens, with a number and a link. Future-you will forget both.

A1. Weekly log

| Week | What I did | Impact (number if possible) | Evidence link (PR / ticket / doc) | Rubric area* | |—|—|—|—|—| | e.g. 3 Mar | Fixed N+1 query in orders API | p95 latency 1.2s → 300ms | PR #482 | Technical | | | | | | | | | | | | |

*Rubric areas: Technical · Scope/Ownership · Collaboration · Mentoring · Delivery · Business impact

A2. Projects (update monthly)

| Project | My role | Start → end | Result | Who saw it (stakeholders) | |—|—|—|—|—| | | Led / contributed / reviewed | | | |

A3. Kudos & feedback received

Paste screenshots or quotes from Slack, email or peer feedback. (“Thanks for jumping on the incident at 2 AM.” — Product Manager, Payments)

-

A4. People I helped

Mentoring, onboarding, pairing, code reviews, interviews conducted.

Who / which team What I did Outcome
     

A5. Things I learned / new skills

-


PART B — Self-Review (fill in at review time)

B1. Summary (3–4 sentences)

Template: “This cycle I focused on [1–2 main themes]. My biggest impact was [top result with number]. I also [second result], and grew in [skill]. Next cycle I want to [goal tied to next level].”

B2. Key accomplishments (top 3–5, most important first)

For each, use XYZ: “Accomplished [X], as measured by [Y], by doing [Z].”

  1. [Project name]
    • What:
    • Impact (number):
    • How / my specific role:
    • Evidence: 2. 3.

B3. Evidence by rubric area

Match your work to what your company expects at your level and the level above. This is how promotions get made.

Area Expectation at Senior (example) My evidence this cycle
Technical Designs systems others build on; makes sound trade-offs  
Scope / Ownership Owns a significant area end-to-end; handles ambiguity  
Delivery Ships reliably; unblocks themselves and others  
Collaboration Works across teams; influences without authority  
Mentoring Grows other engineers through reviews, pairing and onboarding  
Business impact Connects work to customer or revenue outcomes  

Gap check: any empty row is a risk. Either find evidence (check your PRs, docs and calendar) or make it a goal for next cycle.

B4. Challenges & what I learned

Template: “[Situation] didn’t go as planned because [reason]. I [what I did], and next time I’ll [change].” (Showing that you learn from problems reads as senior. Hiding them doesn’t.)

B5. Goals for next cycle (2–3, tied to the next level)

| Goal | Why it matters for [next level] | How I’ll show evidence | |—|—|—| | e.g. Lead the design review for the search rewrite | Staff: cross-team technical leadership | Design doc + review outcomes | | | | |

B6. Support I need from my manager

-


PART C — Tech Lead’s checklist before you submit

Weak vs strong (examples)

| ❌ Weak | ✅ Strong | |—|—| | “Worked on the checkout service.” | “Led checkout performance work: p95 latency 1.8s → 600ms (–67%), removing the #1 source of on-call pages.” | | “Helped with code reviews.” | “Reviewed 34 PRs across 2 teams; my review comments became our team’s error-handling guideline.” | | “Onboarded new hires.” | “Onboarded 2 new engineers; both shipped their first production PR within 2 weeks (team average: 5).” | | “Fixed bugs.” | “Closed 18 bugs, including a data-loss bug affecting ~4% of orders, found through log analysis.” |


Want this filled in automatically from your GitHub and Jira history? ReviewReady is coming. Join the waitlist: [link — to add after the landing page is approved].