Salary Benchmarking
Price one role from a job URL or a few fields. Live plus 90-day expired posted pay, with listing rows.
Open benchmarkingDatasets · Active & Historical
Salary & labor market data API
Salary distributions, hiring velocity, and skills demand for any slice of the market — in a single API call.
Hirebase computes live compensation, workforce, and hiring analytics over 3.5m+ jobs indexed directly from 240k+ company career pages — not scraped from aggregators. Define a cohort with the filters you already use, and get back salary percentiles, remote mix, top technologies, and company breakdowns.
240k+ companies
Same filters as Search
p25–p90 salary distributions
Hiring velocity & skills
Average Salary
$99kmedian total pay
$140k$350k
2.5kOpen positions
Hiring Velocity
JanFebMarAprMayJunJulAugSepOctNovDec
Indexed: Senior Software Engineer @ Absolute Business Solutions
Indexed: Senior IT Infrastructure Engineer @ Tsmc
Indexed: Director, Data & Storage Reliability Engineering @ ServiceNow
Indexed: Principal Technical Lead, Software Engineering (Network and Security)-North America Software Center @ Tsmc
Indexed: Senior Systems Engineer @ Knorr-Bremse Group
Indexed: Cybersecurity Engineer - IAM @ Lululemoninc
Indexed: Senior Project Manager/Leader @ Source Code
Indexed: Product Designer @ Qantas
Indexed: Director, Global Space & Occupancy Planning @ Jobgether
Indexed: Senior Piping Designer @ Worley
The Problem
Labor-market analytics shouldn’t wait on a survey
Product, research, and compensation teams need salary distributions and hiring signals for any slice of the market — not a PDF of last year’s averages.
Today
Export jobs, parse salaries, drop duplicates, hope the filters match Search. Repeat next quarter.
With Insights
One POST with the Search filter shape. Percentiles, hiring velocity, skills, and workforce mix come back together.
Static snapshots
Survey salary files age the day they ship. Hiring velocity, remote mix, and skills demand have already moved.
No cohort language
You can filter a job search, then you rebuild the same filters in a BI tool to get a median. Two query models, two answers.
Aggregator inflation
Counts and pay distributions inherit duplicates, agency spam, and closed roles. The market looks larger and cheaper than it is.
Averages without a histogram
A single median salary hides seniority mix, disclosure rate, and the p90 tail you need for competitive offers.
What you getOne POST request.
One POST request.
Full analytics profile.
Define any cohort — a job title, industry, location, company, or combination — and get back a complete market snapshot.
Distribution
$148k p50
p25p50p75p90
$80k$120k$160k$220k
Salary data, fully distributed
Not just an average. Get p25 p50 p75 p90, a salary histogram, a fitted distribution, and breakdowns by seniority and by remote hybrid on-site plus the share of roles actually disclosing pay.
New postings / week
+18.4%
Live · 2h
W1
W2
W3
W4
W5
W6
W7
W8
Hiring velocity & freshness
See how fast a cohort is moving: new-this-week counts, recency filters, and freshness so you track hiring trends instead of a static snapshot.
Top skills in cohort
Demand share
Python4.2k
React3.6k
AWS2.9k
Kubernetes2.1k
Go1.6k
Skills & technology demand
Top technologies and skills in the same postings as the pay band — so compensation, talent, and product teams see what the market is actually asking for.
Remote42%
Remote42%
Hybrid35%
On-site23%
Seniority mix
Junior18%
Mid34%
Senior32%
Staff+16%
Workforce composition.
Seniority mix, work-arrangement split, company-size distribution, industry and subindustry breakdowns, education requirements, median years of experience, visa-sponsorship rate, and recruiter-agency rate.
S
Stripe
Open roles · 12 mo
JanAprJulOctDec
Company-level tracking.
Scope every metric above to a single employer and watch their compensation, remote mix, and tech stack shift over time.
How it works
Same filter shape as Search
You already know the filter shape — Insights uses the same one as Search.
[ 01 ]
Define a cohort
Pass filters like job titles, keywords, geo locations, location types, industry, and days ago.
[ 02 ]
Call the endpoint
POST v2 jobs insights for any market cohort, or POST v2 hirebase companies slug insights to scope to one company.
[ 03 ]
Get aggregates back
Salary distributions, hiring velocity, tech and skills demand, and the full breakdown ready to drop into a dashboard, a model, or your product.
200 OK
Salary research
What is a salary data API?
A salary data API returns compensation figures programmatically instead of through a report or spreadsheet. Hirebase Insights goes further than a single number: it returns full salary distributions — percentiles, a histogram, seniority and work- arrangement splits — plus hiring velocity, skills demand, and workforce mix for any cohort you can describe.
The filter shape is the same as Search. Pass titles, locations, remote vs on-site, industry, company, or recency, and POST /v2/jobs/insights computes aggregates over first-party career-page jobs — not aggregator copies.
Use Insights when you need analytics for an arbitrary slice of the market. Use Salary Benchmarking when you need an occupational-area report for one role: title expansion, live plus 90-day expired jobs, and listing-level audit rows.
Salary vs compensation: this API reports disclosed base-pay ranges on postings (annual USD midpoints in the distribution). It is not an equity grant database. Pair the cash band with your own total-rewards model when you need the full package.
Built For
Power any workflow that needs live market data
Labor market & economic research
Use job postings as alt-data: track hiring trends, skills shifts, and remote adoption across industries and geographies.
Market & competitive intelligence
Monitor a single company's hiring, compensation, and tech-stack changes over time.
Compensation benchmarking
Build defensible pay bands by role, level, and location — or power a compensation tool — on live market data instead of stale annual surveys.
Talent & workforce analytics
Feed real-time hiring and skills signals into HR dashboards and people-analytics products.
Product features
Embed salary ranges, 'X new roles this week,' or top-skills widgets directly in your own application.
Why Hirebase
First-party data, built for developers.
[ 01 ]
Sourced at the source
Data comes directly from 240k+ company career pages across every major applicant tracking system — not resold from LinkedIn or Indeed. You get first-party postings, not an aggregator's stale copy.
Indexed at the source
Not from aggregators
[ 02 ]
Fresh, and kept fresh.
Postings are refreshed continuously and expired roles are pruned, so your aggregates reflect what's actually open right now — not roles that closed weeks ago.
Live index
Updated 2 min ago
Staff Engineer
Stripe
ML Engineer
Anthropic
Product Designer
Linear
Data Scientist
Notion
[ 03 ]
Normalized and ready.
Salaries are normalized, titles and locations are cleaned, and everything returns in one consistent schema.
Raw
$100k
100,000 USD
100k/yr
SF Bay Area / Remote
→
normalized.json
{
"salary_min": 100000,
"salary_max": 100000,
"currency": "USD",
"location": "San Francisco, CA",
"remote": true
}
[ 04 ]
One filter language
If you can describe a cohort in Search, you can get analytics for it. No new query model to learn.
Shared filter object
{
"job_titles": ["Data Scientist"],
"location_types": ["Remote"],
"days_ago": 30
}
SearchPOST /v2/jobs/search
InsightsPOST /v2/jobs/insights
Same filters · two endpoints
Why The Switch
Aggregator analytics inherit aggregator noise.
If the jobs underneath are duplicates and stale listings, the salary distribution is already wrong. Insights runs on first-party postings.
Survey & aggregator files Vs
Hirebase
01Data source
Job-board scrapes and recycled aggregator feeds
Direct from 240k+ company career pages and ATS platforms
02Query model
A separate analytics schema, or a CSV you have to roll up
The same filter shape as Search — titles, geo, seniority, recency
03Salary output
A mean or midpoint with no histogram or disclosure rate
p25 / p50 / p75 / p90, histogram, seniority and remote splits
04Market context
Pay in one file, hiring trends in another, skills nowhere
Salary, hiring velocity, technologies, and workforce mix in one payload
05Company view
Manual tracking of one employer’s postings over time
The same analytics scoped to a company slug
Keep exploring
Related salary research
Go from a market cohort to a single-role benchmark, the jobs corpus, and public salary rankings.
Jobs API
Query the same first-party listings Insights aggregates — titles, locations, salaries, and 50+ fields.
Jobs data APIHighest paying roles
Public ranking of titles with the highest disclosed pay in the Hirebase corpus.
View the rankingSalary leaders by location
See which markets lead on posted pay when you are setting geographic differentials.
Browse locationsLabor market insights
Hiring trends, fastest-growing roles, and other public cuts powered by the same data.
Insights hubAPI documentation
Filter shape, Insights payload, and authentication. Same language as Search.
Read the docsFAQ
Common Questions
Get StartedStart pulling market analytics today
Start pulling market analytics today
Get a key and make your first Insights call in minutes.
