·9 min read

How Much Below Market Is Actually Underpaid — And What to Do About It

Wondering how much below market is underpaid? We break down the thresholds by role, seniority, and location so you know when to act.

Most professionals have a vague sense they might be underpaid. But "vague sense" doesn't win you a pay rise. What you need is a number — a clear threshold that tells you whether your salary is a reasonable variation from the market or a genuine shortfall worth fighting to close.

So let's answer the question directly: how much below market is underpaid? The honest answer is that it depends on seniority, industry, company type, and geography. But there are defensible benchmarks, and this article will give them to you.


The Threshold Question: Where Does "Normal Variation" End and "Underpaid" Begin?

Salaries aren't a single number — they're a range, and legitimate variation exists within that range. A junior software engineer in Amsterdam earning €52,000 and one earning €58,000 are both within normal market variance. Neither is obviously underpaid. But if that same engineer is earning €42,000, something is wrong.

The widely-used standard in compensation analysis is the compa-ratio — your salary expressed as a percentage of the market midpoint. A compa-ratio of 100% means you're exactly at the midpoint. Most HR departments consider anything between 90% and 110% to be a healthy, competitive range. Below 90% is where you start entering underpaid territory. Below 80% is a serious problem.

Translated into real numbers: if the market midpoint for your role is €60,000, a salary of €54,000 puts you at a 90% compa-ratio — borderline. A salary of €48,000 puts you at 80% — definitively underpaid. That 20% gap is not a rounding error. Over a five-year career, compounding that shortfall can cost you €50,000 or more, not counting the lost pension contributions, bonus calculations, and future offer anchoring that flow from a suppressed base salary.

For junior professionals, the acceptable variance is slightly tighter because base salaries are lower and proportional gaps feel larger. For senior and staff-level roles, the bands widen because total compensation packages diverge significantly — equity, bonuses, and benefits can justify a lower base in some contexts. But even then, if your base alone is more than 15% below the market median for your level, you have a legitimate grievance.


Seniority Levels Change the Calculation Significantly

Being 10% below market as a junior is a different problem than being 10% below market as a senior. Here's why it matters — and what the numbers actually look like across levels.

Junior professionals (0–2 years experience) in most European tech and finance hubs are working with base salaries that leave little room for significant deviation. A junior data analyst in Berlin earning €38,000 when the market sits at €44,000 is 13.6% below market — and that gap will compound into their next offer, since hiring managers frequently anchor to your current salary. The free salary checker is particularly useful at this level because junior professionals often have the least negotiating information and the most to lose from staying silent.

Mid-level professionals (3–6 years) are where underpayment becomes most common and most damaging. This is the cohort most likely to have stayed at one employer through two or three incremental pay reviews that failed to keep pace with market movement. A mid-level product manager in London might have joined at £58,000 in 2021, received 3–4% annual increases, and now sits at £65,000 — while the external market for that role has moved to £78,000. That's a 16.7% shortfall created entirely by loyalty and inadequate internal benchmarking.

Senior professionals (7+ years, lead or principal roles) face a different version of the problem. Total compensation packages are more complex, and base salary represents a smaller slice of the overall deal. A senior engineer at a Series B startup might have a lower base than their Big Tech counterpart but hold equity worth multiples of that gap. Comparing base salaries alone at this level can mislead. That said, if your base is more than 20% below market median and your equity hasn't vested or is speculative, you are almost certainly being underpaid in any meaningful sense.


Company Type and Industry Vertical: The Gaps Are Larger Than You Think

The sector you work in often matters more than your specific role. A software engineer at a German Mittelstand manufacturing company and a software engineer at a Berlin-based fintech are doing comparable technical work, but their salaries can differ by 30–40%. Neither is necessarily "wrong" — but the fintech engineer who doesn't know this comparison exists is leaving money on the table.

