Ask for the Raise: Showing Your Value Without Bragging
If you never ask, your pay is still decided, just without your evidence. Ask before budgets are set, map your work to the level above, name a number, and if the answer is no, leave with what would make it yes and by when.
Key takeaways
- Ask before pay is decided, not after: find out when your company sets raises and book the talk a month or two earlier.
- Map your work to your company's career levels; it turns "I work hard" into "I do the work of the level above".
- Bring evidence from your brag doc, grouped by impact, with links.
- Name a number or a level, with reasons; a vague ask gets a vague answer.
- If the answer is no, ask what would make it yes, and agree a date to check again.
Contents
FAQ
When is the best time to ask for a raise?
A month or two before your company decides pay, often before the yearly review or budget, and soon after a visible win. Ask your lead when raises are decided; that answer alone helps.
What do I say if my boss says no to a raise?
Thank them, then ask what you would need to show for a yes and when you can look at it again. Write down the answer and send it back, then track it in your brag doc.
Sources
Only you and the owner see your answer and rating. Send private feedback
Enjoyed it? Support fx-blog with a coffee.
Related posts
Build the Ship You Want to Sail On: Culture and Giving Back
If a team's good habits live only in its lead, it works only while the lead is in the room. Repeat a few habits weekly: specific thanks, a calm reply to bad news, sponsoring people for real chances, and handing on what you learned.
Manage the Team: Goals, Trust and Delivery
Eleven goals nobody remembers, and a red result found in week 12, cost a lead the team's focus and the boss's trust. Set a few measurable results with one owner each, send a five-line update weekly, and report red early with a plan.
One-to-Ones That Matter, and Handling Conflict
Skip one-to-ones and you hear about trouble when someone stops coming to standup. Hold them weekly with their agenda first; when two people clash, talk to each privately, then together, and end on a shared rule, not a winner.
Comments
Oldest firstNo comments yet. Start the conversation.
Part 5 ended at Friday lunch, with Bun's question: if the client trusts Pip this much, and she's doing a senior engineer's work, is she paid like one? Pip has never asked for a raise. She pushes rice around her bowl.
"Won't Kit think I'm ungrateful?"
"Did he think that when you asked for feedback?" says Bun. "Bring him another good question. With evidence."
Dev Voyage: Open Ocean, in six parts:
Ask before the budget is set
Asking for money can feel rude. But your company decides your pay on its own schedule anyway. Asking puts your evidence on the table when it does.
Timing matters most. Once budgets are set, even a lead who agrees with you may have nothing left to give. So Pip asked Kit first: "When are raises decided here, and who decides?"
Budgets for the new year were set in late November. It was early October. She booked the conversation for the end of the month.
Map your year to the level above
"I work hard" is a feeling. "I'm doing the work of the level above, and here's the evidence" is a case. If your company has written career levels, read them. If not, ask your lead, and look at public frameworks such as Dropbox's engineering career framework or the collection on progression.fyi.
Pip put her brag doc next to the level above:
That table is the whole case: the brag doc Julia Evans recommends, started on probation, a year later doing its job.
Name a number, and plan for no
"I'd like a raise" invites "we'll see". Name a level, a number, or both. To find the number, look at what your role pays in your city: salary surveys, job ads that show ranges, friends you trust enough to ask.
Patrick McKenzie's essay on salary negotiation is written for job offers, but its core holds here: know the market and let your value lead. Harvard's Program on Negotiation adds one more: know your BATNA, your best alternative if there's no deal, so you can stay calm whatever the answer is. Don't bluff about an offer you wouldn't take. Leads remember.
If the answer is no, ask two things and write them down: what exactly would make it a yes, and when you'll look again. Send that back the same day, as in part 1. If it stays vague for two cycles, that tells you something about the ship.
Pip went into Kit's cabin with one page and a cup of tea.
Try it
This month:
Pip said yes before her tea went cold. Back at her desk, she opened her calendar: Monday, her first standup as lead of the checkout crew, with Brock in it. Reviews were already waiting, and a hiring request. She has no idea what a lead does on day one. The voyage continues in Dev Voyage: Uncharted Waters, starting with the move from best engineer to first-time lead.
Read this with your AI