Key facts at a glance
Senior SWE band (Ireland)
€85–115k
4–8 yrs, this site's own data
Senior SWE band (UK)
£76–102k
4–8 yrs, this site's own data
Median vs 75th gap
~13%
Per our percentile methodology guide
The strongest number you can bring into a promotion conversation isn't “I think I deserve more,” it's a specific market band with a clear statement of where your impact places you inside it. Take a Senior Software Engineer in Ireland, whose market band on this site runs €85–115k (£76–102k in the UK) for 4 to 8 years' experience. If you're at the low end of that band with three years of Senior-level impact behind you, the honest ask is a move toward the median. If you can point to measurable impact above what's typical for the role, driving a project other teams now depend on, for instance, the honest ask is the 75th percentile, the top-quartile figure.
The rest of this guide gives you the framework to pick which one honestly applies to you, a script to bring the number into the room without it reading as a demand, and answers to the pushback HR and managers give most often.
For the employer-side methodology behind these percentile bands, see our pay-transparency benchmark guide.
Read the methodology guideWhy percentile data is your best negotiation leverage
Most promotion conversations fail not because the raise wasn't deserved, but because the ask was vague. “I've been working hard, I should get more” gives your manager nothing concrete to take to their own compensation committee. A percentile-anchored ask, by contrast, gives them a specific, defensible number: “the market band for my role and level is €85 to €115k, I'm currently at €89k, and given the scope I've taken on this year, I'm asking to move to €102k.” That's a number your manager can advocate for internally, because it's not just your opinion, it's a market reference point they can point to as well.
This matters more, not less, as pay transparency regulation spreads. Under the EU Pay Transparency Directive and similar UK disclosure trends, more employers are already building and internally publishing exactly this kind of banded data, which means the information asymmetry that used to favour employers in these conversations is narrowing. Bringing your own well-sourced band levels the conversation instead of leaving you negotiating against a number only the other side can see.
Finding your true market value: 50th vs 75th percentile strategy
Worked example using this site's own Senior Software Engineer band, 4 to 8 years' experience:
| Anchor | Ireland | UK | Use when |
|---|---|---|---|
| Band bottom | €85k | £76k | Newly promoted, still proving scope |
| Median (50th) | ~€100k | ~£89k | Solid, competent performance at level |
| 75th percentile | ~€108k | ~£96k | Impact above the typical level, scarce skills, or a competing offer |
| Band top | €115k | £102k | Reserved for exceptional, well-evidenced cases |
Illustrative interpolation within this site's own €85–115k / £76–102k Senior Software Engineer band. Real market percentile distributions aren't always evenly spread across a range; use this to understand the framework, and pull the live band for your own role and level before a real conversation.
The rule: the honest anchor for your ask should match the honest evidence you can produce. Asking for 75th-percentile pay with median-level evidence is the fastest way to lose credibility in the room, but leaving genuine top-quartile impact anchored at median leaves real money on the table.
The data-backed promotion proposal: script and template
Script template
Opening: “I'd like to talk through my compensation ahead of the review cycle. I've looked at the current market band for [role/level] in [country], which runs [band low] to [band high], and I'm currently at [your current pay].”
Evidence: “Over the last [period], I've [specific, measurable impact: led the migration that cut deploy time by X%, mentored two engineers now performing at Senior level, owned the redesign that other teams now depend on]. That's the kind of scope the market band associates with [median / top-quartile] pay for this level.”
The ask: “Based on that, I'd like to propose moving to [specific target figure], which reflects [median / 75th percentile] for my role and level. I wanted to bring a concrete number rather than leave it open-ended, so we have something specific to work with.”
Close: “I know this may need to go through a process on your end, what would be helpful from me to support that, and what's a reasonable timeline to revisit it?”
Bring the band and your evidence in writing beforehand if your company's process allows it, a one-page summary makes it far easier for your manager to advocate accurately on your behalf rather than paraphrasing your case from memory in a compensation meeting you're not in.
Countering common HR pushback
"We don't have budget this cycle."
Ask when the next review point is and what would change the answer, then get the target figure and timeline in writing so it isn't quietly dropped.
"Your title doesn't match that band yet."
Separate title from scope: point to the specific, evidenced work you're already doing at the higher level, and ask whether a title change or a scope-adjusted pay move is the faster path.
"That's above what we normally pay at your level."
Ask what data they're using to say that, and be ready to show your own source. If they have no counter-data, your band is now the only one in the room.
"Let's revisit this at your next review."
Agree, but pin down a specific date and what evidence would make the case stronger by then, so 'next review' has a concrete target rather than becoming indefinite.
"Everyone on the team is getting the same increase."
Acknowledge the constraint, then ask whether a one-off adjustment or a title change is possible outside the standard cycle, since your ask is about correcting a market gap, not requesting an above-average raise.
"We can't share our internal bands."
You don't need theirs if you bring your own, sourced, cited market data. Ask them to confirm or push back on your figure rather than asking them to disclose first.
Pull the live band for your own role before the conversation
Use the full Software Engineer career path as your worked example, or find your own role.
Market intelligence
Ireland's tech market is shifting fast in 2026
AI engineering, platform roles, and contractor demand are all moving. Our monthly Ireland briefing tracks what's actually hiring, at what rates, and where pay is going.
No spam. Unsubscribe any time. GDPR-compliant.
Frequently asked questions
What's the difference between median (50th percentile) and 75th percentile pay?
Median is the midpoint: half the market pays more, half pays less, for that role and level. The 75th percentile is the point where only a quarter of the market pays more, in effect, top-quartile pay for that level. Using this site's Senior Software Engineer band in Ireland (€85-115k) as an example, the median sits roughly in the middle of that range while the 75th percentile sits toward the top of it. The gap between the two is real money: choosing to anchor a negotiation on 75th percentile rather than median is choosing to argue for a materially higher number, and you need a case for why you deserve it.
When should I negotiate at the 50th percentile instead of the 75th?
Anchor at median when your case is 'I am doing this job competently and want fair market pay for my level,' which is the right ask if you're newly promoted, still building a track record at the new scope, or your company has genuinely tight banding. Anchor at the 75th percentile when your case is 'I am outperforming the typical person at this level,' which requires specific evidence: measurable impact above what the role typically requires, scarce skills, or a competing offer. Asking for 75th-percentile pay without 75th-percentile evidence is the single most common way a promotion negotiation stalls.
How is this different from the percentile methodology article already on this site?
Our pay-transparency percentile methodology guide explains the employer side: how HR and compensation teams build P25/median/P75/upper-quartile bands and communicate them under 2026's disclosure rules. This article is written for the other side of the table, you, the person asking for the raise, using the same underlying percentile concept as leverage in your own negotiation rather than as a compliance framework to build.
What if my employer says they don't have percentile data to negotiate against?
That claim is rarely fully true. Most companies that have done any compensation benchmarking at all, even informally, know roughly where they sit relative to market median. If they genuinely have no data, that's your opening to bring your own: a published salary band for your role and level (like the ones on this site), a competing offer, or public salary-transparency disclosures from comparable employers under the EU Pay Transparency Directive. The absence of employer data doesn't mean the absence of a real market rate, it means you need to supply the anchor yourself.
Does bringing percentile data risk making the conversation adversarial?
Framing matters more than the data itself. Presenting a number as 'you're underpaying me' invites defensiveness. Presenting it as 'here's the market band for my level and where my impact this year places me in it' is a collaborative framing that most managers can work with, especially since many managers are themselves arguing your case upward to their own compensation committee, and a clean, well-sourced number makes that easier for them to do, not harder.
How often should I revisit my market position using percentile data?
Annually at minimum, and immediately before any formal review or promotion conversation. Market bands shift meaningfully year over year, particularly in tech, and a number that was accurate 18 months ago may already be stale. Re-pull your role's current band, re-assess honestly whether your impact this cycle supports a median or top-quartile ask, and update your script before every real conversation rather than reusing last year's numbers.
The worked example uses this site's own Senior Software Engineer career-ladder band (Ireland and UK only). Median and 75th percentile figures within that band are illustrative interpolations for teaching the framework, not a live, sourced percentile distribution; pull your own role's current band before a real negotiation. This article is general guidance and does not constitute financial or legal advice.