Treat compensation as a system, not a number
Tech compensation is not one number. It can include base salary, bonus, equity, pension, sign-on payment, relocation, contractor day rate, private health cover, remote-work costs, holiday, notice period and redundancy protections. Negotiation gets messy when candidates compare only the headline salary, because the headline is the one number companies are most willing to hold firm on and the one candidates are most likely to over-weight.
A useful way to think about an offer is as a portfolio with different risk profiles. Base salary is the cash you can rely on every month. Bonus is conditional cash that depends on company and personal performance. Equity is a bet on a future outcome you do not control. Benefits are a floor that protects you when something goes wrong. When you negotiate, you are not just asking for more money, you are choosing how much of your package sits in each of those buckets and how much risk you are comfortable carrying.
This guide is not financial advice and does not tell you what number to ask for. Career and salary content affects income, so it should be framed carefully. The practical goal is to help you understand the offer, collect evidence and negotiate professionally without leaning on the fake scripts and bluffing tactics that circulate online.
A common myth is that negotiation is mostly about confidence and clever phrasing. In practice the candidates who do well are the ones who did the boring work first: they understood the level, gathered comparable data, and knew what they would accept before the call began.
The 2026 context matters. Pay transparency rules have changed candidate expectations. New York and New York City require salary ranges for covered postings. The EU Pay Transparency Directive pushes pre-interview salary information by June 2026. The UK has moved more slowly, with government guidance focused on increasing transparency rather than a blanket range requirement. Primary sources: New York State pay transparency, NYC salary transparency, EU pay transparency, and the UK government's pay transparency publication. The practical effect is that more ranges are visible up front, which shifts negotiation away from extracting a hidden number and towards placing yourself correctly within a known band.
Build a compensation inventory
Before negotiating, write down every part of the offer. The act of writing it down is what surfaces the gaps, because most weak negotiations fail not on the number but on a component the candidate never asked about.
| Component | What to check |
|---|---|
| Base salary | Currency, review cycle, probation impact |
| Bonus | Target, historical payout, eligibility date |
| Equity | Grant size, vesting schedule, strike price if options, refresh policy |
| Pension | Employer contribution and matching rules |
| Sign-on | Repayment clawback and tax timing |
| Remote costs | Equipment, office stipend, travel expectations |
| Leave | Holiday, parental leave, sick pay |
| Risk | Funding stage, notice period, redundancy terms |
For private-company equity, avoid treating paper value as cash. Ask how the company explains valuation, exercise cost, tax treatment and liquidity. A grant described as worth a large sum at the last funding round can be worth far less, or nothing, if the company does not reach a liquidity event or raises again at a lower valuation. For public-company RSUs, check the vesting schedule and stock volatility, and be clear on whether the value quoted is the grant value at offer time or a projection. For startups, the upside can be meaningful, but the risk is different in kind from a higher base salary, and the two should not be added together as if they were equivalent.
A worked example shows why the inventory matters. Two offers can look identical at the top line yet behave very differently:
| Offer A | Offer B | |
|---|---|---|
| Base | 85,000 | 75,000 |
| Bonus target | 5% | 15% |
| Equity (annual value) | 5,000 (public RSUs) | 20,000 (private options) |
| Pension match | 3% | 8% |
| Notice period | 1 month | 3 months |
On paper Offer B has the larger total. But Offer B's bonus is conditional, its equity is illiquid and may never convert to cash, and its longer notice period cuts both ways. Offer A's lower total is almost entirely reliable cash plus liquid stock. Which is better depends on your situation, but you cannot make that call from the headline alone.
Useful data sources include Levels.fyi's annual report, Glassdoor salary pages, public job adverts, recruiter ranges and official labour statistics where relevant. For US occupational data, the BLS Occupational Employment and Wage Statistics is a primary source. For UK context, the ONS labour market pages can help with macro trends, though they are not a tech-company compensation database. Treat every source as one input. The most accurate figure for your specific situation usually comes from triangulating several sources rather than trusting any single one.
Ask for range early, but do it cleanly
The best time to discuss compensation is before a long interview loop. You are not demanding an offer. You are checking whether the process is worth both sides' time. A four-stage loop can absorb a working week of preparation and interviews, and there is no reason to spend that if the band is below your floor.
A clean question:
Could you share the budgeted compensation range for this role, including base salary and any bonus or equity components? I want to make sure we are aligned before going deeper in the process.
If the recruiter asks for your expectation first, you can still anchor in evidence rather than naming a single number you might regret:
I am still calibrating against the scope and level. Based on the role description and market data I have seen for similar roles, I would expect the package to be within the range budgeted for a mid-level backend engineer. Could you share the company's range so I can confirm alignment?
Here is what good and weak look like side by side.
| Weak | Why it hurts you | Better |
|---|---|---|
| "I need at least 95k or it is not worth my time." | Anchors low if their band is higher, reads as a threat | "I want to make sure we are aligned on level and range before the loop." |
| "I am flexible, whatever is fair." | Signals you have not done the work, invites a lowball | "I am calibrating against scope. Could you share the band?" |
| "Another company offered me more." (untrue) | Easily called, destroys trust if checked | "I am weighing a couple of conversations and want to compare fairly." |
Do not invent competing offers. Do not claim "market rate" without knowing which market. London fintech, fully remote US startup, regional UK SaaS and public-sector contractor roles do not price the same way, and a recruiter who covers one of those markets will spot a generic claim instantly. If you do have a competing offer, you can reference it honestly without disclosing the exact number unless it helps you.
Negotiate on scope and evidence
Strong negotiation is usually about fit between level, scope and compensation. You are arguing that the work described justifies a particular point in the band, and you are bringing evidence rather than feelings. Your evidence can include:
- Comparable roles with published ranges.
- Recruiter-provided ranges.
- Offer components from similar companies.
- Your level evidence: ownership, impact, domain match, leadership.
- Scarcity: specialist skills, availability, location or security clearance.
A practical structure:
- Thank them and confirm interest. People negotiate more generously with candidates who clearly want the role.
- State the specific gap. Vague dissatisfaction is hard to act on.
- Tie the ask to scope or evidence. This gives the manager something to repeat to their own approver.
- Ask whether there is flexibility in a component, rather than issuing a demand.
Example:
I am excited about the role and the team. The main gap is the base salary relative to the scope we discussed, especially owning the payments migration and on-call rotation. Is there flexibility to improve the base salary, or alternatively to adjust the sign-on or review timeline?
This avoids fake certainty. It gives the employer options. Candidates report better conversations when they negotiate the package rather than issuing ultimatums, partly because the recruiter is often on your side internally and needs ammunition to take upstairs.
A short, realistic exchange shows how this plays out:
Recruiter: We can come in at 80,000 base, that is where the role is budgeted.
Candidate: Thank you, I am keen on the team. Given the scope includes owning the payments migration, which sits above what I would expect at the bottom of the band, is there room to move the base toward the upper half?
Recruiter: The base is fairly fixed, but I might have flexibility on the sign-on.
Candidate: That helps. Could we do a sign-on that offsets the gap this year, and agree to revisit the base at the six-month review against the migration milestones?
Notice the candidate never threatened to walk and never invented a competing offer. They moved the conversation to components the recruiter could actually adjust.
Understand wide bands and level mismatch
A wide salary band is not always bad faith. It can mean the company hires multiple levels under one title, or that location and equity mix vary. It can also be a warning sign that the company has not defined the role, or that they intend to slot you in low and let the band imply more.
Ask:
- What level is this role mapped to internally?
- Where would this offer sit within the band and why?
- What scope would justify the top of the band?
- How are salary reviews handled after joining?
- Are remote employees paid by location or one global band?
Levels.fyi is useful for company and level mapping, but it is not a substitute for understanding the specific offer. Glassdoor can add signal, but self-reported data can be stale or mixed across titles. Treat all databases as inputs, not verdicts. The single most useful question is the level question, because once you know the internal level you can compare against that level's band rather than the inflated title.
Match the ask to what the employer can actually move
The biggest waste in a negotiation is spending your one clean ask on a lever the person across the table cannot pull. Flexibility is structural. It lives in different components depending on who is hiring, so read the employer type before you decide what to push on.
| Employer type | Where flexibility usually sits | Where you will hit a wall |
|---|---|---|
| Large leveled tech company | Sign-on, equity refresh, level placement | Base inside a level is banded tight by policy |
| Growth-stage startup | Equity size, base, title, start date | Cash is scarce, so equity is the lever they reach for first |
| Agency, contract or day-rate | The rate itself, contract length, notice terms | No pension, holiday or sick pay sits in the package to trade |
| Public sector or large regulated employer | Step within a published scale, start date | Base is often fixed to a national or graded pay scale |
At a company that levels rigidly, pushing base often gets a polite no while a sign-on or an equity refresh has real room, so aim the ask there. At an early-stage startup the base may be genuinely capped by runway, and the honest trade is equity for cash, which only makes sense if you can actually price the equity using the inventory above. A day-rate contract removes most of the safety net, so the rate has to absorb the missing pension, holiday, sick pay and the risk of gaps between contracts. That is a unit mismatch, not a discount: a contractor rate and an employee salary are different currencies, and the difference is legal as well as financial. Whether you are an employee or a contractor changes your rights and who pays your taxes. In the UK the gov.uk employment status rules separate worker, employee and self-employed, and in the US the IRS common-law test decides employee versus independent contractor, which sets who withholds tax and who funds benefits.
If you are stepping into management, the negotiable surface widens rather than narrows. Team size, scope, budget authority and the review timeline all come onto the table, and a larger share of the package shifts into bonus and long-term incentive. That is a scope conversation, not a base-only one, and it rewards candidates who can name the outcomes they intend to own in the first year.
Where negotiations quietly go wrong
- Negotiating only base salary and ignoring sign-on, equity and review timing, which are often where the flexibility actually is.
- Naming a single expectation number too early, anchoring yourself below the band.
- Treating private-company equity as cash and adding it to base as if the two carry the same certainty.
- Inventing a competing offer that a recruiter can puncture with one question.
- Accepting on the spot out of relief, before reading the full written offer.
- Forgetting to get the agreed changes in writing before resigning from a current role.
- Comparing a contractor rate to a salary without adjusting for benefits, pension, holiday and downtime.
Know your walk-away conditions
Negotiation advice often focuses on tactics. The more important question is what you value. A higher package may be a poor trade if the role has unsustainable hours, unclear remote terms or weak sponsorship for growth. A lower package may be rational if it gives you a strong role transition, visa stability, excellent mentorship or a rare domain entry point.
Write down your walk-away conditions before the offer call, while you can still think clearly. Examples:
- Base salary below your minimum budget.
- Required office attendance that breaks your commute.
- Equity-heavy package with low cash and high uncertainty.
- No clarity on level, manager or team.
- Contractor setup when you need employee protections.
Defining these in advance protects you from the pull of the moment, when an enthusiastic call and a deadline make it tempting to accept terms you would reject on a calm Tuesday. This is especially important for remote and cross-border roles, where tax, employment rights and benefits can change the real value of the package and a number that looks generous in one country can be ordinary once local costs are applied.
Frequently asked questions
Should I always negotiate? Usually it is reasonable to ask once, politely, with evidence. The risk of a well-framed, single ask being rescinded is low at most established companies. If the offer is already strong and you are happy, you are not obliged to push.
What if they say the offer is final? Take it at face value but ask about adjacent components, such as a review timeline, sign-on or start date. A fixed base does not always mean a fixed package.
Can I negotiate after I have verbally accepted? It is much harder and can read as bad faith. Settle the important terms before you accept anything, even verbally.
How do I handle an exploding offer with a short deadline? Ask for a reasonable extension in writing. A company unwilling to give you a few days to make a major decision is telling you something about how it operates.
Should I share my current salary? In many places you are not required to, and anchoring on a past salary can hold you below the band. Redirect to the role's range and your expectations for the scope.
Where to take this next
Negotiation is the last link in a longer chain, and it goes best when the earlier steps are already done: