Salary Benchmark - Pay Percentiles for Any Role

Enter a role and a city, state or country, and get what the market actually pays: annual salary percentiles from p5 to p95 in the local currency, the number of postings behind them, and - if you give it one - where your proposed pay range sits. Built on posted salaries from live job listings, scraped straight from company career pages by Hirebase.

Why this actor?

• 🎯 Where does my range sit? Put in a proposed range and get its percentile, its distance from p25, the median and p75, and a plain verdict.
• 📏 Sample size on every answer - you always see how many postings a number is built on, with a confidence grade and the reasons behind it.
• ⏱ Hourly roles included - hourly, daily, weekly and monthly pay is converted to annual, so nurses, warehouse staff and technicians are benchmarked on their whole market.
• 🌍 Any country - pay comes back in the benchmark country's currency (US in USD, UK in GBP).
• 🗺 Compare markets - list several locations and get one row each.
• 💸 Billed per query, not per posting - and never for a location with too little data to answer.

How to use it

1. Enter the Job title (add Similar titles to widen the comparison), or paste a public job posting URL instead.
2. List one or more Locations: Austin, Texas, United States, Texas, United States, United States or London, England, United Kingdom.
3. Optionally narrow by experience level, years of experience, workplace type, industry or sub-industry, and turn on Live postings only to leave out postings that have closed.
4. Optionally enter a proposed range in the location's currency, and whether it's per year, month, day or hour.
5. Run. Each location is one query and one row; a report takes about a minute.

Example input

{
  "jobTitle": "Senior Software Engineer",
  "locations": ["Austin, Texas, United States"],
  "proposedMin": 160000,
  "proposedMax": 190000,
  "proposedPeriod": "yearly"
}

Output

One row per role and location. Real figures for the example above:

{
  "label": "Senior Software Engineer | Austin, Texas, United States",
  "currency": "USD",
  "period": "yearly",
  "sampleSize": 841,
  "p5": 113147.5,
  "p25": 143000,
  "median": 170950,
  "p75": 202550,
  "p90": 235750,
  "p95": 256000,
  "proposedAnnualMid": 175000,
  "proposedPercentile": 54.1,
  "proposedVerdict": "competitive",
  "proposedVsMedian": 4050,
  "confidence": "high",
  "confidenceNote": "High — defensible for a posted-range decision",
  "postingsFound": 1149,
  "livePostings": 347,
  "expiredPostings": 494,
  "pctDisclosingSalary": 73.2
}

Each row also has the percentiles by experience level, by workplace type, by location and by company size, the titles compared, and any fallbacks - where the search had to be widened because the request was too narrow (a city widened to its state, or fewer years of experience). The full report, including the salary histograms, is saved to the run's key-value store.

How the numbers are built

The percentiles come from posted pay ranges (the midpoint of each), not accepted offers, bonuses, equity or survey data. Hirebase annualizes hourly (x 2,080), daily (x 260), weekly (x 52) and monthly (x 12) pay, and leaves out pay in other currencies, pay that is ambiguous or implausible, and duplicate postings (same employer, title and range).

By default the sample includes postings that closed within the time window - still what the market paid recently, and a bigger sample. Turn on Live postings only to compare against open postings alone.

confidence is high, medium or low, with confidenceReasons saying what holds it back - usually a thin sample, or a search that had to be widened. Treat low as directional.

Great for

• Setting a posted range - check a new requisition's range before it goes live, especially where pay-transparency laws apply.
• Recruiters and agencies - "this is what the role pays in this market", with the sample size to back it.
• Job seekers - know whether an offer is below, within or above market.
• Comp and people teams - compare the same role across cities and countries in one run.

Pricing

Billed per query: one row = one role in one location = one charge. A run over three locations is three charges. A location with fewer than 8 postings with pay is not saved and not charged - there's nothing reliable to report. Max queries caps a run, so it doubles as a spending limit.

FAQ

Do I need an API key? No - API access is built into the actor.

Which countries are covered? Any country with enough postings that state pay. Figures are in that country's currency, and the proposed range is read in it too. When you list locations in different countries, the same proposed range is read in each one's currency - run them separately if you mean one fixed amount.

Why is the sample smaller than the postings found? Only postings that state pay can be counted - pctDisclosingSalary shows the share - and a few are left out as ambiguous or duplicate.

Is this legal? The data comes from publicly posted job listings on company career pages, accessed via the Hirebase API, and is reported only in aggregate.