You found the perfect job posting. Title fits, stack matches, location works. Then you scroll down and the salary line says... nothing. Or worse: "competitive."

That single missing number is the most expensive blank space in your job search. Apply without doing salary research and you'll either be screened out for asking too much or, more often, leave $20K-$80K on the table because you anchored low.

Researching salary before you apply isn't optional anymore. It's the difference between negotiating from data and negotiating from hope. Here's how to do it properly in 2026.

Why Salary Research Has to Happen Before You Apply

Most candidates research salary after they get an offer. That's too late. By then you've already been asked "what are your expectations?" three times in three interviews, and whatever number you blurted out is now the ceiling.

Researching beforehand gives you three advantages:

You filter out underpaying roles before wasting hours on applications and screens.
You walk into the recruiter call with a number instead of fumbling.
You know what's standard for the company, role, location, and seniority — so you can spot a lowball offer instantly.

If you're not also tracking which salary ranges you've quoted to which companies, read How to Track Your Job Applications Like a Pro — keeping receipts on your own asks is part of the game.

The Tools That Actually Have Real Salary Data

Not all salary sites are equal. Some are mostly self-reported guesses, others pull from verified offers and pay stubs. Here's the stack worth using:

Levels.fyi — Best in class for tech, especially big tech and senior IC roles. Verified offers, breakdown by base/stock/bonus, level mappings across companies.
Glassdoor — Wide coverage but skews self-reported. Great for ranges, weak for exact totals.
Payscale — Strong for non-tech and mid-market roles. Their salary report tool factors in years of experience.
Salary.com — Good for traditional industries, HR-grade benchmarks.
LinkedIn Salary — Pulls from member-submitted data, decent for regional norms.
H1B Salary Database (h1bdata.info) — Public US disclosure data. If a company sponsors visas, every salary they filed is searchable. Underrated goldmine for tech base salaries at large US employers.
BLS.gov — US Bureau of Labor Statistics. Boring but authoritative for occupational medians by metro.
Built In Salary Reports — Strong for tech in major US metros (NYC, SF, LA, Chicago, Austin).

Use at least three sources. If three independent tools say a Senior Backend Engineer in Berlin makes €85-110K, that's your range. If only one site says €140K, that's an outlier.

Use Search Operators to Pull Public Salary Data

Most job boards now hide salary, but the data is still leaking onto the open web. Boolean and Google search operators surface it fast.

Try these dorks:

site:levels.fyi "Stripe" "Senior Software Engineer"
site:glassdoor.com "salary" "Atlassian" "Product Manager"
"base salary" "RSU" "Datadog" filetype:pdf
site:reddit.com "offer" "Snowflake" "L4"
site:teamblind.com "TC" "Cloudflare"

Reddit threads in r/cscareerquestions, r/recruitinghell, and country-specific subs (r/germanyjobs, r/AusFinance) are full of unfiltered offer breakdowns. Blind is even more raw if you can access it.

If you want to chain these operators without typing them by hand, the Job Search Query Builder lets you compose the boolean string once and fire it across Google, LinkedIn, and the other engines you actually care about. Same logic that finds hidden jobs also finds hidden pay data.

Layer in Levels, Locality, and Total Comp

A "Senior Engineer" at one company is a "Staff" at another and a "Lead" at a third. Don't compare titles — compare scope and level.

Use levels.fyi's level matrix to map titles across companies.
Adjust for cost of living with Numbeo or Nomadlist if you're considering remote/relocation.
Always look at total compensation, not base. A $160K base with no equity is often worse than a $140K base with $60K/year RSUs and a 15% bonus.
Factor in benefits: 401k match, health premiums, PTO, learning budget, equipment stipend. These can swing $10-20K of real value.

For remote roles in particular, salaries vary wildly by company policy. Some pay SF rates everywhere; others geo-adjust by 30-50%. Check the company's stated remote pay philosophy before you anchor a number.

What to Do With the Data Once You Have It

Salary research is only useful if it changes your behavior. Once you have a defensible range:

Set a floor — your walk-away number. Below this, don't even take the call.
Set a target — the realistic top of band for your level and location.
Set a stretch — what you'd ask for if everything in the interview went perfectly.
Document your sources — three data points per role. When the recruiter asks "where did you get that number?", you have a real answer.
Quote a range, not a point — and make the bottom of your range your actual target. Recruiters anchor to the bottom number, always.

Pair this with strong sourcing — if your pipeline is full, you have leverage. The Job Search Query Builder helps keep that pipeline wide so no single offer holds you hostage.

Don't Skip This Step

Spending two hours on salary research before applying can be worth tens of thousands of dollars over the life of a single role. It's the highest hourly-rate work you'll do in the entire job search.

Once you've got your numbers, go back and audit which roles in your tracker actually clear your floor. While you're at it, double-check you're not falling into any of the 10 Job Search Mistakes That Cost You Interviews — a strong salary range means nothing if your applications never make it past the recruiter.

Research first. Apply second. Negotiate from data, not from fear.

How to Research Salaries Before You Apply