In European markets specifically, the public-sector and non-profit brackets tend to pay 15–25% below private-sector equivalents for the same roles. That gap is well-documented and often accepted in exchange for job security, pension benefits, or mission-driven work. It becomes a problem only when the worker doesn't realise the tradeoff they're making.

Within the private sector, the highest-paying verticals for knowledge workers are typically: financial services and fintech, enterprise software and SaaS, management consulting, and pharmaceuticals. Roles in retail tech, media, and traditional professional services (outside of law) often pay 10–20% below these verticals for equivalent seniority. If you're a mid-level data scientist in a retail business earning €65,000 and a friend at a fintech earns €82,000, you're not comparing apples to apples — but the gap still tells you something real about your options.

For a concrete example: a product manager salary Berlin at a Series A–B startup typically ranges from €70,000 to €90,000 at mid-level. The same role at a DAX-listed corporation tends to cluster around €75,000–€85,000, but with more structured bonus schemes. An e-commerce company might offer €60,000–€72,000. The spread is significant, and where you land within it tells you something about whether your current number is defensible.


Location Within a Country Matters More Than Most Professionals Realise

People benchmark against national averages and then wonder why the numbers don't match their experience. City-level data is more accurate and often more actionable. A mid-level software engineer salary London sits around £70,000–£90,000 at the mid-level band — substantially higher than the UK national median for that role, which ONS data places considerably lower. If you're working remotely for a London-based employer from Manchester and earning £55,000, you need to decide which benchmark applies: local cost of living, or the employer's headquarters market.

In Germany, Munich and Frankfurt salaries for knowledge workers run roughly 12–18% above the national median, while Leipzig or Dresden roles in the same function might sit 10–15% below it. In France, the Paris premium is real and significant — a senior finance professional in Lyon might earn 20% less than a counterpart in La Défense, even at the same firm. These aren't arbitrary gaps; they reflect labour market depth, cost of living, and concentration of high-paying employers.

The practical takeaway: always benchmark at the city level first, not the country level. National averages flatten regional variation and can make an underpaid professional in a high-cost hub look fine on paper. You can see how we calculate salaries to understand how we account for these location adjustments in our own data.


The Signs You're Underpaid (Beyond Just the Number)

Sometimes the number itself is ambiguous — you're sitting at 87% of market median, which is borderline but not obviously egregious. In those cases, behavioural and structural signals can confirm what the data suggests. Check out the full breakdown in our signs you are underpaid article, but the most reliable indicators are worth covering here.

The first signal is salary stagnation relative to your growth. If your responsibilities have materially expanded — you're managing people, owning larger deliverables, or operating at the next level's scope — but your pay hasn't reflected that shift, the gap between your market value and your current salary is widening in real time. Employers often rely on inertia here. You get the responsibilities without the formal title change or pay adjustment, and suddenly you're doing senior work for mid-level pay.

The second signal is new hires earning more than you. This happens constantly and is a direct consequence of companies adjusting offers to meet the current market while letting existing salary bands stagnate. If you've been at a company for three years and a newly-hired peer at your level earns 15% more, you haven't received 15% worth of raises, and the company is implicitly telling you that your loyalty costs less than their hiring budget.

The third signal is your salary history anchoring your new offers. When recruiters ask for your current salary — which is now illegal in several European jurisdictions — they're trying to anchor their offer to your existing suppression. The moment you recognise that your current salary is low, you should stop treating it as a credible reference point in any negotiation.


How to Negotiate If You're Underpaid: Specific Steps That Work

Knowing you're underpaid is step one. Fixing it requires a process, not just a conversation. Here's what actually moves the needle.

Step 1: Quantify the gap precisely. Don't walk into a negotiation saying "I think I'm below market." Walk in with specific data: your role, your seniority level, your location, and a defensible market range. Use multiple sources — public salary databases, recruiter conversations, peer benchmarks. The free salary checker gives you a market percentile for your exact role and location, which is more useful in a negotiation than a vague range from a general salary survey.

