Job Market Insights - Salary, Remote % and Skills Data

Describe a slice of the job market and get the numbers behind it in one row: salary percentiles, the share of roles that are remote, the technologies and skills employers actually ask for, the experience mix, and who is hiring most. Computed over live listings scraped straight from company career pages by Hirebase.

Job scrapers answer which jobs. This one answers what the market looks like - without paying for a single job row.

Why this actor?

• 📊 A whole cohort in one row - filter the way you would a job search, get one row of aggregates back.
• 💰 Real salary distribution - p25 / median / p75 / p90, the average, the full histogram, and the share of postings that disclose pay at all.
• 🏠 Remote mix - the remote / hybrid / in-person split, with salary broken out by each.
• 🛠 Skills and tech that count - the top technologies, skills and benefits with the share of postings asking for each.
• 🏢 Company scope - point it at company slugs instead, and compare employers side by side, one row each.
• 💸 Billed per query, not per job - a cohort of 250,000 jobs costs the same as one of 250.

How to use it

1. Leave Scope on Whole market and describe the cohort with the filters: job titles, keywords, locations, workplace type, industry, seniority, posted-within, and so on.
2. Or set Scope to One company at a time and paste company slugs - each gets its own row. The cohort filters still apply on top, so you can ask "what does Stripe's remote engineering hiring look like".
3. Run. Every row is one query.

Example input

{
  "scope": "market",
  "jobTitles": ["Data Scientist"],
  "locationTypes": ["Remote"],
  "postedWithinDays": 30
}

Output

One row per query. Real figures from the example above:

{
  "label": "Data Scientist | Remote",
  "scope": "market",
  "totalJobs": 258,
  "medianSalary": 136000,
  "salaryCurrency": "USD",
  "pctDisclosingSalary": 63.95,
  "pctRemote": 100,
  "topCompany": "Booz Allen Hamilton",
  "topTechnology": "Python",
  "dominantExperienceLevel": "Senior",
  "newThisWeek": 64,
  "visaSponsorshipRate": 12.79,
  "recruiterAgencyRate": 5.04,
  "yoeMedian": 5,
  "topTechnologiesText": "Python 82%, SQL 53%, R 22%, AWS 19%, Tableau 14%",
  "topSkillsText": "Machine learning 49%, data science 39%, Data analysis 16%",
  "salaryP25": 113676.25,
  "salaryP50": 136000,
  "salaryP75": 168520,
  "salaryP90": 191460,
  "salaryCount": 143
}

The same row also carries the full breakdowns as nested arrays: salaryHistogram, salaryByLevel, salaryByLocationType, levelBreakdown, locationTypeSplit, jobTypeSplit, educationSplit, companySizeSplit, industrySplit, subindustrySplit, topTechnologies, topSkills, topBenefits, topCompanies, topLocations, freshness, scores and scoresByLevel - each with counts and percentages. Export to JSON, CSV or Excel, or pipe into Sheets, Make, n8n or a BI tool.

The ...Text columns are the top five of a section as plain text, so the run's table is readable at a glance. Hirebase tags skills case-sensitively, so those summaries merge "Machine learning" and "machine learning"; the nested arrays keep the raw values.

Great for

• Compensation benchmarking - what a role pays now, by seniority and by workplace type, in any market you can describe.
• Talent and workforce planning - where hiring is concentrated, which employers dominate a niche, how much of it is remote.
• Recruiters pitching clients - hard numbers for "this is what that role costs in this market".
• Market research and content - salary and skills reports that refresh on a schedule.
• Tracking employers over time - company scope on a daily or weekly schedule builds a time series of one company's hiring.

Pricing

Billed per query, not per job. One row = one query = one charge, whether the cohort holds 250 jobs or 250,000. Company scope runs one query per slug, so five slugs is five charges. Cohorts that match no jobs are not saved and not charged - which is what happens when a company slug is wrong, so check the slug if a row is missing.

Max queries caps how many queries a run can make, so it doubles as a spending cap.

FAQ

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

Where do I get company slugs? From the companySlug column of Company Search or any Hirebase job actor. It's the lower-case identifier (stripe), not the company name.

Why is the median salary based on fewer jobs than the cohort? Only some postings disclose pay. pctDisclosingSalary tells you what share did, and salaryCount how many that was - the percentiles are computed over those.

How fresh are the numbers? They're computed over the live index when you run it, and generatedAt records when. Repeat queries may be served from Hirebase's cache (cached: true).

Can I get the individual jobs behind these numbers? Yes - put the same filters into Job Search and it returns the postings themselves.

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.