What to Do 30/60/90 Days Before Performance Review Season

Two weeks before review season, half the engineering org opens a blank document and stares at it. They can't remember what they shipped in Q1. They vaguely recall a project that went well, but the details are gone. The peer feedback window closes in three days and they haven't asked anyone yet. Their manager hasn't mentioned promotion. They're not even sure what the rubric says about their level.

This is what "preparing for your performance review" looks like for most people. And it's why most people walk out of review season with the same rating they got last time.

The engineers who get promoted don't do anything superhuman. They just start earlier. Ninety days earlier, specifically. Not because they're obsessive planners, but because the things that actually move a promotion case — documented evidence, manager alignment, peer visibility, a self-review that reads like a case document — take time to accumulate. You can't manufacture three months of positioning in a weekend.

90 days out: build the foundation

Three months before review season is when the real work starts, and almost nobody does it. At this point, you're not preparing for the review. You're creating the raw material that will make everything downstream easier.

Start a win log (or resurrect the one you abandoned)

If you don't have a running document of your accomplishments, start one now. Not a Notion template you'll forget about. A simple file — a note on your phone, a Google Doc, a text file pinned to your desktop — where you write down what you did at the end of each week.

What goes in a win log:

• Projects shipped — what it was, what it did, and who it affected
• Problems solved — incidents you responded to, blockers you removed, decisions you made under ambiguity
• Scope you took on — anything beyond your defined role: mentoring, cross-team coordination, process improvements
• Quantified outcomes — numbers, percentages, time saved, error rates reduced

The standard here is low. A bullet point is fine. "Led the migration of the billing pipeline off legacy infrastructure. Reduced failed transactions by 35%." That took ten seconds to write and will be worth ten minutes of calibration credibility later.

The Ebbinghaus forgetting curve — one of the most replicated findings in cognitive psychology — shows that people forget roughly 50% of new information within days. Three months from now, when you're writing your self-review, you will not remember what you did this week. The win log is insurance against your own brain.

Run a rubric gap check

Pull up your company's promotion rubric or leveling guide. Read the criteria for the level above yours. Then ask yourself two questions:

1. Where do I already have evidence? Mark the dimensions where you can point to specific work that demonstrates the next level. These are your strengths.
2. Where are the gaps? Identify the dimensions where you have thin or no evidence. These are the areas you need to target over the next three months.

This isn't an abstract exercise. At Google, the promotion committee evaluates against specific dimensions like scope, complexity, and leadership. At Amazon, it's the Leadership Principles. At Meta, calibration weighs impact, engineering excellence, and direction. If you don't know what your company's rubric emphasizes, you're building a case without knowing what the judges are scoring.

Write the gaps down. Then look at your current project load and ask: is any of my planned work going to fill these gaps naturally, or do I need to find opportunities deliberately?

Identify the projects that will become your evidence

You have roughly 12 weeks before the evidence window closes. That's enough time to finish one meaningful project, contribute significantly to another, and build a track record of the kind of work your rubric values.

This doesn't mean switching projects or overhauling your roadmap. It means looking at the work you're already assigned and asking: how do I do this in a way that demonstrates next-level scope?

• If the gap is cross-team impact, look for a coordination point in your current project and own it
• If the gap is technical leadership, offer to write the design doc or lead the technical review
• If the gap is mentoring, start pairing with a junior engineer on something real

The work doesn't change. The framing does.

60 days out: align with your manager

Two months before review season, the focus shifts from building evidence to making sure the right people know the evidence exists. And "the right people" starts with your manager.

Have the alignment conversation

This is the single most important meeting of your entire review cycle, and most engineers never have it. Sixty days before review season, schedule a 1:1 with your manager that's explicitly about your review, not a status update that drifts into career talk. At companies with formal mid-year reviews, that check-in is the natural moment for this conversation — if you treat it as a promotion conversation rather than a formality.

What to cover:

• State your goal. "I want to make sure my work this cycle puts me in the strongest position for [promotion / a strong rating]. Can we talk about where I stand?"
• Share your gap analysis. "I looked at the rubric and I think my strongest areas are X and Y. The gap I see is Z. Does that match your read?"
• Ask what they need. "When you present my case in calibration, what would make the pitch easy for you?"

If your manager agrees with your self-assessment, you're aligned. If they see gaps you missed, you've just bought yourself two months to address them. Either way, you're in a better position than the person who walks into review season hoping their manager noticed everything.

The mechanics of having a career conversation with your manager about promotion are worth reading in full — it covers the specific scripts that work and the ones that backfire.

Start your visibility push

Your manager isn't the only person who matters in calibration. At most companies, the calibration room includes multiple managers and sometimes directors. If nobody else in that room has heard your name, your manager is making a cold pitch with no corroboration.

Sixty days is enough time to build a second voice — someone outside your immediate team who can speak to your work. The moves are straightforward:

