How to Research Your Market Rate Before Negotiating

Why Market Data Is the Single Best Negotiation Lever

Most salary conversations stall because the candidate says "I was hoping for more" and the hiring manager says "that is at the top of our range." Neither side has proven anything. When you show up with third-party data -- median pay for the role in the metro area, adjusted for your experience band -- the conversation shifts from feelings to facts. Recruiters know these numbers exist. The difference is whether you know them too.

Research from Glassdoor's 2025 salary negotiation survey found that candidates who cited specific market data received offers 7-12% higher than those who negotiated on gut instinct alone. That is not a rounding error; on a $120,000 base salary it is worth $8,400 to $14,400 per year, compounding over every future raise and bonus calculation.

Where Salary Data Actually Comes From

Not all salary data is created equal. Here are the primary sources, ranked roughly by reliability:

• Bureau of Labor Statistics (BLS): Government-collected, massive sample sizes, but slow to update (usually 12-18 months behind) and grouped into broad occupation codes. Best for establishing a reliable baseline.
• Levels.fyi: Self-reported by tech workers, verified against offer letters. Excellent for software engineering, product management, and data science. Less useful outside tech.
• Glassdoor / Indeed / Payscale: Crowdsourced with large sample sizes. Useful for a wide range of industries. Watch for outdated entries that drag averages down.
• Company H-1B filings (via h1bdata.info): Legally required salary disclosures for visa sponsorship. Real numbers from real employers, though skewed toward roles that commonly sponsor.
• LinkedIn Salary Insights: Good for role-specific benchmarks. Requires a LinkedIn profile. Data skews toward mid-career professionals.
• Recruiter conversations: Off the record but often the most current. Ask recruiters: "What is the range you are seeing for this level right now?"

The best approach is triangulation. If three independent sources all point to $130K-$155K for a Senior Product Manager in Austin, you can be confident that range reflects reality.

How to Adjust for Location

A $150,000 salary in San Francisco and a $115,000 salary in Raleigh can deliver nearly identical purchasing power. Cost-of-living (COL) multipliers let you compare apples to apples. The most cited index is the Council for Community and Economic Research (C2ER), though BestPlaces and Nerdwallet offer free calculators that use similar underlying data.

The key adjustments: housing (typically 60-70% of the COL difference), state income tax (0% in Texas and Florida vs 13.3% top rate in California), and commute costs. When evaluating an offer, convert both your current compensation and the offer to the same baseline city, then compare.

Remote Work and Geographic Arbitrage

In 2026, roughly 35% of knowledge workers are fully remote. Some companies pay location-adjusted salaries (GitLab, Stripe), while others pay the same regardless of where you sit (Airbnb, Reddit). This creates an opportunity: earning a New York salary while living in a city with half the cost of living.

Before you celebrate, check the fine print. Many employers now require you to report your work location and adjust compensation if you move. And some states require payroll registration the moment you work there for more than 30 days, which can affect an employer's willingness to hire across state lines.

Reading Salary Ranges: 25th, 50th, and 75th Percentile

When a source reports a "range," understand what the percentiles mean:

• 25th percentile: Entry point. Often matches junior candidates or those switching industries. If you have 5+ years of relevant experience and an employer offers this, push back.
• 50th percentile (median): The "market rate" most people reference. A fair target for candidates with solid, matching experience.
• 75th percentile: Top of market for the role. Reaching this typically requires niche skills, strong competing offers, or a track record of measurable business impact.

Do not confuse the 50th percentile with the "average." Averages are pulled upward by outlier executive packages. Median is almost always the more useful number.

Putting It All Together

Before your next negotiation, build a one-page "market brief." List the role title, target metro, three data sources with their reported ranges, and the percentile you are targeting based on your experience. Print it or keep it on screen during the conversation. You do not need to hand it over, but having it ready transforms vague assertions into confident, data-backed statements.