Most salary negotiations fail before they begin because workers anchor on feelings rather than data. Percentile data changes that dynamic. Instead of saying “I feel underpaid,” you can say: “According to BLS OES May 2024 data, my salary places me at the 38th percentile for software developers in Texas — the median is $127,260, and I’m asking to move toward that benchmark.” That framing is far harder for a manager to dismiss than a subjective appeal.

Why Government Data Carries Weight

Government data carries particular weight in these conversations. Unlike Glassdoor or Levels.fyi, the BLS surveys 1.1 million employer establishments directly — the sample is massive, the methodology is public, and it’s the same source the federal government uses for economic policy. Presenting BLS figures signals that you’ve done serious research, not just checked a crowdsourced site after a frustrating performance review.

Timing and Framing

Timing and framing matter as much as the data itself. Bring your percentile result to annual reviews, not mid-cycle. Lead with your contributions, then use the data to justify the number: “Based on my impact over the past year and BLS benchmarks for this role in our market, I’m targeting $X — which would put me at the Nth percentile nationally.” If your employer pushes back, ask what percentile they’re targeting for the role; that question alone often reveals how far apart you actually are.

After the Negotiation

Track the outcome. If you got a raise, note what moved the needle — data, timing, or framing. If you didn’t, document your current percentile and set a 6-month reminder to revisit. Most salary increases come through sustained, documented conversations rather than one-time asks. Your percentile is a living number; recalculate it after every major BLS data release (published annually in the fall) to stay current on where you stand.