• Present your work. Give a tech talk, demo your project at a team all-hands, or write an internal post about a technical decision you made. The format matters less than the audience.
• Contribute to cross-team work. Pick up a task that touches another team's codebase or system. Do it well enough that their manager knows your name.
• Be visible in design reviews. Ask thoughtful questions, offer substantive feedback, and follow up with the author afterward.

None of this is "playing politics." It's making sure the work you've already done is visible to the people who'll weigh in on your case.

30 days out: prepare your materials

One month before review season, the building phase is mostly over. Now you're packaging what you've built into the materials that will actually be evaluated: your self-review, your peer feedback requests, and the case document your manager will carry into calibration.

Draft your self-review early

Do not write your self-review the night before it's due. Write a rough draft now, 30 days out, when the review period is still fresh and you have time to revise.

A strong self-review does three things:

1. Maps your work to the rubric. Every major accomplishment should be connected to a specific leveling dimension. Don't make the reader do the mapping.
2. Quantifies impact. Not "improved the build system" but "reduced average CI build time from 18 minutes to 6 minutes, unblocking 40 developers who were context-switching during builds."
3. Makes the level claim explicit. If you're going for promotion, your self-review should make it clear that you're operating at the next level. Don't hint. Say it: "This work demonstrates [next-level dimension] because [specific evidence]."

If you need a structure to follow, how to write a promotion case document breaks down the exact format that holds up in calibration rooms.

Build your peer feedback strategy

Peer feedback isn't a popularity contest. It's ammunition your manager uses in calibration. "Three peers independently mentioned her technical leadership" carries more weight than your manager's solo assessment.

Who to ask:

• A collaborator on your biggest project — someone who saw your technical decisions up close
• Someone from another team you worked with — this is the cross-team voice your manager needs
• A more junior engineer you mentored — evidence of leadership and multiplying impact

Who not to ask:

• Your best friend at work who doesn't know your recent projects
• Someone who only overlapped with you for a week
• Five people (most companies want two to three, and managers can tell when someone carpet-bombed the feedback form)

When to ask: Now. Don't wait until the feedback window opens. Send a message: "Review season is coming up. I'd appreciate if you'd be one of my peer reviewers. I'll send you a quick summary of what we worked on together so the review is easy to write." That last sentence is the key — you're reducing friction for them and ensuring they mention the right projects.

Prepare a manager brief

This is the document most engineers skip, and the one that makes the biggest difference in calibration. Two to three weeks before your manager has to present your case, hand them a one-page brief:

• Your top 3 wins — each with a 2-sentence description and a quantified outcome
• Rubric mapping — which leveling dimension each win demonstrates
• Pre-answered objections — the questions another manager might ask, with specific answers

Your manager is preparing cases for six to ten reports. They cannot remember everything. The engineer who hands them a ready-made brief is the engineer whose case gets the crispest, most confident pitch. The engineer who assumes their manager tracked everything is the one whose case gets fuzzy answers and follow-up questions.

The final week: execute, don't scramble

Review season is here. If you did the work in the prior 90 days, this week is execution, not panic.

Write the final self-review

Pull out the draft you started 30 days ago. Revise it with fresh eyes. Trim the list to your strongest evidence. Make sure every claim has a number or a specific outcome attached.

Read it once from the perspective of someone who has never worked with you. Does it make sense? Could a stranger understand what you did and why it mattered? If not, rewrite the parts that assume context.

Brief your advocates

If someone in the room besides your manager might speak up for your work — a skip-level, a peer manager you collaborated with — make sure they know your case. This doesn't need to be a formal meeting. A quick message: "Hey, just a heads up — I'm up for senior this cycle. The observability project we worked on together is a big part of my case. Appreciate any good words if it comes up."

This feels awkward. It's also how the engineers who get promoted operate. They don't assume their work will speak for itself, because in a room where your manager has 90 seconds to make the pitch, what they say about you matters more than what you actually did.

Walk into the review conversation prepared

The review meeting with your manager is the one moment in the cycle where you're in the room. Come ready to have a real conversation, not just to receive a rating. Bring your self-review, your top wins, and two or three questions about what happened in calibration and what's expected for the next level.

The companion guide on how to prepare for your performance review conversation covers what to bring, how to advocate for yourself in real time, and what to do if the rating surprises you.

The timeline at a glance

Phase	When	Focus	Key actions
Phase 1	90 days out	Build evidence	Start win log, run rubric gap check, identify target projects
Phase 2	60 days out	Align and amplify	Manager alignment conversation, visibility push, cross-team work
Phase 3	30 days out	Package and prepare	Draft self-review, peer feedback strategy, write manager brief
Phase 4	Final week	Execute	Finalize self-review, brief advocates, prepare for review meeting

---

Most engineers treat review season like a pop quiz: it shows up, they scramble, and they hope their manager remembers the good stuff. The engineers who get promoted treat it like a project with a deadline, working backward from the review date and building their case week by week. CareerClimb helps you run that project year-round — logging wins as they happen, identifying rubric gaps, and preparing the materials that make calibration a formality. Download CareerClimb and start building your case before the next review cycle begins.