Q2 Compensation Review: 3-Week Prep Timeline

Q2 Compensation Review: The 3-Week Preparation Timeline Every Senior Engineer Needs

Your Q2 compensation review is approaching, and most senior engineers will find out their adjustment after it’s already been decided. The number shows up in an email or a brief 1:1, and by then the window for influence has closed.

That’s not how this works at well-run companies. And even at poorly-run companies, the weeks before comp review cycles are when your manager is building the case (or not building the case) for your adjustment. What you do in those weeks matters more than what you did in the six months prior, because it shapes how your work gets framed, remembered, and ranked.

Q2 comp cycles at most major tech companies kick off in April and wrap up by late May. Whether you have three weeks or more before your cycle begins, this timeline applies. Three weeks is enough time to meaningfully change your outcome. Not by working harder, but by making the work you’ve already done visible and legible to the people who decide your number.

Here’s the week-by-week breakdown.

Week 1: Salary Review Preparation Starts With Your Evidence Base

The single biggest mistake engineers make in comp season is assuming their manager remembers what they did. Your manager has six to twelve direct reports. They’re juggling their own performance narratives, headcount planning, and whatever fire is burning this sprint. They remember the last two weeks clearly. Everything before that is a blur of merged PRs and project names.

Your job in week one is to make their job easier by assembling the raw material they need to advocate for you.

Pull Your Work Log

If you’ve been keeping a weekly work log, this takes an hour. If you haven’t, it takes a full evening. Go through your commits, design docs, code reviews, project trackers, and any docs you authored or co-authored in the last six months. Build a list of everything meaningful you shipped or contributed to.

Translate Technical Output Into Business Outcomes

This is where most engineers leave money on the table. “Migrated the payments service to the new API” is a technical description. “Reduced payment processing latency by 40%, which unblocked the checkout team’s Q1 conversion target” is a business outcome. Your manager doesn’t present your work to the comp committee using your technical language. They present it using business language. Give them the business language.

For each major project, write one sentence that answers: what changed for the business because this work existed? Revenue impact, cost reduction, reliability improvements tied to customer experience, developer productivity gains tied to shipping velocity. If you can attach a number, attach a number. If you can’t, describe the counterfactual: what would have happened if this work hadn’t been done?

Identify Your Top Three Contributions

Not ten. Three. Your manager will most likely use two or three examples when making the case for your adjustment. Pick the ones with the clearest business impact, the broadest scope, or the most visible cross-team collaboration. These are your anchors.

Document Scope Expansion

If your responsibilities have grown since your last review (owning a new system, mentoring junior engineers, leading a workstream you didn’t lead before), write that down explicitly. Scope expansion without title or comp adjustment is the most common form of under-compensation in tech. But nobody will notice it unless you name it.

One of my coaching clients, a senior backend engineer at a mid-size fintech company, went through this exercise last year and realized she’d taken ownership of an entire service tier that wasn’t in her original scope. She’d been maintaining it for five months without ever framing it as a responsibility expansion. When she added it to her evidence document with the associated reliability metrics, her manager said he hadn’t realized how much of that system she owned. That single line item became the anchor of her comp adjustment case, and she went from the standard 3% to an 8% raise.

Week 2: The Compensation Negotiation Conversation Before the Conversation

Week two is when most engineers do nothing. They assume the process will take care of them. It won’t.

The comp review process at most companies works like this: your manager writes a summary of your performance, proposes a compensation adjustment, and then defends that proposal in a calibration session with their peers and their manager. The calibration session is where the real decisions happen, because that’s where your manager’s proposal gets compared against everyone else’s.

Your goal in week two: make sure your manager walks into that calibration session with the strongest version of your story.

Schedule a Pre-Review 1:1

This isn’t your regular weekly sync. This is a dedicated conversation about your performance and compensation expectations. Frame it directly: “I know comp reviews are coming up. I’d like to spend 30 minutes making sure we’re aligned on how the last two quarters went and what I’m hoping for.”

Some engineers feel awkward about this. That awkwardness is costing you money. Research from Carnegie Mellon’s Linda Babcock, documented in her book Women Don’t Ask, shows that people who initiate compensation conversations earn significantly more over their careers than those who wait to be offered adjustments. The discomfort is real, but the cost of avoiding it compounds.

Share Your Evidence Document

Send your manager the summary you built in week one, ideally 24 hours before the 1:1. Tell them: “I put together a summary of my key contributions over the last two quarters to make the review process easier. Happy to walk through it or answer questions.” You’re not being pushy. You’re being organized. Every manager I’ve worked with has appreciated this.

Name Your Expectation

This is the part that takes courage. In the 1:1, say what you’re hoping for. Not in vague terms (“I’d like to be recognized for my contributions”) but in specific terms (“Based on the scope increase and the impact of the payments migration, I believe an adjustment to [X band / X percent / X level] is appropriate”).

You might not get a direct answer. That’s fine. The point isn’t to negotiate in the room. The point is to anchor your manager’s thinking before they write their proposal. If you say nothing, they’ll anchor on whatever number feels safe and easy to defend. If you name a specific expectation backed by evidence, they have to engage with it.

Another coaching client, a senior full-stack engineer at an enterprise SaaS company, told me he’d never once named a number in a comp conversation. He’d always said some version of “I trust you to do the right thing.” When I asked what his adjustments looked like, he said 2-4% every cycle. The first cycle after he named a specific expectation (a 12% adjustment, backed by market data and a documented scope increase), he got 9%. Not the full ask, but more than double his historical average.

