How to Use Public Salary Data to Negotiate a Higher Offer

You’ve landed an interview, the recruiter says “We’ll send you an offer soon,” and suddenly you’re staring at a blank screen, wondering how much you should ask for. The answer isn’t a gut feeling – it’s data you can find online right now. In this post I’ll walk you through the exact steps I use when I’m helping a friend or a client turn public salary numbers into a stronger negotiating position.

Why Public Salary Data Matters

Public salary data is the one free resource that levels the playing field. When a company publishes its pay bands, or when a city releases its employee salaries, you get a real‑world benchmark that’s harder to dispute than a vague market average. Using that data shows you’ve done your homework, and it gives you a concrete reason to ask for more – not just “I think I’m worth it.”

Step 1 – Find Reliable Sources

Government portals

Most states and many large cities post employee compensation on their websites. Look for sections titled “Payroll,” “Employee Compensation,” or “Salary Schedule.” The data is usually in CSV or PDF format, which you can open in Excel or Google Sheets.

Industry surveys

Sites like Glassdoor, Payscale, and the Bureau of Labor Statistics collect self‑reported salaries and aggregate them. While not perfect, they give you a quick sense of the range for a role in a specific city.

Company disclosures

If the firm you’re interviewing with is public, check its SEC filings. The “Form 10‑K” often includes a table of executive compensation, and sometimes the company releases a broader pay range for all employees.

Tip: Stick to sources that update at least once a year. Out‑of‑date numbers can backfire.

Step 2 – Clean and Filter the Data

Raw salary files can be messy. Here’s a quick recipe I use:

Remove outliers – Delete entries that are far above or below the norm (more than two standard deviations). Those are usually errors or special cases.
Match job titles – Look for the exact title you’re applying for. If the data uses “Software Engineer I” but your role is “Junior Developer,” find the closest match.
Adjust for location – If the data is for a national average but you’re in a high‑cost city, apply a cost‑of‑living factor. The BLS publishes regional price indexes you can use.

When you finish, you should have a clean list of salaries that truly reflect the market for your role and location.

Step 3 – Calculate Your Target Range

Now that you have a tidy dataset, it’s time to turn numbers into a negotiating range.

Median salary – The middle value. This is a safe baseline.
75th percentile – The point where 75 % of salaries fall below. This is a strong, but realistic, ask.
Top of the band – If the company publishes a salary band, use the top of that range as your ceiling.

For example, if the median for a data analyst in Austin is $78,000, the 75th percentile is $85,000, and the published band tops out at $92,000, you might aim for $86‑$90k. That gives you room to negotiate while staying within the company’s own limits.

Step 4 – Build Your Narrative

Numbers alone won’t close the deal. You need a story that links the data to your value.

Start with the data – “According to the Texas Workforce Commission, the 75th percentile for a data analyst in Austin is $85,000.”
Add your fit – “My three years of experience building automated reporting pipelines have saved my current employer over $200k in manual labor.”
State your ask – “Given that background and the market data, I’m looking for a base salary of $88,000.”

Keep it concise. Recruiters appreciate a clear, fact‑based pitch more than a long‑winded justification.

Step 5 – Practice the Conversation

I once helped a friend rehearse his salary talk with a friend who works in HR. We role‑played the recruiter’s possible objections: “We have a fixed budget,” or “Our internal equity rules.” Each time we responded with a data point and a brief reminder of the candidate’s impact. The practice made the real conversation feel less like a high‑stakes gamble and more like a routine discussion.

Common Pitfalls and How to Avoid Them

Pitfall	Why It Hurts	Fix
Citing outdated data	Shows you haven’t done recent research	Verify the publication date; use the latest year
Asking for a number far above the band	Makes you look unrealistic	Anchor your ask near the 75th percentile or top of the band
Forgetting total compensation	Salary is only part of the picture	Include bonuses, stock, benefits in your calculations

When to Walk Away

If the employer refuses to move even after you present solid data, it may be a sign of deeper equity issues. A company that won’t respect transparent pay is unlikely to be a champion of workplace fairness. Trust your research and be ready to say “no thanks” if the offer stays far below market.

My Personal Takeaway

The first time I used public salary data in a negotiation, I was nervous. I’d spent hours digging through a city payroll spreadsheet, cleaning it up, and rehearsing my pitch. When the recruiter finally asked “What are your salary expectations?” I felt a calm confidence. I quoted the median, added my own achievements, and asked for a figure right at the 80th percentile. The recruiter came back with an offer that matched my ask, plus a signing bonus. It felt like a win for both sides – the company got a candidate who knew the market, and I got a fair pay package.

The lesson? Data removes guesswork. It turns a vague “I think I deserve more” into a concrete, defensible request. And that’s exactly what Pay Transparency Insights aims to empower job seekers to do.