Step 2: Build the business case around your contribution, not your needs. "I need more money" is not a negotiating position. "I'm delivering senior-level output at a mid-level salary, the market rate for this scope of work is £X, and I'd like to align my compensation accordingly" is. Frame the ask in terms of retention risk and market alignment, not personal finance.

Step 3: Choose your moment carefully. Performance review cycles are the obvious window, but they're not always the most effective. A negotiation immediately following a visible win — a product launch, a major client close, a successful project delivery — gives you a concrete anchor for the conversation. Timing matters.

Step 4: Get a competing offer if you can. A real offer from a competitor is the single most powerful negotiating tool available. It removes subjectivity from the conversation and creates a genuine retention decision for your employer. You don't need to be actively looking to have an exploratory conversation. If the external market confirms you're underpaid, that data point is valuable whether you use it in a negotiation or eventually walk out the door.

Step 5: Know your walkaway number. Before any negotiation, decide the number below which you will leave. Not threaten to leave — actually leave. This clarity protects you from accepting a token raise that closes 30% of a 25% gap and resets your ambition for another two years. For deeper tactics, see the full salary negotiation tips guide.


FAQ: What Professionals Actually Ask About Being Underpaid

Is 10% below market salary considered underpaid?

Ten percent below market sits at the boundary of what most compensation frameworks consider acceptable variance. In a strict compa-ratio model, 90% is the floor of the competitive range. Whether it's a problem depends on context: if you have exceptional benefits, significant equity, or high job security, the tradeoff might be conscious and reasonable. If you have none of those compensating factors and simply haven't negotiated in two years, then yes — 10% below market is underpaid, and it'll compound if you don't address it.

How do I know what the market rate is for my role?

The most reliable approach combines multiple data sources: official statistical sources like ONS, Eurostat, or Destatis for baseline national data; role-specific platforms like Levels.fyi for tech compensation; recruiter conversations for current live-market data; and peer networks where people actually share numbers. No single source is complete. The reason we built SalaryVerdict is to aggregate these sources into a single percentile ranking for your specific role and city — because the scatter across individual sources is wide enough to be confusing without some synthesis.

Can you be underpaid even with a good salary?

Absolutely. A software engineer earning £90,000 in London sounds well-paid in absolute terms, but if the market for that role and seniority level sits at £110,000, they're 18% below market. "Good salary" is always relative to a reference point, and the relevant reference point is what the market would pay you today — not what feels like a lot compared to your previous job or your peers in different industries.

What should I do if my employer refuses to close the gap?

Document the refusal, continue developing your external options, and set a timeline. If a company acknowledges you're below market but declines to address it — citing budget, policy, or timing — that tells you something real about how they value your retention. Many professionals find that a formal external offer, or even a resignation letter, accelerates internal movement that was previously described as impossible. If the gap is large and the employer won't move, the most financially rational response is usually to leave.

Does location affect how much below market is considered underpaid?

Yes, significantly. High cost-of-living cities have tighter tolerance for below-market salaries simply because the absolute impact of a 10% shortfall is larger. A 10% gap on a €45,000 salary in Warsaw is €4,500. A 10% gap on a €95,000 salary in Zurich is €9,500. The percentage threshold matters, but so does the absolute number and your cost of living context. Always benchmark at the city level, not the national level, for the most actionable result.


Find Out Exactly Where You Stand

If you've read this far and you're not certain whether your salary clears the market threshold, that uncertainty is worth resolving today — not at your next performance review. Use the free salary checker to enter your role, location, and current salary and get your market percentile in under a minute.

The tool covers 34 roles across 50 locations, drawing on public benchmark data from BLS, ONS, Eurostat, Destatis, and others. It won't give you a vague range. It'll tell you where your number sits relative to the market — so you can stop guessing and start negotiating from a position of actual information.

Find out if you're underpaid

Enter your role, location, and salary. Takes 30 seconds.

Check my salary →