How to Negotiate a Higher Salary as a Software Engineer
Where the leverage actually sits in an engineering pay conversation, how to time the ask around review cycles, and which federal wage tables to quote.
By Tobias Lindqvist · Oct 06, 2026 · 9 min read
Negotiating as a software engineer is mostly an evidence problem, not a confidence problem. The engineers who move their base pay show up with a researched annual figure for their occupation code and metro area, a written record of what they shipped, and a date that lines up with how their employer actually sets budgets.
This guide covers the three kinds of leverage that matter in this role, a sequence for preparing and making the ask, and a checklist to run through before you sit down. It does not quote dollar amounts at you — it tells you which named government tables to pull your own numbers from, so the figure you bring is current and specific to where you work.
What Leverage Looks Like in This Role
Leverage is anything that makes paying you more cheaper than replacing you. Four sources of it are specific to software engineering, and each one translates into a number you can state out loud.
A competing written offer. This is the only kind of leverage that comes with its own price tag attached. Its value in the conversation is exactly the gap between your current annual base and the annual base in the written offer — stated in matched units, annual against annual, not annual base against a total-compensation headline that includes a signing bonus or equity. If you are weighing an offer, CareerOneStop (U.S. Department of Labor) advises expressing appreciation and interest and then requesting at least 24 hours to decide before you negotiate. CareerOneStop also notes that because future increases are often calculated from starting pay, moving the starting number has a long-term effect on earnings — which is why a one-time bonus is not a substitute for base.
A scarce, named technical skill. O\*NET OnLine (U.S. Department of Labor/Employment and Training Administration) flags TensorFlow as a "Hot Technology" among the analytical and scientific software used by Software Developers. If you are the person maintaining that kind of system, the number to argue for is the distance between the median and an upper percentile in the OEWS annual wage estimates for Software Developers, occupation code 15-1252, May 2023 (U.S. Bureau of Labor Statistics). Pull the table for your state or metro area, subtract the median annual wage from the 75th percentile annual wage, and divide by the median — that percentage is the evidence-backed size of your ask, and it comes from a federal survey rather than from you.
Credentials and formal preparation. O\NET places Software Developers in Job Zone Four, meaning considerable preparation is needed and most occupations in that zone require a four-year bachelor's degree, which also matches the typical entry-level education the Bureau of Labor Statistics lists for this occupation group in 2025. Because a degree is the baseline, a degree alone is not leverage. A certification can be, and O\NET's listing for 15-1252.00 includes a tool for finding relevant certifications and state licenses by location. Certifications move money when you attach them to scope you have taken on — not on their own.
Timing, which behaves like a busy season. The University of New Hampshire Professional & Continuing Studies (2023) notes that many companies set fixed times of year for performance review and raise consideration, and that review season is generally a good time to ask when feedback has been positive. PrideStaff recommends raising the subject several months before a quarterly or annual review so your supervisor has time to consider your contributions. Harvard Professional & Executive Development advises initiating the conversation after a positive review, and checking that it has been at least a year since your last one.
Background conditions help too. The Bureau of Labor Statistics projects employment of software developers, QA analysts and testers to grow 10 percent from 2025 to 2035, much faster than the average for all occupations, with projected annual openings over the decade coming mostly from replacement needs. That is a hiring-cost argument, not a personal one — use it as context, not as your main case.
Two cautions on figures. Always separate annual base salary from total compensation; the Bureau of Labor Statistics notes in the Occupational Outlook Handbook Pay tab (2025) that workers may be compensated through annual salaries, hourly wages, commissions, tips or bonuses, and that earnings vary by experience, responsibility, performance, tenure and geographic area. And OEWS data excludes self-employed workers, so contractors will not find themselves in those tables.
Steps to Prepare and Ask
- Fix your occupation code first. Software Developers are classified under 15-1252.00 by O\*NET, distinct from the older 15-1132.00 code for Software Developers, Applications. Using the current code keeps you out of stale tables.
- Pull the figures. Open the OEWS annual wage estimates for Software Developers (15-1252), May 2023, from the Bureau of Labor Statistics, and write down three numbers for your state or metro area: the median annual wage, the 75th percentile annual wage, and the national mean annual wage. Note the median annual wage for software developers published in the Occupational Outlook Handbook Pay tab (U.S. Bureau of Labor Statistics, 2025) as your national reference point. Label every number annual, and label it median, mean or percentile — you will be asked.
- Choose one target number and one floor. Your target is usually the OEWS 75th percentile annual figure for your area; your floor is the number below which you would start interviewing elsewhere. Both are annual base, excluding bonus and equity.
- Document the wins. Write six to ten lines, each naming a system, a date and an outcome. Favour anything that maps to the factors the Bureau of Labor Statistics names in the 2025 Pay tab — responsibility, performance and tenure — because those are the words your manager's own compensation guidance will use.
- Pick the date by working backwards from review season. PrideStaff recommends flagging your interest in a raise several months before a quarterly or annual review. Harvard Professional & Executive Development advises making the ask after a positive review and confirming at least a year has passed since the last one. Book a dedicated meeting; do not bolt it onto a one-on-one.
- Open by naming the researched range, not a feeling. Say which table it came from, its date, and that it is annual base. Then say your target number and stop talking.
- Separate base from everything else. If the counter arrives as a one-time bonus or extra equity, say so plainly: CareerOneStop notes that future increases are often based on starting pay, so a bonus leaves your next raise calculated from the old base.
- If the answer is no, convert it into criteria and a date. Ask what specific scope or results would justify the number, ask for that in writing by email, and set a follow-up for 90 days out. If no criteria are offered, that is information about the employer — use the time to look at what the OEWS table says comparable roles pay in your area and decide whether to test the market.
- Record what was agreed. Send a short summary email the same day with the number, the effective date and any conditions.
Negotiation Checklist
Work through these before the conversation, not during it.
- Look up the OEWS annual wage estimates for Software Developers (15-1252), May 2023, from the Bureau of Labor Statistics, for your state or metro area, and write the median and 75th percentile annual figures on one page.
- Note the national mean annual wage and the national employment figure for Software Developers from the same May 2023 OEWS release for context.
- Write down your current annual base separately from your bonus, equity and any on-call differential, so you can compare base to base.
- Choose one target annual base number and one walk-away floor, and say both out loud once before the meeting.
- List six to ten documented wins with dates, systems and outcomes.
- Check the calendar: confirm at least a year since your last review (Harvard Professional & Executive Development) and that you are ahead of, not inside, the review window (PrideStaff).
- Check O\*NET's certification and state licence finder for 15-1252.00 and note any credential you hold or are close to completing.
- Draft and rehearse one sentence answering "that is above our band," naming the table and its date.
- Draft the follow-up email you will send if the answer is no, with a 90-day review date already in it.
- Book a dedicated meeting slot rather than using an existing one-on-one.
Frequently asked questions
What number should I say first?
Say the researched one, and attach its source and units. A usable line: "For software developers in this metro, the May 2023 OEWS percentile table from the Bureau of Labor Statistics puts the 75th percentile annual wage at [figure you looked up]. Given the systems I own, I'm asking for that as annual base." Naming the table, the year and the word 'annual' keeps the conversation on a shared document instead of on competing impressions.
They said there's no budget. What do I do next?
Turn the refusal into criteria and a date before you leave the room: "I understand. What specific scope or results would move me to [your target number], and can we put that in writing with a review in 90 days?" Then send the summary email yourself the same day. If no criteria come back, treat that as data — the Bureau of Labor Statistics projects 10 percent employment growth for software developers, QA analysts and testers from 2025 to 2035, with most projected annual openings coming from replacement needs, so there is a market to test.
Is it better to negotiate a new offer or a raise in my current job?
A new offer gives you a cleaner number to negotiate against, and CareerOneStop (U.S. Department of Labor) advises waiting until an offer is on the table before discussing salary, then thanking the employer and asking for at least 24 hours to decide. CareerOneStop also notes that because future increases are often based on starting pay, the starting figure has a long-term effect — so negotiate the annual base rather than the signing bonus. Internally, timing does the same job: ask after a positive review, and flag your interest several months ahead of the review cycle (PrideStaff).
Sources
- U.S. Bureau of Labor Statistics — Software Developers, Quality Assurance Analysts, and Testers : Occupational Outlook Handbook (2025)
- U.S. Bureau of Labor Statistics — 15-1252 Software Developers (OEWS, May 2023) (2023-05)
Written by
Tobias Lindqvist
Tobias writes on trades, apprenticeships, and the kinds of careers that don't start with a resume. He's interested in skill as a form of dignity, and in how little the discourse around work usually accounts for hands.
