Updated recently
Last updated:
Quick Answer: How to ask for salary raise tech: To ask for a salary raise in tech, wait for a trigger rather than a date – taking on materially more scope, a promotion, a market adjustment or a certification you started using – then bring a written case with your outcomes, your market band and a specific number. Timing and specificity decide the outcome far more often than confidence does.
The Salary Raise Ask: What Determines the Outcome
Asking for a raise is a business conversation with a specific structure, and most people run it as an emotional one. The candidates who succeed have three things: a trigger that makes the timing defensible, an evidence base that makes the number arguable, and a specific ask that can be accepted or countered.
The other thing that separates the outcomes is that a raise is not a favour. Companies have bands, and the request that works is one that positions you inside the band with evidence, rather than one that asks to be given something outside it. That reframing sounds cosmetic and is not – it changes the meeting from a negotiation about your worth to a correction about your placement.
| Element | What strong looks like | What weak looks like | Why it matters |
|---|---|---|---|
| Trigger | New scope, a promotion, a market move | It has been a year | A defensible trigger is hard to refuse |
| Evidence | Outcomes with numbers, scope owned | A list of duties | Evidence ends the cost-of-living argument |
| Market data | The band for the role at that company | A national average | A band is a fact; an average is an opinion |
| The ask | One specific number | As much as possible | A range invites a low anchor |
| Delivery | Short, calm, then stop talking | Justifies for ten minutes | The first two minutes are heard; the rest is not |
| Fallbacks | Title, review date, equity, remote days | Nothing | Levers beyond cash are often cheaper to grant |
| Timing | Soon after a visible win | Just before a review deadline | Deadlines are when budget is fixed |
That last row is the one most people get backwards. Asking just before a review deadline means the budget is already committed, and asking just after it means the next cycle is nine months away. The window is shortly after a result lands and before the next cycle closes.
How to Ask for Salary Raise Tech in 2026: The Sequence That Works
Start with the trigger, and be honest about which one you have. Taking on work nobody else wants, owning a system that used to be a black box, becoming the person who answers a particular class of question, or passing a certification you now use in the job – these are all real and all defensible. ‘I have been here a year’ is not a trigger, because the year passed for everyone in the same band and the company planned for it.
Then build the evidence in writing, before the meeting. Three or four lines: what you own, what changed because of it, and what it is worth in money or time. A candidate who says ‘I reduced checkout latency by 40 percent, which we estimate at $1.2 million a year in recovered revenue, and I now own the service without an on-call rotation for other teams’ has ended the discussion before it started. A candidate who describes being ‘responsible for performance work’ has not.
Bring the band, not the average. Three data points – the range for your role at this company if you can find it, the range for the same role at comparable companies in the same city, and what the role pays in the next level up – will carry the conversation. An average is dismissible in one sentence; a range with three sources is not.
Make one specific ask, state it once, and then stop talking. ‘I would like to move my base to $X’ is a proposal. ‘I would like to discuss my compensation, I think I am underpaid, and I would like to be at $X’ is a plea with a number attached, and the second version sounds weaker even when the number is right.
And prepare the outcome. The realistic responses are yes, no, and ‘not now’, and the third is the most common. A good ‘not now’ response includes a specific date and a specific condition, and a candidate who asked for both will usually get them.
# Track the evidence before you need it - the promotion case is a file,
# not something you assemble in the week before the cycle
cat > compensation-records.csv <<'CSV'
date,role,scope,outcome,metric,visible_to
2026-03-14,Payments Migration,Led 3 teams,Cut checkout latency 40 percent,revenue protected,Eng wide
2026-06-02,Payments Migration,Own runbook,Onboarded 2 engineers,3 months faster ramp,Team
2026-09-20,Observability,Defined 4 SLOs,Caught 3 incidents before customers,reduced pager noise,Partner team
2026-11-08,Payments Migration,Lead design review,Approved by architecture board,design adopted,Company
CSV
# What the band actually says - replace with your employer's real figures
cat > band.csv <<'CSV'
level,min,max,currency
L4,118000,142000,USD
L5,142000,175000,USD
L6,175000,215000,USD
CSV
# Where you sit, and what the gap is worth over a year
awk -F, 'NR==1 {for (i=1;i<=NF;i++) h[$i]=i; next}
{if (\$1=="L4") {mid=(\$2+\$3)/2; print "L4 midpoint:", mid}}' band.csv
# The ask, written down before the meeting so it is one sentence
cat > ask.txt <<'TXT'
Ask: base 142,000 (bottom of the L5 band, which is where my scope now sits)
Reason: 3 cross-team migrations led, 2 owned systems, 4 SLOs defined
Evidence: compensation-records.csv, and the design review approved in November
Fallback: review date 2027-04-01, or title change to L5
TXTWhat to Do When the Answer Is No
Find out which no it is. ‘No’ because the band is fixed, ‘no’ because the budget is committed this cycle, and ‘no’ because the manager does not think your contribution justifies it are three different situations with three different responses, and treating them identically is how people ask repeatedly and get nothing.
If it is the band, ask what the band is and where you sit in it, and what would move you within it. Some companies have a defined progression framework with named steps, and if yours does, the conversation becomes ‘which step am I at’ rather than ‘please pay me more’, which is a much better conversation to be having.
If it is the budget cycle, ask when the next cycle runs and what has to be true to be in it, and get both in writing. A specific date and a specific condition is a genuine commitment, and it is worth more than a vague promise of ‘something next year’.
If it is the manager’s assessment, that is the one worth taking seriously, because it is about the evidence rather than the budget. Ask what they would want to see, get it as a list, and then go and build it. Some managers genuinely cannot advocate for someone whose impact they cannot describe, and a specific list of things is a gift – it is the clearest possible promotion plan.
How to Avoid Damaging the Relationship
Do not overstate. Claiming scope you do not have, or an outcome the team had nothing to do with, is the fastest way to lose credibility, and the manager will know. The claim does not need to be dramatic; it needs to be true and quantified.
Do not make it personal. Avoid ‘I need this because of my rent’ and ‘my colleague was promised more’. Both invite a discussion you cannot win, and the second is a direct invitation to be compared to a colleague, which you will lose if you do not know their number.
Do not threaten, and do not imply you have an offer unless you have one. An ultimatum with nothing behind it ends the relationship, and a bluff that gets exposed costs you the role and the credibility. If you do have a competing offer, that is a legitimate thing to mention plainly – but as information, not as a threat.
And do not ask more than once in a way that reads as repeated failure. If the answer was a firm no, the next appropriate moment is after a new result, not three months later with the same case. Repeated asking with unchanged evidence reads as entitlement and it changes how the manager thinks about you.
What the Research Says About Pay Equity in Raises
The research on internal pay equity is consistent on one point that is useful for candidates: employees who ask tend to end up closer to the correct placement in the band, and employees who never ask tend to drift below it, even when the initial placement was fair. New-hire offers are frequently set optimistically to close a candidate, and the band then quietly moves above where that offer sits.
That is a normal feature of the system rather than an injustice, and it means the raise conversation is a correction of a drift that affects everyone who does not raise it. The practical implication is that a raise request is not a favour being requested from a generous manager – it is information being supplied about a gap that the organisation’s own data contains.
The second finding is that requests which include specific evidence are accepted at a materially higher rate, and that the evidence which works best is quantitative and about outcomes rather than effort. A candidate who says ‘I did more than last year’ is describing effort, which the organisation already assumes. A candidate who says ‘the migration I led avoided a second outage and removed a manual step that three people were doing five hours a week’ is describing a change, and changes are what the band is being corrected against.
How to Handle the Career Conversation That Is Not a Raise
Some of the most valuable conversations in a career are not about money at all, and they are the ones candidates skip. The ‘what should I be doing next’ conversation with a manager is the most useful meeting available to a mid-level engineer, and it is worth requesting explicitly – and worth having before there is a specific ask attached, so that the ask is not the thing being negotiated.
The second is the scope conversation. Most promotions come from a change in scope that happened informally and was never made explicit. A candidate who notices that they have been running a quarterly planning process, or that two teams now depend on something they built, and says so plainly – and asks whether that is recognised as a level change – is doing something most people never do.
And the third is the market conversation, which people are strangely reluctant to have with their own managers because it feels like a threat. Many managers find out months after the fact that a candidate was interviewing elsewhere, and the surprise damages the relationship. A short, honest note – the market is moving, here is what I would need to stay, here is my ask – is the version that tends to work.
A Candidate Who Asked at the Right Time and Got More Than Expected
A mid-level engineer brought a raise request eight weeks after a migration she had led. Her written one-pager described the two-week outage the migration prevented, the three teams that had stopped carrying a manual process, and the fact that she now ran the migration runbook for new engineers.
She brought the band for her level at the company, which she had found in a levels-and-bands page on the company wiki, and observed that she was below the bottom of it. Her ask was a specific number – the bottom of the band – rather than a number she had chosen herself.
The manager came back with the bottom of the band, which was $7,000 more than she had asked for, because the framing had made it a correction rather than a favour. The manager also volunteered that the levels framework had a second step, which the candidate could work toward with two more quarters of evidence. That conversation had not been on the agenda, and it would not have happened if the request had been framed as a request.
Why This Matters Outside the United States
Salary review conventions are US-specific in timing and process – a useful thing for international candidates to understand before they ask.
Raise and promotion practice differs substantially by country, and in the United States the at-will employment context and the prevalence of published bands make the process more structured than in many markets. The underlying technique transfers – trigger, evidence, band, specific ask, and a written follow-up – but the norms around asking, and what a company will consider legitimate grounds, are specific to the local employment culture.
How to Read These Numbers
The timing and evidence advice here reflects how compensation review processes are generally run in US technology companies, and the specific cycle varies considerably by employer size and structure. In companies with a defined review cycle, the effective deadline is well before the submission date.
The market data references are typical US technology bands and vary by city, company size and level. A specific band for a specific employer is always the better reference than a published average, and it is worth asking for during the process.
Key Terms Used Above
| Term | What it means in practice |
|---|---|
| Comp band | The published range for a role, level and location. The space a raise request moves within. |
| Level | The internal grade that determines band. A promotion is a level change, a raise is a move within one. |
| Review cycle | The periodic process that sets pay changes. Its calendar determines when to ask. |
| Total compensation | Base plus bonus plus equity. The figure that matters when the band is not the whole story. |
| Promotion criteria | The written rubric for the next level. The most useful document to read before a cycle. |
| Counter offer | An employer’s attempt to retain a candidate who has another offer. Rarely a good outcome. |
Ask what the band is and where you sit in it. A request framed as a correction to a placement is much easier to approve than one framed as a favour.
Related Reading
If you want the wider context, start with our guide to negotiating a tech salary, then the full guide, then the full guide. Each of these covers a different part of the same decision.
Training Resources
For a structured path rather than scattered free material, the SkilBrill training programme covers the practical side of this topic with the same framing employers use. For a broader foundation, the related SkilBrill course covers the surrounding concepts so you are not learning this topic in isolation.
FAQ
When is the best time to ask for a raise in tech?
At the start of a review cycle or immediately after taking on materially more responsibility. Asking right after a strong review, a promotion, or a completed high-visibility project all work better than asking annually on a fixed date.
What evidence should I bring to a salary raise request?
Market data for your role and level, a record of outcomes you delivered that mattered to the business, and a specific ask. Scope of responsibility and a competing offer are the two strongest levers.
What should I say when my manager says there is no budget?
Ask what would need to change for it to be possible – which responsibility, which result, which quarter – and ask to be measured against it. That turns a refusal into a deadline.
How much of a raise should I ask for?
For a promotion, commonly 8%-15%; for a scope increase without a title change, 5%-10%. Anchor slightly above the target so the discussion lands where you wanted it.
