Why 86% of Tech Jobs Are Still Playing Hide-and-Seek With Salary

I was on a call with a junior developer last week who'd just finished five interviews with a startup. Five rounds. When they finally asked about compensation, the number they heard made it clear those hours were wasted. They could have known in five minutes if someone had just... told them upfront.

That conversation stuck with me until I read about someone's analysis of 42,000 live tech job postings. The finding was brutal: only 14% actually list a salary. Fourteen percent. I've been hiring and looking for work in this industry long enough to know this happens constantly, but seeing it quantified across actual market data hit different. It's not anecdotal frustration anymore—it's a pattern we're all swimming in.

This isn't just annoying. It's a form of friction that wastes everyone's time and compounds inequality in ways the industry doesn't like to admit.

The Real Cost of Salary Silence

Most people think about this problem wrong. They focus on the candidate's frustration—and yes, that's real. But the actual damage runs deeper.

When companies don't post salaries, they're not being clever. They're shifting negotiation risk onto candidates. A junior developer doesn't know if they're supposed to ask for $80k or $150k. A mid-level engineer doesn't know if they're being lowballed by 30%. The asymmetry is complete, and it compounds for candidates from underrepresented backgrounds who often lack the networks to triangulate market rates.

I've been the person on both sides of this. Early in my career, I accepted an offer that was genuinely below market because I had no reference point. Now, when I'm hiring, I post ranges because I've lived that anxiety.

The data shows designers disclosure salary more often (19%) while mobile and data roles hide it most (11% each). Why? Maybe because mobile and data teams are newer, or the companies hiring for those roles tend to be growth-stage startups that haven't standardized their process yet. But that's speculation. What's not speculation is that five out of six postings tell you absolutely nothing.

What the Data Actually Reveals

The person who built this dataset pulled information from major ATS platforms—Greenhouse, Lever, Ashby—tracking the same jobs daily. This is meticulous work. They deduplicated postings (companies repost the same role constantly), pulled only disclosed numbers (not guesses), and tracked real-time open/close velocity.

The breakdown matters. Full-stack roles have 16% disclosure. Backend similarly sits at 17%. But when you look at the median bands for roles that do disclose—$150k–$200k for backend and full-stack—you realize the companies that are transparent tend to be paying competitive rates.

There's a signal in that silence. The companies not posting salaries? I'd hypothesize they're either below-market or they want the luxury of negotiating downward. Neither is a place I want to work.

The article also noted something I wasn't expecting: hiring isn't stalling. Net new openings are outpacing closures by thousands weekly. The "tech is dying" narrative doesn't match the actual job board velocity. Defense and hardware companies (SpaceX, Anduril, Shield AI) are growing fastest—roles that typically do pay competitively and are transparent about it.

My Take: Why This Matters Beyond Job Hunting

I care about this data partly because I'm building a career in Islamabad, in a market that's increasingly global but still smaller than Silicon Valley. Salary transparency is a competitive advantage for companies, not a liability. When I post a role with a range, I get better candidates faster because the signal is clear.

More fundamentally, pay transparency—or the lack of it—is a mirror for company culture. If you're not willing to be honest about compensation in the job posting, what else are you being opaque about? Code reviews? Technical debt? Security incidents?

The frustration I have with the 14% figure isn't moral grandstanding. It's practical. Every candidate who wastes three interview rounds discovering misalignment is a candidate who didn't interview for the role that would have worked. Every engineer who accepts an offer 15% below market is an engineer who'll hit a resentment cliff in six months.

What I'd Do Differently

If I were running recruiting, I'd post salary ranges. Not a point estimate—a range. And I'd make it real, not the insultingly wide $50k spreads I see sometimes. Three months of data collection to get market-accurate bands is worth the investment.

I'd also audit my own historical postings. I've probably been part of this problem.

Your Move

If you're job hunting: that original article has a directory of which companies are transparent. Filter for them. If you're hiring: post your damn ranges. You'll get better fits faster, and you'll attract the candidates who actually want to work at a company that respects their time.

Source: This post was inspired by "I measured how many tech job postings actually list a salary. It's 14%" by Dev.to. Read the original article