Mercer: Tech wage boom deepens inequality

Tech pay outpacing every other sector reads like a revelation, but let's not kid ourselves — it's a headline that mostly confirms what hiring managers have been adjusting to for years. Payscale's Labor Market & Wage Trends Report, highlighted by HRTech Series, is useful because it broadens individual anecdotes into a pattern. The pattern, though, has wrinkles that matter for strategy, not just parade-ground talk about “tech scarcity.”

Start with the part everyone pretends is mysterious and really isn’t: wage growth in tech is a demand story dressed up as a compensation story. Firms keep paying more because they keep competing for the same scarce skills. You can argue internally about whether it's cloud, AI, or some niche framework driving the latest bidding war, but the mechanism is identical every time — intense demand meets limited supply and prices rise until someone blinks. Someone still has to pay for it.

That price pressure is not neutral across employers. It rewards firms that actually convert premium talent into premium economics — scale businesses with product-led distribution, or companies that can turn incremental features into incremental revenue. Distribution eats elegance; a well-distributed product can monetize a great engineer in quarters, while a beautifully engineered internal tool might never pay back its fully loaded cost. For employers outside that club, the wage story is a liquidity problem: you can match market pay, but can you monetize the hire at the same velocity?

This is where compensation stops being an HR topic and becomes a unit-economics topic. It's not just base salaries; it's equity, signing bonuses, remote stipends, and the cottage industry of perks that get recycled into headline “tech pay.” The report’s conclusion pressures HR and finance to rethink role economics: which hires are growth multipliers and which are merely capacity expansion? That’s where margins start talking. If your internal business case for a role can’t survive the new clearing price, the issue isn’t the report — it’s your model.

Of course, Payscale is giving you an averaged picture, and averages are blunt instruments. The finding that tech wage growth outpaces other industries is directionally right. The harder question is what, exactly, is being measured.

Three blind spots skew the narrative.

First, geography and remote work. If wage growth reflects nationalized pay bands for remote roles, then “tech pay” is really coastal compensation leaking into every ZIP code with broadband. In that world, a headline about tech outpacing all industries may say more about where the jobs are benchmarked than about universal pressure on every employer.

Second, employment status. Contractor and gig rates can spike while full-time salaries move more slowly. If a report mixes project work with permanent roles — a common methodological shortcut — it can make structural wage inflation look scarier than it actually is for core staff, while underplaying the operational risk of relying on a contingent workforce whose pricing resets constantly.

Third, job-class mapping. “Tech” is a broad bucket. Product managers, SREs, data scientists, and frontend developers do not share the same supply curve or career alternatives. Aggregation can hide a clean transfer of budget inside the bucket: some roles get dramatically repriced, others stagnate, but the blended average looks like steady uplift for everyone.

Call this the measurement problem. The report signals a real trend, but it rarely tells you whether you’re staring at a permanent re-pricing of specific skills or a temporary mismatch amplified by remote hiring and contractor substitution. Executives who treat the headline as a universal law will overpay in the wrong places and underpay where it hurts.

Non-tech employers reading the same headline tend to default to resignation: “We can’t compete with tech on pay.” That’s only partly true, and mostly unhelpful. They have three broad responses, none of them painless.

Raise selectively. Identify roles where external competition directly threatens revenue or critical operations, and pay those up. That demands uncomfortable role-level ROI thinking — not every vacancy earns a premium offer, and some roles you’ve historically treated as “nice to have” turn out to be core.

Redesign work. If you can’t outbid tech, you restructure the job so the highest-cost skills are spread across more output or decomposed into tasks that can be done at different price points. That means better tooling, cleaner processes, and brutal clarity about what actually requires top-tier expertise. The demo is not the business; it’s the enabler of scaled labor efficiency, not a slide in the employer-brand deck.

Accept turnover as a cost. Some sectors will simply live with higher churn in certain roles and size recruiting and training engines accordingly. It’s ugly and it commoditizes knowledge, but it can be rational if the work itself doesn’t create much marginal productivity when done by a “star” versus a competent replacement.

There is a tempting counter-argument: tech wage growth is cyclical, driven by a few hot segments, and will cool as hiring slows or automation gets better. That’s plausible on the surface. Hires slow, budgets tighten, and the headline growth curve flattens.

But that story underestimates structural change. Once remote pay parity becomes embedded, floors rarely go back down. Baseline compensation for many tech roles has been quietly repriced higher in the markets that matter, and delayed adjusters will be dealing with retention and hiring problems long after the headlines move on. The spike may fade; the new reference point sticks.

The Payscale report says tech wages are rising faster than other industries. The real divide will be between employers that treat that as a budgeting nuisance and those that use it as a forcing function to redesign how, and where, value actually gets produced.