Skip to main content

Negotiating Tech Job Offers: Compensation, Equity, and Remote Work

· 7 min read
Negotiating Tech Job Offers: Compensation, Equity, and Remote Work

A strong tech offer is rarely just a salary decision. It is a bundle of cash, equity, work arrangement, level, and expectations - and one weak piece can quietly erase the value of a strong-looking number. Good negotiation starts when you stop asking "Can I get more?" and start asking "What exactly am I being asked to trade off?"

That matters because the market is competitive, but it is not soft enough to make negotiation irrational. The U.S. Bureau of Labor Statistics puts median software developer pay at $133,080 in 2024 and still projects about 129,200 openings per year on average through 2034.[1]

Levels.fyi's 2025 pay report found that reported U.S. software engineer compensation in its dataset rose 1.8% year over year overall, while staff-level compensation in that same dataset rose 7.52%.[2] At the same time, remote work has settled into a mixed model rather than a universal perk: Pew found that among workers with jobs that can be done remotely, 35% work from home all the time and 41% work hybrid.[3]

That is why negotiation in 2026 is usually about the full package, not a single number.

Start with the package, not the base salary

If you only negotiate salary, you can miss the parts that matter more six months later: level, bonus target, sign-on, refresh cadence, on-call expectations, promotion scope, and location rules. Harvard Business Review's negotiation guidance makes the broader point well: understand the whole offer before you start trading against any single part.[4]

A practical first pass looks like this:

  • base salary and bonus target
  • sign-on, if any, and clawback terms
  • equity type and vesting schedule
  • title, level, and reporting line
  • remote, hybrid, relocation, and office expectations

That list turns negotiation from a generic ask into a set of specific variables. Sometimes the company cannot move much on base salary, but it can shift sign-on, level, start date, or work arrangement. Sometimes the number is fine and the real risk is that the role is scoped below your experience level.

Diagram showing one offer package broken into salary, bonus, equity, level, and work arrangement The useful comparison is the package, not the headline number.

Treat equity like a contract term, not a lottery ticket

A lot of candidates negotiate equity badly because they negotiate the quantity before they understand the instrument. Public-company RSUs, private-company stock options, and startup equity grants do not behave the same way. The IRS is explicit that stock options can create different tax consequences depending on whether they are incentive stock options or nonstatutory options, and when you exercise or sell can matter materially.[5]

Before you negotiate equity, I would want clear answers to four questions: what kind of grant is this, what is the vesting schedule, what assumptions is the company using when it talks about today's value, and what usually happens after year four. That last question matters more than candidates expect. An initial grant can look very different once you understand the company's normal refresh pattern and how level changes affect later grants.

Levels.fyi's 2025 report also points to another reason to be precise: compensation moved differently by level, with staff engineers seeing much stronger growth than the market average.[2] If a company says the equity band is fixed, level may be the real lever. Negotiating the package may mean asking whether the offer accurately reflects scope, not just asking for more shares.

Diagram comparing RSUs, stock options, and the questions candidates should ask before comparing them Equity only becomes comparable when you know the instrument, vesting, and assumptions behind it.

Remote-work terms belong in writing

Remote work still matters because it changes commute cost, schedule flexibility, and how often you are expected to be physically present with the team. Pew's data shows that hybrid is now the dominant steady-state outcome for many teleworkable roles, not a temporary exception.[3] That means vague language like "mostly remote" or "we're flexible" is not enough.

What you want is operational clarity: how many in-office days are expected, whether that can change by team or manager, whether relocation is on the table later, how travel works, and whether compensation is tied to office geography. A lot of bad surprises come from candidates negotiating pay while leaving work arrangement informal.

If remote flexibility is one of your top priorities, say so directly and convert it into a concrete ask. "I can move quickly if we can confirm two in-office days max and no relocation requirement for this role" is easier to evaluate than "Remote matters to me." Specific terms are easier for a hiring manager to approve and much harder to reinterpret later.

Diagram showing a vague remote promise turning into written terms: in-office days, relocation, travel, timezone, and compensation policy Remote-work terms should be as concrete as compensation terms.

A clean way to respond

The best negotiation messages are short, calm, and anchored in evidence. HBR's advice is useful here too: show enthusiasm, ask informed questions, and make it easy for the other side to solve the problem with you instead of against you.[4]

A good structure is simple: say you are excited, name the two or three terms you want to discuss, explain the reasoning, and stop. For example: based on the level, scope, and competing market data, you would like to revisit base and equity; if those are fixed, you would like to discuss sign-on or remote terms. That gives the recruiter something concrete to take back internally without turning the exchange into a speech.

If you are running several role-specific applications at once, keep your materials organized so you do not mix up levels, packages, and follow-up asks. A tool like CoreCV can help with the resume side by keeping role-specific resume versions straight, while you track application details separately.

The point of negotiation is not to win an argument. It is to make sure the deal matches the job you are actually taking. When salary, equity, and remote terms all make sense together, the offer usually feels clearer - and a lot safer to accept.

Sources

1. U.S. Bureau of Labor Statistics. "Software Developers, Quality Assurance Analysts, and Testers." https://www.bls.gov/ooh/computer-and-information-technology/software-developers.htm

2. Levels.fyi. "End of Year Pay Report 2025." https://www.levels.fyi/2025/

3. Pew Research Center. "35% of workers who can work from home now do this all the time in U.S." https://www.pewresearch.org/short-reads/2023/03/30/about-a-third-of-us-workers-who-can-work-from-home-do-so-all-the-time/

4. Harvard Business Review. "15 Rules for Negotiating a Job Offer." https://hbr.org/2014/04/15-rules-for-negotiating-a-job-offer

5. Internal Revenue Service. "Topic no. 427, Stock options." https://www.irs.gov/taxtopics/tc427

Share this post

Ready to Build Your Perfect Resume?

CoreCV.ai is the JSON-based resume builder designed specifically for developers and technical professionals. Write your resume once in structured JSON, then instantly render it across multiple professional templates. With AI-powered tailoring, you can customize your resume for any role in seconds.

Get Started FreeNo credit card required • 3 free templates

✨ Write once, render anywhere • AI-powered tailoring • 9 professional templates • ATS-optimized • Developer-friendly