Self-review examples by role
Weak lines and rewrites that a calibration committee can verify, written for your role. Every example keeps the facts you must supply in [brackets], so nothing is invented.
- Software EngineerEngineering reviews are decided on scope and impact, not on ticket counts. The examples below turn common engineering bullets into claims a promotion committee can verify, with the facts you must supply left in [brackets].5 examples →
- Engineering ManagerManager reviews are judged on what the team delivered, how people grew, and how much the org depends on your judgment. These examples convert management activities into results.5 examples →
- Product ManagerProduct reviews reward outcomes and judgment, not launch counts. These examples tie what you shipped to what changed for users and the business.5 examples →
- Product DesignerDesign self-reviews are often read by people who will not open your Figma file. These examples make design impact legible to engineering and product reviewers.4 examples →
- Data ScientistData science reviews hinge on whether your analysis changed a decision. These examples connect models and analyses to the business choices they drove.4 examples →
- Data EngineerData engineering is invisible when it works. These examples surface the reliability, cost, and enablement value of pipelines and platforms.4 examples →
- Data AnalystAnalyst reviews reward insight that led to action. These examples show the step from report to decision.3 examples →
- Site Reliability / DevOps EngineerReliability work is judged on outcomes you prevented. These examples quantify uptime, toil, and velocity improvements.4 examples →
- QA / Test EngineerQuality work is easiest to undervalue. These examples show the defects, delays, and risk your testing removed.3 examples →
- Security EngineerSecurity impact is about risk reduced without slowing the business. These examples express that in terms reviewers outside security understand.3 examples →
- Machine Learning EngineerML engineering reviews look for models that reach production and move product metrics. These examples cover the path from experiment to impact.3 examples →
- Technical Program ManagerTPMs are judged on complex programs delivered across teams. These examples show coordination as outcomes, not meetings.3 examples →
- Marketing ManagerMarketing reviews reward pipeline and revenue influence. These examples tie campaigns to commercial outcomes.3 examples →
- Sales / Account ExecutiveSales reviews start with quota, but promotions are won on how you sell. These examples add the deal strategy and team impact behind the numbers.3 examples →
- Customer Success ManagerCustomer success is measured in retention and expansion. These examples connect relationships to revenue outcomes.3 examples →
- Project ManagerProject management reviews focus on delivery against scope, time, and budget. These examples show judgment, not just tracking.3 examples →
- UX ResearcherResearch is valued by the decisions it changes. These examples connect studies to roadmap and product outcomes.2 examples →
- Financial AnalystFinance reviews value accuracy, speed, and influence on decisions. These examples show analysis that changed how money was spent.3 examples →
- Operations ManagerOperations reviews reward efficiency, quality, and scale. These examples quantify how processes improved under your leadership.3 examples →
- Customer Support SpecialistSupport reviews look at quality and volume, but promotions need more: problems you fixed at the root and teammates you helped.3 examples →
- HR Business PartnerHR partner reviews value business outcomes from people programs. These examples connect HR work to retention, performance, and leadership decisions.3 examples →