Every review cycle, strong engineers sit down in front of a blank performance review form, list five Jira tickets from the last month, write "Worked on the billing migration and helped onboard two new hires," and submit it.

Then calibration happens, and someone who shipped half as much walks out with an "Exceeds Expectations" rating.

The reason isn't necessarily favoritism. It’s mechanical: your manager has about three minutes in a calibration room to defend your rating in front of six other engineering managers and a director who have never read your code.

If your self-review reads like a Jira commit log, your manager has to remember your business impact under pressure. If your self-review already has the metrics, the scope level, and the links to evidence, your manager reads your sentences aloud verbatim.

The Formula: Outcome + Metric + Scope + Evidence

Every bullet in a calibration-ready review should answer:

What changed for users or the business? (The Outcome)

How was it measured?…