Ask About the Process

Different companies run comp reviews differently. Ask your manager: When is the calibration session? What information do they need from you? Is there a self-review component? Who else is in the room when decisions are made? Understanding the mechanics helps you prepare for them. I’ve seen engineers at the same company have wildly different comp outcomes because one understood the process and the other didn’t.

Week 3: Strengthen the Senior Engineer Raise Case With Cross-Team Signal

Your manager is your primary advocate, but they’re not the only voice in the room. Week three is about making sure the broader signal around your work is strong.

Request Feedback From Cross-Team Partners

If you collaborated with engineers, PMs, or leads on other teams, ask them to send a short note to your manager. Something like: “Hey, I worked with [you] on the checkout reliability project and wanted to flag that their technical leadership on the API design was a big factor in us hitting our Q1 targets.” Keep it specific, keep it short, and make it easy for them by suggesting what to highlight.

This isn’t gaming the system. Calibration sessions rely heavily on cross-team signal because managers can’t directly observe work that happens outside their team. If there’s no cross-team signal, your manager has less ammunition.

Check Your Peer Feedback

If your company has a formal peer feedback mechanism, look at what’s already been submitted. If it’s thin, gently remind the people you’ve worked with most closely. Peer feedback that arrives after calibration is worthless.

Update Your Internal Profile and Self-Review Documents

If there’s a self-review component, write it with the same rigor you applied to your evidence document. Use business language. Lead with your top three contributions. Don’t be modest. The self-review isn’t a personality test. It’s a data input to the calibration process. A well-written self-review makes your manager’s job easier and signals that you take your career seriously.

Know Your External Market Value

This isn’t about threatening to leave. It’s about having calibrated expectations. Check levels.fyi, Glassdoor, and Blind, and tap any recent offers from your network. If your current compensation is significantly below market for your level and location, that’s a data point worth sharing with your manager. Framing matters: “I want to make sure my comp reflects my contributions here, and I’ve noticed the market has moved” is collaborative. “Pay me more or I’ll leave” is adversarial and usually backfires.

What Happens After the Q2 Compensation Review

Sometimes you get the adjustment you asked for. Sometimes you don’t. Either outcome requires a follow-up.

If You Got What You Wanted

Thank your manager and ask what you’d need to demonstrate for the next level or band. Start the clock on the next review cycle immediately.

If You Got a Partial Adjustment

Ask your manager what the limiting factor was. Was it budget constraints, calibration ranking, or a gap in the evidence? Budget constraints are impersonal. Calibration ranking means someone else had a stronger case. An evidence gap means you have something specific to fix. Each of these requires a different response, so get specific about which one it was.

If the Comp Committee Rejected the Proposal

This happens more than managers admit. Sometimes your manager went to bat for you and lost. If you suspect this is the case, ask directly: “Did you propose a higher adjustment that got calibrated down?” A good manager will tell you the truth. That information matters because it tells you whether the problem is your manager’s advocacy or the committee’s budget.

In Any Case

Get the answer in writing, either by sending a follow-up email summarizing the conversation or by asking your manager to document it. Verbal promises about “next cycle” have a habit of evaporating when org changes happen.

And if the gap between your expectations and reality is large enough, it might be worth examining whether you’re in the right role. Sometimes the best raise is the one you negotiate at a new company. Understanding the broader dynamics of salary negotiation gives you a framework for that conversation whether you’re staying or leaving.

What If Your Situation Doesn’t Fit the Timeline?

Your Manager Is Unresponsive or Avoids the Conversation

This is information. A manager who won’t engage with your comp expectations before the review cycle is either conflict-averse, not planning to advocate for you, or doesn’t have the authority to influence the outcome. In any of those cases, you need to build relationships with skip-level leadership. Your manager’s manager is often the person who actually controls the budget.

Comp Is Frozen Company-Wide

Freezes are real, and no amount of preparation overcomes a hard budget constraint. But freezes rarely last more than one or two cycles, and the evidence document you build now carries forward. The engineers who get the biggest adjustments when freezes lift are the ones who documented their contributions during the freeze, not the ones who stopped paying attention because “it wouldn’t matter.”

Your Company Does Surprise Reviews With No Predictable Timeline

Build the evidence document anyway and keep it updated quarterly. When the review lands, you’ll have 48 hours of lead time at best. Having a current evidence document means you can send it to your manager the same day the cycle opens, while everyone else is scrambling to remember what they did.

You Started Recently and This Is Your First Review

The three-week timeline still applies, but adjust your expectations. First-cycle adjustments are typically modest. The real value of running this process early in your tenure is that it sets the precedent for how you engage with comp reviews going forward. Your manager will remember that you came prepared.

The Meta-Lesson

Compensation reviews aren’t a single event. They’re the output of a system. The engineers who consistently get strong comp outcomes are the ones who treat visibility, evidence collection, and manager alignment as ongoing practices, not last-minute scrambles.

If you’re starting this timeline today, you’re already ahead of most of your peers. If you’re reading this after the review already happened and you’re disappointed with the result, bookmark this for the next cycle and start your weekly work log today.

Three weeks of focused preparation won’t fix six months of invisible work. But it will make sure the work you did gets seen, gets remembered, and gets valued.

Ready to structure the kind of career narrative that performs well in comp reviews, promotion committees, and interviews? My SWE Interview System includes frameworks for articulating impact that work in all three contexts.