Tech Salary Transparency: What the Data Actually Shows Now

Tech salary transparency has gone from niche to mainstream in just a few years. States are passing pay transparency laws. Job postings increasingly show salary ranges. Levels.fyi, Blind, and Glassdoor have turned compensation into searchable data. But what does the data actually show—and who benefits?

The picture is more nuanced than “transparency good, secrecy bad.” It reveals widening gaps by role, geography, and company stage. It exposes how disclosure requirements are being gamed. And it highlights who’s still left in the dark. Here’s what the numbers say now.

What Changed

A decade ago, salary was taboo. Candidates were told not to ask. Employers kept ranges secret. The only way to know your market rate was to interview widely and compare offers—or rely on anonymous surveys with uncertain accuracy. Today, that’s flipped. Levels.fyi has millions of data points. Blind has compensation threads. Job postings in disclosure states show ranges. The shift happened fast—driven by regulation, culture change, and the rise of crowdsourced data platforms.

The Geography Divide

Salary transparency laws are spreading. California, Colorado, Washington, New York, and others now require employers to disclose pay ranges in job postings. The effect is uneven. Companies post ranges, but those ranges are often comically wide—$120K to $250K for the “same” role—which makes them barely useful. Some employers exclude remote workers from roles to avoid disclosing for locations with stricter laws. Others list “multiple locations” with a single range that obscures regional differences.

The data that does get shared reveals stark geographic splits. A senior engineer in San Francisco might earn 40% more than an equivalent role in Austin or Denver, even at the same company. Remote-first companies are increasingly tiering pay by cost of living—which can feel fair or punitive depending on where you live. Transparency makes these gaps visible. It doesn’t automatically close them.

FAANG vs Everyone Else

Levels.fyi and similar platforms have made it clear: Big Tech pays more. Significantly more. A mid-level software engineer at Google or Meta can earn $300K–$400K in total compensation (base, bonus, equity). The same level at a Series B startup might pull $150K–$200K. The gap isn’t just at the top—it runs through every level.

Transparency has made that gap impossible to ignore. Candidates walk into negotiations with data. Employers have to compete or explain why they can’t. Some startups have responded by raising comp to stay competitive. Others have leaned into non-salary benefits—mission, equity upside, work-life balance—and accepted that they’ll lose candidates to FAANG. The market is segmenting: top dollar for top companies, trade-offs elsewhere.

Who’s Gaming the System

Transparency laws have predictable loopholes. Wide salary bands ($100K–$200K) comply with the letter of the law while giving little useful information. “Up to” figures that represent the top of band for a principal engineer get applied to roles that will hire at mid-level. Some companies post ranges only when required and pull postings in non-disclosure states.

The data also skews toward people who share. Levels.fyi and Blind are self-reported. High earners may be more likely to contribute—or less, depending on culture. Either way, the sample isn’t random. Use the data as a signal, not gospel. Cross-reference with multiple sources when it matters.

What’s Actually Improved

Despite the caveats, transparency has shifted the conversation. Candidates are less likely to lowball themselves. Employers are more aware of market rates. The old “don’t ask, don’t tell” norm around salary is eroding. That helps underrepresented groups who historically faced larger pay gaps—studies show that when pay is transparent, those gaps tend to narrow.

Transparency has also made equity more legible. Total comp, not just base salary, is now the default frame. That’s important in tech, where equity can dwarf base. Candidates can compare offers more meaningfully. Companies can’t hide behind “competitive salary” when the real story is in the equity structure.

The Bottom Line

Tech salary transparency is real and growing. The data shows big gaps by company, geography, and level. It exposes gaming—wide bands, selective disclosure—but it also empowers candidates and pressures employers to justify their offers. Use multiple sources. Treat ranges as ranges, not guarantees. And remember: transparency reveals the market. It doesn’t fix it. That part still takes negotiation, policy, and collective action.

What the Data Reveals About Gaps

Transparency has made pay gaps visible—and they’re wider than many assumed. Gender gaps persist: women in tech still earn less than men for equivalent roles, though the gap narrows when you control for level and company. Race-based gaps are harder to measure (many datasets don’t include demographic info), but anecdotally they’re real. Transparency doesn’t fix these gaps—but it makes them harder to ignore. Employers who post ranges have to justify them. Candidates can benchmark themselves and negotiate from data.

The junior developer market has also gotten more legible. Entry-level roles that used to hide behind “competitive” now show ranges—and often low ones. The gap between bootcamp grads and CS degree holders, between internships and first full-time roles, is now visible. That helps candidates set expectations and pushes employers to compete for talent at every level.

Remote Work and the Transparency Frontier

Remote work has complicated the picture. Companies that hire anywhere face a choice: pay everyone the same, or tier by location. Many have chosen tiering—same role, different pay based on where you live. That’s transparent in some ways (you know your tier) and opaque in others (you don’t always know what tier you’re in until you negotiate). Transparency laws haven’t fully caught up. A remote role with “multiple locations” might list a single range that doesn’t reflect your actual offer.

The data shows that remote workers in low-cost areas often earn less than their Bay Area counterparts—even at the same company. Whether that’s fair depends on your perspective. Transparency at least makes the trade-off visible.