Think Like Your Manager in Performance Reviews
After a performance review, some developers wonder, "Why didn't I get promoted? Why was the raise small?" Often the problem isn't how hard you worked. It's how prepared your manager was for the meeting that matters.
As companies grow, promotion and salary decisions aren't made in your review conversation. They're made in a separate meeting - the calibration meeting. That's where your manager advocates for you. If she has no data, she stays quiet.
In this post, we'll talk about what a calibration meeting is, how your manager prepares for it, and what you can contribute to that preparation.
What Is a Calibration Meeting?
When a company does a performance review cycle, each manager rates a few of their team members at different levels. Junior A is good, Junior B is very good, Junior C is excellent. But what does "very good" mean across the whole company? Every manager measures "excellent" differently.
In the calibration meeting, managers from different teams gather. The goal is to maintain a consistent standard across the company. To agree: "Yes, both excellent in your team and excellent in another team mean the same thing." At the same time, because raise and promotion budgets are limited, decisions like "this person gets promoted, that person doesn't" are made in this room.
What does a manager bring to the calibration table? Data. Records of their employees' code review feedback, completed projects, responsibilities given, and most importantly, documents proving these things happened.
Your Manager's Defense of You Depends Entirely on Data
In calibration, your manager is discussing who gets promoted, who gets a raise. If you have evidence, the argument is strong. "Look, this person didn't just solve problem X; they finished Y team's 3-week job in 2 weeks, and here and here they refactored code and reduced technical debt." Another manager hears that and says, "Okay, I believe it."
No data? Your manager is left with a feeling. "This person is very hardworking." But "very hardworking" is not an argument; it's an emotion. When another manager asks, "What did they actually deliver?" your manager answers, "I'm not sure, but they're nice, and they're in the office at 9 every day."
The person making your case in that room is your manager. But she's equipped with data that comes from you.
Making Your Manager Strong in Calibration Is Your Job
At the start of the performance cycle (usually January), your manager asks you, "What are your goals for the year?" At the end, "How would you rate yourself?" These aren't just check-ins; they're data gathering. Because she'll tell that story in calibration.
An effective software engineer gives her two things during this cycle:
1. Concrete metrics
Not "I'm very hardworking," but "In Q1, I modularized X microservice, raised test coverage from 45% to 78%, and failure rate dropped 8 percentage points." Dates, numbers, proof. Your manager can say this out loud.
2. Documented evidence that the work happened
PRs that went through code review, design documentation, architecture contributions, help given to other teams. These are links or PDFs your manager has. "Look, this project was led by her, she wrote this documentation" - she can show.
Pay attention to their preferred format. Don't recite accomplishments to your manager like they're a crime. It should come naturally: "I approached this project this way, I hit this obstacle, here's how I solved it."
Preparing a Calibration Brief
Some companies ask managers to fill out a form before calibration. It's called a "self-assessment." Most engineers fill it out as a formality. But this is your defense brief.
To make your manager strong in calibration, you can prepare a brief like this. Share it with her, make her life easier:
A good calibration brief looks like this:
Title: "Performance Summary and Calibration Brief"
Header: Your role, title, team, period (Jan-Jun 2026, etc.)
Goals vs. Results
- The 3-4 goals set at the start
- What you did against each
- Numbers, wins
Concrete Wins (as bullet headlines)
- Technical Contribution: "Re-architected X system, deployment time went from 45 min to 8 min"
- Cross-Team Work: "Spent two solid weeks with Y team solving Z problem"
- Skill Growth: "Took a machine learning course and brought a model into production"
- Team Support: "Mentored 3 juniors with code review and 1-1s this cycle; all passed the final exam"
Challenges (optional but impactful)
- What you didn't expect, how you adapted
- Shows problem-solving, not just execution
Links
- Important PRs, documentation, design docs
- Your manager can open these in calibration
One example of solving a quick jam
- "When X broke, the fix Y would have taken 2 days; I got it done in 4 hours"
- Short, story-based, not boastful
Example format:
== PERFORMANCE SUMMARY - 2026 H1 ==
Role: Senior Backend Engineer
Team: Data Processing
GOAL COMPLETION:
- Goal: Optimize Elasticsearch queries → Result: Refactored 4 problem queries, latency 1.2s → 320ms (73% improvement)
- Goal: Mentor junior engineers → Result: 2-hour weekly 1-1s with 4 juniors, all scoring 90%+ on reviews
- Goal: Complete tech debt roadmap → Result: 23-page strategy doc + API migration plan
TECHNICAL WINS:
**Infrastructure Stability:** Rewrote cron jobs, added failover mechanism. Uptime 99.2% → 99.8%
**New Feature:** Designed async export, led implementation end-to-end, delivered in 15 hours (estimate was 1 week)
LEARNING MOMENT:
• Spotted a gap in Kubernetes migration task and solved it before Infra team would've seen it
EVIDENCE:
- PR: github.com/...
- Doc: notion.so/...
What your manager says about you in calibration circles back to these details. "This person delivered these things last half" is what she'll say.
Monthly 1-1 Meetings With Your Manager
You build the foundation for this brief in your monthly 1-1s. Each month-end (or start), you sit with your manager for 30 minutes. The goal: "What did I do this month, are goals still aligned?"
Structure helps here:
- Last month's goals: Which I finished, which are still open?
- This month's work: 3-4 key wins or learnings
- Blockers: What slowed me down, what help I need?
- Next month's focus: What comes next?
You're giving your manager something to write down. Those notes become the source material for calibration.
Salary Negotiation Is Built on Calibration
If your manager advocates well for you in calibration, she's more flexible in salary talks. Because she's already told the company: "This person deserves an early raise, this person is someone I can count on," etc.
The opposite: if in calibration she said, "my team's average," then in salary talks she's stuck saying, "I can't go above average." Because you're already on record as average.
That's why the calibration brief is the foundation of salary negotiation. When your manager records you as "one of my top 3" and makes that case in calibration, she then asks you, "You deserve a raise; what number are you thinking?" That opening only exists because the brief did its job.
Two Warnings
Don't exaggerate your wins.
When writing the brief, if you feel pressure to claim "I did the whole project," pause. Multidisciplinary work is teamwork. Your piece is your piece. "I designed it first; then Y engineer led implementation while Q tester validated for production" - that's real.
Don't coach your manager.
Hand over your brief and don't say, "Make sure you say this in calibration." It's her meeting, her call. You supplied the data; she decides how much and how to use it.
Your Manager Speaking for You Truly Matters
They talk about "fair promotion systems." But in practice, the person who brings the most concrete evidence wins. Not the person who advocates for themselves - the person whose manager advocates for them.
For your manager to advocate well, you have to be the source of that data. The brief, the monthly 1-1 notes, the completed goals - you provide all of it. Your manager voices it in calibration.
A good calibration brief, then, means good communication between you and your manager.
To understand where you stand in the market, check the getSalary 2026 software engineer salary guide. Knowing where the market sees you makes the negotiation table feel less scary.