Most professionals have no idea whether they're paid fairly. They have a vague sense — a colleague let slip their number at a Christmas party, or they saw a job listing that made them feel slightly nauseous — but they've never actually sat down and compared their salary to the market in a structured way. That's a problem, because the gap between what you're earning and what you should be earning doesn't close by itself. This guide walks you through how to benchmark your salary properly, where to find data you can actually trust, and what to do if the results aren't what you hoped.
What Salary Benchmarking Actually Means
Salary benchmarking is the process of comparing your current compensation to the market rate for your role, seniority level, and location. The operative word is market rate — not what your employer says is fair, not what your most vocal LinkedIn connection claims to earn, but what employers are actually paying for comparable talent in your geography and sector.
The goal is to establish your percentile. Are you in the bottom 25% of earners for your role? The top 10%? Squarely in the median? Each of those positions tells you something different about your negotiating position and your employer's attitude toward your pay. Someone sitting at the 30th percentile for a software engineer role in Amsterdam isn't just slightly underpaid — they're leaving meaningful money on the table every year, and every salary increase they receive is calculated on an already-suppressed baseline.
Benchmarking is not the same as comparing yourself to a single data point. One salary figure from one recruiter or one job ad tells you almost nothing. You need a distribution — a range that shows you the 25th, 50th, and 75th percentile for your specific role and location — and you need to understand where your skills and experience place you within that distribution.
Done properly, benchmarking gives you a factual foundation for any pay conversation. It removes the awkward subjectivity from salary negotiation and replaces it with data. Employers negotiate with data every day. You should too.
Where to Find Reliable Salary Data in Europe
The quality of salary data varies enormously, and using bad data is almost worse than using none — you can anchor a negotiation to a number that has no grounding in reality. Here's where the credible sources actually live.
Government statistical agencies are the most rigorous source. In the UK, the Office for National Statistics publishes the Annual Survey of Hours and Earnings (ASHE), which breaks down median pay by occupation at a granular level. In Germany, Destatis publishes earnings data by industry and qualification level. Eurostat aggregates data across EU member states, which is useful for cross-border comparisons. Spain's INE publishes the Encuesta de Estructura Salarial. These sources are methodologically sound, but they lag by 12–18 months and don't always slice data finely enough — you might get a median for "IT professionals" rather than "mid-level backend engineers."
Sector-specific sources fill in the gaps. For tech roles, Levels.fyi is the most granular public dataset available, with self-reported compensation broken down by company, level, and location. It's heavily skewed toward large tech companies and senior talent, so treat it as a ceiling rather than a midpoint for most professionals. In the US, the Bureau of Labor Statistics (BLS) Occupational Employment and Wage Statistics programme is the gold standard for American benchmarks, which matters if you're comparing against US-based multinationals operating in Europe.
Salary tools synthesise multiple data sources to give you a contextualised answer quickly. Our free salary checker uses data from BLS, ONS, Eurostat, Destatis, INE, Statistics Canada, and Levels.fyi to calculate your market percentile based on your actual role, location, and reported salary. If you want to understand how we calculate salaries, the methodology page walks through the weighting and sources in detail. The advantage of a tool over raw government data is that it saves you three hours of spreadsheet work and gives you an answer in the context that matters: your specific job title, your city, and where you sit in the distribution right now.
How to Break Down Your Benchmark by Seniority and Company Type
A single market rate figure for "product manager salaries" is nearly useless. The range within that title is enormous, and where you sit in it depends on two variables more than any other: your seniority level and the type of employer you work for.
By seniority level, the differences are substantial. Consider a product manager in Berlin. Based on current market data, a junior product manager (zero to two years of experience, typically IC2 or equivalent) earns in the range of €42,000–€55,000 gross annually. A mid-level product manager (three to six years, running a product area independently) earns €60,000–€80,000. A senior product manager (six-plus years, owning a product line with measurable business impact) sits in the €85,000–€110,000 range. The product manager salary Berlin page breaks this down by percentile if you want the full distribution. What this means in practice: if you're calling yourself a "senior PM" but earning €65,000, either your title is inflated or your compensation hasn't kept pace with your progression.
By company type, the divergence is even more pronounced. A software engineer at a Series B startup in London will typically earn less total cash than the same engineer at a FAANG or large-cap tech firm, but may receive equity that changes the picture significantly. A software engineer at a professional services firm or a legacy enterprise organisation often earns more cash than a startup peer but with minimal upside. For reference, a mid-level software engineer in London at a large tech company might earn £85,000–£105,000, while the same profile at a scale-up sits closer to £65,000–£80,000, and at a traditional enterprise or consultancy, £60,000–£75,000 is common — check the full breakdown on the software engineer salary London page for percentile-level detail.
By industry vertical, even within the same city, you'll see significant variation. In Paris, a data analyst working in financial services typically earns 15–25% more than an equivalent analyst in media or non-profit. In Stockholm, software engineers in fintech and gaming outpay those in traditional retail and logistics. These differences compound over a career. Getting your market category right before you benchmark is not pedantry — it's the difference between an accurate result and one that sends you into a negotiation with the wrong number.
Signs You're Overdue for a Benchmark Check
If you haven't benchmarked your salary in the last 12 months, you're likely flying blind. A few specific situations make a benchmark check urgent rather than just good practice.
You've been promoted without a meaningful pay increase. This is more common than it should be, particularly in organisations that use promotion as a substitute for compensation adjustment. Getting a new title without a corresponding pay uplift is a warning sign worth investigating. The signs you are underpaid post covers this and several other patterns in detail.
You've been at the same company for more than two years without switching. External hires consistently command higher salaries than internal promotions in most industries. If you've stayed loyal, the market may have moved on without you. Studies consistently show that job switchers earn 10–20% more on their first offer compared to the raise they would have received staying put.
Your company has gone through a hiring freeze or cost-cutting period. During these cycles, merit increases are compressed or paused — but the market doesn't pause. If you've had two years of below-inflation increases while the market rate for your role has risen, the gap between what you earn and what you're worth has widened silently.
Recruiters have started reaching out with roles that mention significantly higher salaries than what you currently earn. This is the market giving you a direct signal. Don't ignore it.
How to Negotiate If You're Underpaid
Finding out you're underpaid is genuinely useful only if you do something about it. Here's how to move from data to action.
Step one: quantify the gap precisely. Don't go into a negotiation saying you feel underpaid. Know that you're at the 28th percentile for your role and location, that the median for your profile is £X, and that reaching the median would require a specific percentage increase. Numbers anchor conversations. Vague feelings don't.
Step two: choose your moment. The best time to raise salary is during a formal review cycle or immediately after a significant win — a product launch, a closed deal, a promotion conversation already in progress. Raising it randomly mid-year is possible but harder. If your company has an annual review in Q4, start the groundwork conversation in Q2 or Q3, not the week before the decision is made.
Step three: separate market data from personal performance. A pay increase grounded in market benchmarks is a different conversation from a merit raise. Be explicit about which argument you're making. "The market rate for this role in this city is X, and I'm currently at Y" is a structural argument that's hard for a reasonable manager to dismiss. If your performance has been strong, layer that in as supporting evidence, not as the primary case.
Step four: have a number ready, not a range. Ranges signal flexibility and invite your employer to anchor at the bottom. Say "I'm looking to move to £72,000" rather than "something in the £68,000–£72,000 range." You can always negotiate down. You cannot negotiate up from a ceiling you've already set.
Step five: prepare for pushback. Common responses include "budget is frozen," "we don't negotiate mid-cycle," and "we pay fairly across the board." Each of these has a counter. The salary negotiation tips article covers specific scripts and responses if you want to go deeper on the mechanics.
Step six: know your walk-away point before you walk in. If your employer cannot move your salary to within a reasonable range of the market — say, within 10% of the 50th percentile — it's worth thinking seriously about whether staying is the right financial decision. Most professionals who negotiate in good faith and hit a wall find that their leverage increases dramatically the moment they hold an external offer.
How Often Should You Benchmark Your Salary?
The honest answer is once a year, minimum. Salary markets shift with macro conditions — inflation, sectoral growth, hiring cycles, remote work normalisation — and a benchmark that was accurate 18 months ago may be meaningfully out of date today.
The post-pandemic period demonstrated this sharply. Between 2021 and 2023, tech salaries in London, Amsterdam, Berlin, and Dublin rose significantly as demand for engineering and product talent outpaced supply. Professionals who had benchmarked in 2019 and not revisited were, in many cases, 15–30% below where the market had moved. Then in 2024, cooling in the tech hiring market compressed those gains. If you had been using 2022 peak numbers as your benchmark in 2025, you'd have been arguing from an inflated baseline and likely getting nowhere.
Benchmark annually. If your company announces layoffs, a hiring surge, or a significant funding event, benchmark again — those events move market rates and your relative position simultaneously. It takes fifteen minutes with a reliable tool. The information is worth far more than that in terms of actual career earnings over time.
Frequently Asked Questions
What's the difference between benchmarking my salary and negotiating my salary?
Benchmarking is the research phase — it tells you what the market is paying for your role, location, and experience level. Negotiation is what you do with that information. You can't negotiate effectively without a benchmark, because you have no factual basis for the number you're asking for. Think of benchmarking as building the case; negotiation is presenting it. Most professionals skip the benchmarking step and go straight to negotiation, which is why they tend to anchor on arbitrary numbers and get weak results.
Can I trust self-reported salary data from sites like Glassdoor or LinkedIn?
Self-reported data is better than nothing but carries real biases. People tend to over-report salaries (anchoring to a desired number rather than their actual total), and the sample is skewed toward professionals who actively use those platforms — who tend to be higher earners. Glassdoor's aggregated figures are more reliable than individual data points, but they're still best used as a directional sanity check rather than a precise benchmark. For European roles specifically, government statistical sources and tools that aggregate multiple datasets tend to be more accurate than self-reported platforms.
Does location within a country affect salary benchmarks significantly?
Yes, often more than people expect. In Germany, Munich salaries for software engineers run roughly 12–18% higher than Hamburg for the same role and seniority, with Berlin sitting somewhere in between. In the UK, London salaries for most professional roles run 20–40% above regional UK equivalents — though that gap has compressed slightly since remote working became normalised. In France, Paris commands a significant premium over Lyon or Bordeaux for finance and tech roles. When you benchmark, always use your actual city, not a national average. National averages are almost never accurate for major urban professionals.
How do I benchmark my salary if my role has an unusual title?
Start by mapping your actual responsibilities to the closest standard job title. If you're a "Growth Hacker" running paid acquisition campaigns, you're functionally a performance marketing manager. If you're a "People Experience Lead," you're an HR manager or HR business partner depending on seniority. Use the standard title for benchmarking purposes, then adjust for any specialisation premium — certain technical specialisations command a 10–20% premium over the generic title median. If your role genuinely sits across two functions (say, a technical product manager who also writes code), benchmark both components and assess which is dominant.
Is it ever a bad idea to benchmark your salary?
Only in one narrow circumstance: if you benchmark and get a result that's higher than expected, and then use that information without verifying the methodology. An inflated benchmark used as leverage in a negotiation can damage your credibility if your employer has their own data showing a different picture. Always cross-reference at least two reliable sources before treating a figure as definitive. Otherwise, benchmarking is always worth doing. The worst outcome is that you confirm you're paid fairly — which is also genuinely useful information.
Check Where You Stand Right Now
You've read this far, which means you're serious about understanding your market position. The next step is simple: run the numbers.
The free salary checker on SalaryVerdict.com takes your role, location, and current salary, and returns your market percentile based on data from BLS, ONS, Eurostat, Destatis, INE, Statistics Canada, and Levels.fyi. It covers 34 roles across 50 locations and takes about 90 seconds to complete. No signup required.
If the result comes back and you're below the 50th percentile, you have something concrete to work with. If you're above it, you know you're in reasonable shape — and you'll know precisely by how much. Either way, you'll be making decisions based on data rather than guesswork, which is how this should always work.