How to Negotiate Your Salary: Know Your Market Rate with BLS Data
Most people approach salary negotiations without hard data. They might have a number in their head, or a rough sense from talking to colleagues, but they walk into the conversation without the kind of credible third-party evidence that actually moves employers. Bureau of Labor Statistics wage data changes that dynamic. This guide walks you through how to find, interpret, and use BLS data to negotiate confidently — whether you're starting a new job, asking for a raise, or evaluating a competing offer.
Why BLS Data Is the Most Credible Source for Salary Research
There are dozens of salary data sources available — Glassdoor, LinkedIn Salary, Levels.fyi, PayScale, and others. Each has value, but they also have well-documented limitations. Self-reported salary data tends to skew toward higher earners, because people with above-average salaries are more motivated to share them. Platform samples may be biased toward certain industries, company sizes, or demographics.
The Bureau of Labor Statistics Occupational Employment and Wage Statistics (OEWS) survey is different. It is a federally mandated survey of more than 1.1 million US business establishments. Response is legally required for sampled businesses. The methodology is designed by statisticians to produce representative, unbiased estimates of what workers in each occupation actually earn — not what they say they earn, and not what job postings advertise.
This makes BLS data uniquely useful in a negotiation context. When you cite a median salary from the Bureau of Labor Statistics, you're citing a government agency's finding — not a number from an app that the hiring manager has reasons to distrust. It's hard to argue with the federal agency that produces official employment statistics.
Step 1: Find the Right Occupation Code
BLS data is organized by Standard Occupational Classification (SOC) codes. Before you can pull salary data, you need to know which code matches your role. The BLS occupational classification system can seem opaque at first, but for most common roles the mapping is straightforward.
Start at the OEWS data page and use the occupational search to find your role. Common examples:
- Software developers fall under SOC 15-1252 (Software Developers) or 15-1253 (Software Quality Assurance Analysts)
- Registered nurses are SOC 29-1141
- Accountants and auditors are SOC 13-2011
- Civil engineers are SOC 17-2051
- Elementary school teachers are SOC 25-2021
If your role doesn't map neatly, use the closest match and be prepared to explain in your negotiation why your role is more similar to a higher-tier classification. A senior DevOps engineer, for example, might reasonably argue they should be benchmarked against the software developer median rather than a more junior IT support category.
Step 2: Pull Metro-Level Data for Your City
National median salaries are a starting point, but they mask massive geographic variation. A registered nurse salary in San Francisco is roughly 50% higher than the national median for the same role, while a registered nurse salary in Dallas sits closer to the national average. Using the wrong geographic benchmark will undermine your negotiation.
On this site, you can look up metro-level salary data directly for common occupations. For your BLS research, navigate to the OEWS Metropolitan Area estimates and download the table for your metro area or state. The BLS publishes separate tables by metropolitan statistical area (MSA) — these are the figures you want for a geographically specific negotiation.
If you're negotiating for a role in Chicago, use Chicago-area figures. If you're negotiating remote work with a company headquartered in New York, clarify upfront whether the role is pegged to New York rates or to your location — the difference can be substantial. The accountant salary in Chicago and accountant salary in New York represent meaningfully different market rates, and that distinction matters in any negotiation that involves geographic pay bands.
Step 3: Use the Full Distribution, Not Just the Median
The median is the midpoint — half of workers in that occupation and metro earn above it, half below. But the median alone doesn't tell you where you should land in the distribution. For a negotiation, you also want the 75th percentile (P75) and, if available, the 90th percentile (P90).
Here's how to use them:
- If you're entry-level: The median is a reasonable target for where you want to be after 2–3 years. Entry offers typically start between the 25th and 50th percentile. Anything below the 25th percentile should raise a flag.
- If you're mid-career with solid experience: The median should be your floor, and the 75th percentile is a reasonable ceiling to negotiate toward.
- If you're a senior specialist or manager: The 75th percentile is your baseline and the 90th percentile is a legitimate target if you have rare skills, demonstrated results, or a competing offer.
Using the distribution rather than just the median also gives you a defensible range. "BLS data shows the median for this role in this city is $X, and the 75th percentile is $Y — given my experience, I'm targeting the upper half of that range" is a much more structured negotiating position than simply citing a number.
Step 4: Frame the Data Correctly
How you present salary research matters as much as what the data actually says. A few principles:
Lead with the data, not your personal need
Salary negotiations go sideways when candidates justify their asks with personal financial needs — rent, student loans, what their previous employer paid. Those factors are irrelevant to the employer. What matters to them is market rate and your value relative to it. Frame everything around market data: "Based on BLS OEWS data for this metro, the median for this role is X. Given my background in Y and Z, I'm targeting the upper end of that range."
Bring printouts or links
Have the actual BLS data accessible — either printed or a link you can share. This shifts the conversation from "you say / I say" to an objective third-party reference. Hiring managers who aren't familiar with the BLS will be impressed; those who are will respect that you did your homework.
Address cost of living proactively if relevant
If you're negotiating a remote role with a company in a different city, or if you're relocating, address the geographic question upfront. Reference the specific metro-level data for the location the employer is using as their benchmark. The civil engineer salary in Houston is a very different data point than the same role in Boston — if the employer is trying to pay you Houston rates for a role anchored in a high-cost market, you need to bring both figures to the table.
Step 5: Handle the Counteroffer Stage
When an employer counters with a number below your ask, the data-backed approach continues to be your best tool. If the counteroffer is below the median for your role in your market, you can simply point that out — "I appreciate the offer, but based on the BLS data for this metro, that figure is actually below the median for this role. I was hoping we could get closer to the market rate."
If the counteroffer is above the median but below the 75th percentile, you have a choice: accept, counter with the specific percentile you're targeting and your rationale, or evaluate whether the total package (benefits, equity, flexibility) bridges the gap.
If you have a competing offer, use it — but use the data to anchor the competing offer in market context rather than just citing the dollar figure. "I have an offer from another employer at X, which aligns with what the BLS data shows for the 75th percentile in this market" is more persuasive than simply presenting the number as a threat.
When BLS Data Alone Isn't Enough
BLS data is powerful, but it has real limitations. The data is released annually with an 18-month lag — the May 2024 survey is released in spring 2025, so by the time you're reading this it's nearly two years old. In fast-moving markets like technology, compensation trends can shift meaningfully in that time.
Supplement BLS data with current job postings (which increasingly list salary ranges due to pay transparency laws in states like California, Colorado, and New York), conversations with recruiters who work your market daily, and community salary data from forums specific to your industry.
The BLS provides the credible anchor. Layer current-market intelligence on top of it to give yourself the complete picture. A hybrid approach — "BLS data puts the median at X, and recent postings and my recruiter conversations suggest the market has moved 10–15% above that over the past year" — is more compelling than either source alone.
Check Your Own Market Rate
Start by looking up the salary data for your specific role and city on this site:
- Software Developer Salary in San Francisco
- Accountant Salary in Chicago
- Registered Nurse Salary in New York
- Civil Engineer Salary in Houston
- Financial Analyst Salary in Boston
- Browse all job titles and cities
Then go directly to the BLS OEWS data to pull the full percentile distribution for your specific occupation and metro area. That combination — this site for quick orientation, BLS for the full authoritative picture — gives you everything you need to walk into your next negotiation with confidence and credible data behind every number you cite.