How to Ask for a Raise as a Software Engineer: Scripts and Numbers
Where software engineers actually hold leverage, how to build a target number you can defend from published wage data, and the words to use in the meeting.
By Lena KowalczykOct 28, 2026 · 8 min read
Asking for a raise as a software engineer works best when you stop arguing about effort and start arguing about replacement cost: what it would take your employer to hire and onboard someone who can do what you already do. That means a target number built from published wage data for your own state or metro, a short list of systems and outcomes you own, and timing tied to your company's compensation cycle.
This guide covers the leverage specific to engineering work, the preparation steps in order, lines you can say out loud, and a readiness checklist to run before you book the meeting.
What Leverage You Actually Have
Leverage in engineering is concrete, not rhetorical. Four sources come up repeatedly, and each can be sized in dollars before you walk in — using your own employer's bands and published wage data, not assumptions.
Production ownership and on-call. If you are the named owner of a service, a deployment pipeline or a data store, your employer's alternative to paying you more is a handover plus a hiring cycle. Size it: count the weeks of on-call you carried in the last 12 months, list the systems where you are the only reliable escalation point, and ask your manager how many months a backfill plus ramp-up would take. Months multiplied by your monthly cost to the company is the number you are implicitly negotiating against.
Scarce specialisms. Security, distributed systems, embedded, platform and data work often clear above general application work, but the size of the gap is set by individual employers and varies by metro — so pull it rather than quoting it. The BLS Occupational Employment and Wage Statistics programme publishes median and percentile annual wages for software developers by state and metropolitan area (U.S. Bureau of Labor Statistics, May 2025), and ONET OnLine publishes 2025 median wages for Software Developers, SOC 15-1252.00 (ONET OnLine, 2025). The distance between the median and the 75th or 90th percentile in your metro is the practical ceiling of a within-role ask; most within-role asks land in the 5% to 12% range, with bigger steps usually requiring a level change.
Labour market demand. BLS projects employment for software developers, quality assurance analysts and testers to grow much faster than average from 2025 to 2035, with openings projected each year on average across that decade (U.S. Bureau of Labor Statistics, 2025). That entitles you to nothing, but a manager who loses you faces a competitive hiring market, and it is fair to say so.
Scope above your title. If you review other people's designs, run releases, or mentor juniors, you are already doing part of a senior or lead job. BLS notes software developers can advance into project management specialist or computer and information systems manager roles (U.S. Bureau of Labor Statistics, 2025); the step before that is usually scope you are carrying unpaid.
Steps to Prepare
- Pull your market rate from a named source. Start with the BLS Occupational Employment and Wage Statistics tables for software developers (May 2025), filtered to your state and metro area, and note for each figure whether it is hourly or annual and whether it is a median, mean or percentile. Cross-check against O*NET OnLine's 2025 median wages for Software Developers. Write the figures and the data year down — you will cite them in the meeting.
- Find your employer's internal band. Ask HR or your manager for the range attached to your level and location, and where in it you sit. In states and cities with pay transparency rules, your company's own job adverts for your level may already show the range.
- Quantify six to ten achievements. For each, write the system, the measurable change and the period: incidents reduced, build time cut, cost or revenue affected, features shipped, engineers onboarded. Specific claims become the written justification your manager passes upward; vague ones get discounted.
- Document scope above your title. List responsibilities you hold that appear in the next level's job description. That converts a raise request into a promotion case, which is often funded from a different budget.
- Set an opening, a target and a floor. Express all three as annual base figures: the opening at the top of what your data supports, the target at or just above your metro's published median, the floor as the number below which you start interviewing. Note separately what you want for bonus, equity refresh and title.
- Pick the timing. Raise it 6 to 8 weeks before your review or budget planning closes, ideally within a month of a delivery your manager publicly praised.
- Book a dedicated meeting. Call it a compensation review, not a one-to-one add-on, and send your one-page case 24 to 48 hours ahead.
What to Say
Insert the annual base figures you pulled from BLS Occupational Employment and Wage Statistics (May 2025) for your own metro where these lines refer to the median and to your current base.
Opening the ask
"I'd like to talk about base salary. The BLS Occupational Employment and Wage Statistics data for May 2025 puts the median annual wage for software developers in this metro above where I sit today, and I've carried on-call for the payments service for 14 of the last 18 months on top of regular delivery. I'm asking for a 12% increase to base, which lands just above that published median."
If you are told the budget is fixed
"I understand this cycle is allocated. Two things would help. First, can we agree in writing to that 12% effective at the start of the next cycle, with the scope I already cover written into my level? Second, if base is frozen this year, I'd like a one-off adjustment, an equity refresh, or a training budget instead — and a review date 90 days out."
If you are remote and told your location caps you
"The work is identical to the team members in the headquarters metro, where the published 75th percentile annual wage for software developers is higher than my band's ceiling. I'm not asking to match it. I'm asking for 8%, between my location band and theirs. If the policy can't move, tell me which band I'd need to be in and what qualifies me for it, so I'm not guessing."
Before You Ask: Checklist
- Pulled median and 75th-percentile annual wages for software developers in your state and metro from BLS Occupational Employment and Wage Statistics (May 2025), with the data year written down.
- Confirmed your employer's internal band for your level and location, and where you sit in it.
- Written six to ten achievements with a number and a date range attached to each.
- Listed the responsibilities you already perform that appear in the next level's job description.
- Fixed three annual base figures — opening, target and floor — plus what you would accept if base is frozen.
- Checked the review and budget calendar and booked the meeting 6 to 8 weeks before it closes.
- Sent a one-page written case to your manager at least 24 hours ahead.
- Decided what you will do if the answer is no, including whether you are ready to interview, and set a date to revisit.
Frequently asked questions
Do I need a competing offer to get a raise?
No, and leading with one backfires if you would not actually leave. A market-data case plus documented scope carries most cycles. If you do hold an offer, state the base, title and deadline once, factually, and say plainly that you would prefer to stay at a matched or near-matched number. Never bluff an offer you do not have.
My manager says there is no raise budget this year. What now?
Move off base pay onto three things usually funded separately: a title and level change effective next cycle, a one-off bonus or equity refresh, and a written commitment with a date and a percentage. Ask for the specific criteria in email and schedule a follow-up 90 days out. If nothing is in writing after the second meeting, treat that as the answer and start checking openings — BLS projects much-faster-than-average growth for software developers through 2035.
I got a counteroffer after resigning. Should I take it?
Compare it against why you were leaving. If pay was the only issue and the counteroffer meets your target in base — not a retention bonus paid over 12 months — it can be reasonable. If you were leaving over scope, management or on-call load, money rarely fixes it. Get the increase in base, effective immediately, in writing, plus the scope change you wanted.
How do I argue for pay as a fully remote engineer?
Separate the band your employer assigns to your location from the band your work merits. Pull BLS Occupational Employment and Wage Statistics figures (May 2025) for both your metro and the company's headquarters metro, request the written location policy, and anchor between the two rather than demanding the headquarters number.
How often can I reasonably ask?
Once per annual cycle for a standard increase, and separately whenever scope changes materially — taking over a service, absorbing a departed colleague's work, or joining the on-call rota. Make the scope-change ask within a month of the change, before the new work becomes your assumed baseline.
Sources
- U.S. Bureau of Labor Statistics — Software Developers, Quality Assurance Analysts, and Testers : Occupational Outlook Handbook (2025-05)
- O*NET OnLine (U.S. Department of Labor, Employment and Training Administration) — Summary Report for: 15-1252.00 - Software Developers (2025)
Your coach for this guide
Lena builds long-form conversations with workers across industries, chasing the specific texture of a job rather than its title. She's most interested in the gap between what a role is called and what it actually asks of someone.
