Software Engineer Negotiation and Why Level Matters More Than Base
What are you negotiating?
Your offer or current pay
Market-rate band
Talking points
Email template
Timing
Coaching, not legal or financial advice.
Software engineer negotiation is mostly decided by level, not by base salary. A company sets a pay band for each level, so asking for 10,000 dollars more base inside the level you were offered moves you a little, while getting re-leveled one step up moves the base, the equity grant and every later raise at once. If you hold a software engineer offer, spend your first email on level, your second on equity, and only then on base and sign-on.
That ordering is the opposite of what most engineers do. They compare the base number to a salary site, ask for a bit more, and accept when the recruiter finds 5,000 dollars. The level was never discussed because it arrived inside the offer letter as a fact. It is not a fact. It is the output of an interview debrief, and debriefs can be reopened with evidence.
Why does level matter more than base for a software engineer?
Because the equity grant, the bonus target and the refresh eligibility are all attached to the level, not to your base. Here is an illustrative comparison, not a real company, showing the same engineer offered one level down and then re-leveled up. Every number is hypothetical and the structure is typical of large tech companies.
| Line | Offer at the lower level | After re-leveling one step up | Offer at the lower level plus a 10,000 base bump |
|---|---|---|---|
| Base salary | 165,000 | 195,000 | 175,000 |
| Equity grant over 4 years | 200,000 | 400,000 | 200,000 |
| Sign-on bonus | 20,000 | 0 | 20,000 |
| Year one total | 235,000 | 295,000 | 245,000 |
| Four year total | 880,000 | 1,180,000 | 920,000 |
The base bump is worth 40,000 dollars over four years. The level change is worth 300,000. Even if the higher level also removes the sign-on bonus, the engineer is far ahead. This is also why a recruiter will happily raise the base and rarely volunteer a level conversation: the base fits inside the existing band, and a level change needs a hiring committee.
How do you ask to be re-leveled?
You ask the recruiter what level the offer is at, which band that maps to, and what would be needed to be considered for the next level. Most recruiters answer the first question directly. If the answer is a level below what your scope suggests, make the case with evidence, not with a feeling.
Useful evidence is specific. Teams you led or technically owned, systems you designed and operated in production, the size of the user base or the dollar impact, the years of experience in the stack, and any competing offer at the higher level. Offers from comparable companies matter most because they show the market already prices you at that level. If you hold none, say plainly what you have done at your current level, and ask whether the interview loop assessed it.
- Ask for the level and the band in writing, in a friendly question.
- Say which two or three things in your background support the next level.
- Ask whether the hiring committee can review the level before you decide.
- Offer a deadline you both can meet, usually three to five business days.
Sometimes the answer is no, because the interview scores landed at the lower level. That is useful information. Then the conversation moves to the top of the band for the level you were given, an equity grant at the high end, and an agreed review date so the promotion clock starts sooner. Ask for the review date in writing. A verbal promise to look at it in a year is worth little.
What else can a software engineer negotiate?
After level, the order of value usually runs equity, sign-on, base, and then terms. Equity is the largest lever at public companies, where the grant is denominated in dollars and converted to shares at a fixed price or a short average. At a private company, the number of shares is meaningless without the strike price, the latest valuation and the exercise window, so ask for all three. Our guide to negotiating equity and RSU grants covers the vesting schedule questions, including front-loaded vesting and refresh policy, and the startup salary negotiation guide covers option terms.
A sign-on bonus is the easiest ask because it is one time and often comes from a separate budget. Its purpose is to cover what you leave behind, so name the figure: the unvested equity you forfeit, a bonus you will miss by leaving before payout, or relocation. Read the repayment clause before you accept it. Most sign-on bonuses are repaid in full or pro rata if you leave in the first twelve months, and our sign-on bonus repayment calculator shows what leaving early would cost.
Terms matter too. Remote or hybrid status, start date, team assignment, and a written review cycle are all cheap for a company and valuable for you. Team assignment is underrated: the same level on a core team and on a maintenance team has very different promotion odds, so ask which team the offer is for before you sign.
How much should you counter on a software engineer offer?
Counter inside the band for the level, anchored to a competing offer or posted range if you have one. Many states now require employers to post pay ranges, which gives you the band edges directly, as we explain in negotiating when the range is posted. A reasonable counter on total compensation is 10 to 20 percent above the first offer when the offer sits in the lower half of the band, and a smaller ask when it already sits near the top. Do not pick the number from a leaderboard alone. Self-reported data skews high and hides level differences.
Two traps are worth naming. The first is giving a number first when the recruiter asks for your expectations. Say you want to understand the level and band before naming a figure, then state your range for total compensation, not base alone. The second is asking for everything at once. One email with a prioritized ask, level first, then equity, then sign-on, is received better than a list of eight changes. For a tone that works, see our note on how to negotiate salary with a recruiter.
What does a software engineer negotiation email look like?
Thank you for the offer. I am excited about the team and the work, and I want to make this work. Before I decide, I would like to understand how the level was determined. Based on my experience leading [system or team] and [impact], I believe my scope matches the next level, and I have a competing offer at that level from [type of company]. Could the hiring committee review the level? If it stays as offered, I would like to discuss an equity grant of [figure] and a sign-on bonus of [figure] to reflect what I am leaving behind. I can respond by [date].
Notice what it does not do. It does not threaten, it does not reveal the other company's name, and it names one decision for the other side to make. Companies respond to a clear, polite request that they can route internally.
Where does Counteroffer fit?
Counteroffer reads your offer, benchmarks the base and equity for your level and location, flags where the level looks low for your background, and drafts the email, so you do not assemble a negotiation from five browser tabs and a salary leaderboard. If you are weighing two offers, the job offer comparison calculator lays out the four year totals side by side, and the salary negotiation coach walks you through each reply as the recruiter answers. This is career coaching, not legal or tax advice. Check any equity tax questions with a tax professional, and see the IRS guidance on stock options.
Build your counteroffer with Counteroffer.
Paste your offer or current pay and get a market-rate band, the number to counter with, talking points, and an email template, in minutes.
Keep reading