Numbers for software engineering self-reviews.

Numbers that can help put your achievements in context, and make them comparable to others, during e.g. performance calibration. All numbers are for achievements within the period:

  • Money
  • Revenue generated
  • Incremental revenue generated
  • Costs saved
  • Business results
  • Business results generated (as KPIs)
  • Results where your work directly/indirectly overachieved results set
  • Reliability
  • SLAs increased from X to Y
  • Number of highest-level outages
  • TTR, TTM average times.
  • TTR, TTM reduced
  • Number of outages avoided by doing work ahead of time
  • Engineering productivity
  • Person hours/days/weeks/months saved by a certain project
  • Reducing time to do (a common enough developer task) by X%
  • Code & architecture
  • Number of PRs done o Number of code reviews
  • Listing out planning documents
  • Number of planning documents you had input on (and listing these)
  • Examples where you helped others ship something in production
  • People
  • Number of people onboarded
  • Number of people mentored
  • The results of mentoring (e.g. people promoted, growing professionally etc)
  • Recruitment
  • Number of interviews done
  • Number of hired made on loops you were
  • Other
  • Number of internal events organized (eg knowledge sharing in your team)
  • Number of external events organized or participated in (events where you helped the business achieve outcomes)
    I’ll cover this topic in-depth on pragmaticengineer.com. Sign up to not miss it!