Performance Reviews in IT: How to Prepare and Get Promoted
Advanced3 minInnovialabs editorial team
In short
A promotion at performance review is prepared all year, not the week before: you track achievements, agree on next-level criteria with your manager early and arrive with facts rather than feelings. A self-review is evidence of impact, not a list of tasks.
How a performance review works
A performance review is a regular evaluation of an employee's work, usually every six months or once a year. It typically includes:
- self-review: your own assessment;
- peer feedback: from people you worked with;
- manager assessment: the final view combining all sources;
- calibration: managers compare ratings across teams.
The key takeaway: promotion decisions are often made in calibration, where you are not in the room. Your manager needs clear arguments in hand. Your job is to give them those arguments.
Step 1. Track achievements all year
Memory fails: by review time you will have forgotten half of what you did. Keep an achievements log (often called a brag document) and update it every week or two.
## Q2
- What: moved the frontend build to a new bundler
- Why: the CI build was a bottleneck for the whole team
- Outcome: releases became more frequent, CI complaints stopped
- Evidence: PR link, team lead's comment in chat
Record not only tasks but also:
- incidents you resolved and root causes you found;
- help to colleagues, reviews, mentoring;
- process and documentation improvements;
- thanks and feedback from people.
Step 2. Align on expectations early
The most common cause of review disappointment is different ideas of what "working at the next level" means. Sort this out before the review, not during it:
- Ask your manager for the level descriptions or competency matrix.
- In a 1:1, say it directly: "I want to reach the next level. What am I missing?"
- Write the answer down and turn it into goals for the next six months.
- Return to these goals in regular meetings and check progress.
If your manager answers in general terms, ask for specific examples of the behavior they expect to see.
Step 3. Write a strong self-review
A self-review is not a retelling of tickets from the tracker. It is a reasoned document about your impact.
| Weak | Strong |
|---|---|
| "Worked on payment tasks" | "Led the payment provider integration from requirements to release" |
| "Helped colleagues" | "Onboarded two new developers who now close tasks independently" |
| "Improved CI" | "Reduced build wait times so the team ships changes more often" |
Principles:
- Action verb + outcome + why it matters.
- Tie examples to the criteria of the level you are aiming for.
- Mention growth areas too. It shows maturity, not weakness.
- Keep it short: your manager reads many of these documents.
Step 4. Build a promotion case
A promotion case answers the question "why is this person already working at the next level?" Gather:
- 3 to 5 of your strongest examples, tied to level criteria;
- peer feedback that supports those examples;
- the period over which you have consistently shown this behavior.
Give the material to your manager ahead of time so they can prepare for calibration.
If you didn't get promoted
Don't argue emotionally. Ask exactly what evidence was missing, agree on a plan and the timing of the next review, and record it in writing.