Raises are not won in the meeting where you ask for one. They are won months earlier, by the evidence you collected when nobody was watching. By the time your first review arrives, the story about you is already written; reviews mostly ratify impressions formed in the first quarter. So the real question of your first 90 days is not “how do I survive probation?” It is “how do I make my future raise case impossible to argue with?”
That reframe changes everything about how you spend the next three months. Most new hires optimize for not breaking anything. You are going to optimize for building a paper trail, because the colleague who gets the raise you deserved usually isn’t better. They’re better documented.
Here is the 90-day plan, in order.
Days 1–30: Learn the scoreboard
You cannot score points in a game whose scoreboard you can’t see. Your first month has one job: figure out how pay decisions actually get made at this company, because it is never how the handbook says.
Find out what your manager is measured on. Your manager is your single biggest pay lever, and they have their own boss, their own targets, and their own review coming. Ask directly in your first one-on-one: “What are the two or three numbers your leadership cares about this quarter?” Work that moves your manager’s numbers gets remembered and rewarded. Work that doesn’t gets thanked. Every task you’re handed for the next year should be silently sorted into one of those two buckets.
Map who actually decides pay. In most companies your manager does not set your salary. They advocate for it, and someone above them (a director, a comp committee, HR with a budget spreadsheet) approves or trims it. Ask a tenured teammate over coffee: “How do raises actually work here? Who signs off?” You are looking for the real chain, because your raise case eventually has to survive a conversation you won’t be in. If your manager can’t defend your number in one sentence to their boss, you don’t get it.
Find the calibration calendar. Nearly every company with more than 50 people runs compensation on a cycle: performance calibration in one month, budget allocation in another, raises effective in a third. These dates are rarely secret, just rarely asked about. Once you know that calibration happens in, say, February, you know your evidence needs to be assembled by January, and that a raise conversation in March is a year too late. Asking after the money moves is the single most common timing mistake, and it is entirely avoidable.
While you’re mapping the scoreboard, benchmark yourself. Run your role through a salary calculator for your market, and if the number you accepted looks light, check whether you’re underpaid now, not in month eleven. Starting below market means your first raise case has to argue for a correction plus growth, and you want to know that early.
Days 31–60: Ship one win and start the file
Month two is about creating the first piece of evidence and the system that will hold all the rest.
Ship one attributable win. Not a heroic project. A finished, visible, unambiguously-yours win: the onboarding doc everyone complains about, the report that eats Friday afternoons, the ticket nobody owned. Size matters less than three properties: it’s done (not in progress), it’s attributable (your name on it), and it’s narratable (one sentence, understandable outside your team). “She’s been here six weeks and already fixed X” is the sentence you’re trying to plant. Early wins get retold, and retold stories become reputation at zero extra cost to you.
Open the brag document the same week. This is the highest-return two minutes of your working week. One running file, updated every Friday, in a format your future self can hand over as evidence. Use this:
| Date | What I did | Impact | Witness |
|---|---|---|---|
| 2026-08-14 | Automated the weekly ops report | Saved ~3 hrs/week for the team | Priya (ops lead) |
| 2026-08-21 | Fixed onboarding doc, closed 4 stale tickets | New-hire setup time cut from 2 days to 1 | Marcus (manager) |
| 2026-09-02 | Caught pricing bug before quarterly invoice run | Prevented ~$12k in misbilling | Finance Slack thread (saved link) |
The Witness column is the part almost everyone skips and the part that makes the document work. A claim with a name or a saved link attached is evidence; a claim without one is just your opinion of yourself. Screenshot the Slack praise. Save the client email. Note who was in the room. When raise season comes, you will not be reconstructing your year from memory while your manager skims twenty reviews. You’ll be handing over receipts.
If your win involved learning something new, log that too. Skills you can prove are comp leverage, and as we’ve covered in degrees versus certifications, the market pays for demonstrated capability far more reliably than for credentials collected.
Days 61–90: Set the bar out loud, then clear it
Month three is where you convert quiet work into an explicit, agreed-upon standard, because a raise case built on a bar your manager defined is nearly impossible to wave away.
Have the expectations conversation around day 75. Ask for 30 minutes and say some version of this:
“I want to make sure I’m aimed at the right things. How would you say my first quarter has gone? And looking ahead: by my one-year mark, what would ‘exceeding expectations’ look like in this role, specifically? I’d like to write it down so we’re working from the same list.”
This script does three things at once. It surfaces problems while they’re cheap to fix. It gets your manager to define the bar out loud, in their own words, on a date you can cite. And the last line (“I’d like to write it down”) turns a vague chat into a referenceable agreement. Send a short follow-up email summarizing what they said. That email is now the opening exhibit of your raise case: “In October you said X would constitute exceeding expectations. Here’s the evidence I did it.”
Build visibility without the cringe. You do not need to perform. You need to be legible. Three low-cringe moves: give credit loudly and specifically to others (people repay it, and it marks you as secure); post short “shipped” updates in public channels stating what changed and who it helps, in two sentences, no victory lap; and send your manager a five-bullet 90-day summary nobody asked for: shipped, learned, owning next quarter. That last one takes ten minutes, almost nobody does it, and it repositions you from “new hire settling in” to “person who manages their own scope.”
Pre-build the raise case. By day 90 you should have: the bar, in your manager’s words, in writing; a brag document with dated, witnessed entries; one retold win; and the comp calendar. That is a raise case sitting in a drawer, months before you need it. When the window opens, the ask itself is a solved problem. Our full guide on how to negotiate salary covers the conversation mechanics, but understand that the negotiation is the last 10% of the work. You just did the other 90.
The five most common first-90-day mistakes
- Keeping your head down. Quiet competence feels safe and reads as absence. Invisible excellence is a donation to your employer.
- Working hard on unmeasured things. Effort spent outside the company’s scoreboard earns gratitude, not money. Check the bucket before you burn the weekend.
- Waiting to be evaluated instead of asking. If you don’t request the expectations conversation, you get graded against a bar you never saw, defined after the fact.
- Starting the brag document “later.” Month-eleven you cannot recover month-two evidence. The Slack messages are gone, the witnesses have forgotten, the numbers are fuzzy.
- Confusing being liked with being valued. Likability helps, but budget meetings run on justification, not affection. Managers fight hardest for the people whose case writes itself.
The long game this sets up
The first 90 days is one move in a longer game. Compensation growth inside a single company is slow by design: annual cycles, 3–4% budgets, bands that quietly cap you. That’s the trap dissected in why your salary stopped growing, and the early-evidence habit is your best defense against it, because documented people are the ones budgets bend for.
But keep the bigger levers in view too. Sometimes the right move after a strong first year is not a raise request but a market move, and for remote-capable roles the gap between local pay and global pay is enormous. We ran those numbers in remote work and global pay arbitrage: same skills, same hours, 2–3x difference based on who employs you. Your brag document works just as well in an external interview as in an internal review. Evidence is portable.
And if the first 90 days teach you that you picked the wrong game entirely, that’s valuable too. Browse the careers hub to see what comparable roles actually pay worldwide before you invest a second year.
Start the file today. Ask the scoreboard questions this week. Your month-twelve self, sitting across from a manager with a compensation spreadsheet open, will be very glad you did.