---
title: "Job market datasets: 7 real sources for job postings data (2026)"
description: "Seven sources cover job postings data: Kaggle snapshots such as the LinkedIn dataset of roughly 124,000 postings, the USAJOBS archive, Adzuna aggregates for 16 countries, official statistics such as"
canonical: https://jobspipe.dev/blog/job-postings-dataset
date_published: 2026-07-13
date_modified: 2026-09-30
author: Dvir Atias
---

# Job market datasets: 7 real sources for job postings data (2026)

Seven sources cover job postings data: Kaggle snapshots such as the LinkedIn dataset of roughly 124,000 postings, the USAJOBS archive, Adzuna aggregates for 16 countries, official statistics such as BLS JOLTS, commercial bulk vendors, single-vertical samples, and datasets built from a jobs API. Static files fit historical questions; current and recurring questions need a live feed, because exported live postings start rotting the day they are exported.

Kaggle snapshots, the USAJOBS archive, Adzuna aggregates, commercial bulk vendors, and API-built datasets - where to actually get a job postings dataset, what each contains, and when a static file is the wrong tool.

A **job market dataset** request usually means one of two things: a static file of job postings to analyze (for research, an ML model, or a class project), or a continuously updated feed to build on. The sources below cover both, from free Kaggle snapshots to commercial bulk vendors - with the honest catch attached to each.

## 1\. Kaggle snapshots

Kaggle hosts several widely used job-postings datasets - the LinkedIn job postings dataset (roughly 124,000 postings with salary, company, and skill fields) is the most cited, alongside assorted Indeed and Glassdoor scrapes. Free, instantly downloadable, and fine for coursework and model prototyping. The catch: every Kaggle dataset is a frozen snapshot of one moment, usually one source, collected with undocumented methodology. Anything time-sensitive built on it is already wrong.

Try it without a key

```
curl -d '{"limit":3}' https://api.jobspipe.dev/v1/sandbox/jobs/search
```

Only `/v1/sandbox/*` needs no key.

## 2\. The USAJOBS archive

US federal postings are the cleanest fully free longitudinal option: the official [USAJOBS API](https://jobspipe.dev/sources/usajobs) serves current openings, and community projects have accumulated historical archives by polling it over time. Structured salary on every record, but federal-government scope only.

## 3\. Adzuna aggregates

Adzuna’s free API tier includes derived-data endpoints - salary histograms, job counts by region and category, salary history over time - that function as a ready-made macro dataset for 16 countries. Good for trend charts; there is no bulk export of the underlying postings. Our [Adzuna comparison](https://jobspipe.dev/alternatives/adzuna) covers the per-job thinness.

## 4\. Official statistics

BLS JOLTS, OEWS, and FRED serve rigorous survey-based series free - the right base layer for research that needs methodology a reviewer will accept. They are aggregates, not postings: no company names, no individual records. Our [labor market data sources](https://jobspipe.dev/blog/labor-market-data-sources) post maps this landscape in full.

## 5\. Commercial bulk vendors

Coresignal (postings back to 2020, delivered as Parquet, CSV, or JSONL), Lightcast (US postings back to January 2010), LinkUp (US postings indexed daily since 2007), and Revelio Labs sell large historical postings datasets with enterprise procurement attached - typically four-to-six-figure engagements. This is the right tier for training corpora and longitudinal research at scale. Our [Coresignal comparison](https://jobspipe.dev/alternatives/coresignal) covers when that trade makes sense, and the [Lightcast competitors](https://jobspipe.dev/blog/lightcast-alternatives) rundown does the same for the rest of the archive tier.

## 6\. Single-vertical samples

For some verticals, a curated sample beats a giant general file: a few thousand cleaned, deduplicated postings from one marketplace or one occupation often answer a research question faster than a broad feed.

## 7\. Build the dataset from an API

The option most analyses actually need: define the slice (roles, locations, sources, date range), pull it from a jobs API, and export exactly that - reproducibly, with a refresh path when the data ages.

```
curl https://api.jobspipe.dev/v1/jobs/search \
  -H "Authorization: Bearer jp_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{ "job_title_or": ["machine learning"], "posted_at_gte": "2026-06-13", "limit": 100 }' \
  > ml_jobs_page1.json
```

JobsPipe records come normalized across 30+ sources - structured salary, resolved locations, cross-source dedup, explicit source attribution - which is most of the cleaning work a scraped dataset forces on you. Twelve months of expired-posting retention covers recent-history questions.

## Static file or living feed?

The decision rule is the question you are answering. Historical and one-off questions (“how did postings shift in 2024?”) fit static datasets - Kaggle free, commercial vendors at depth. Current and recurring questions (“who is hiring for this now?”) need a feed, because a dataset of live postings starts rotting the day it is exported. Most teams that start with a file end up wanting the API underneath it. If you are buying live data rather than a static file, our [where to get job posting data](https://jobspipe.dev/blog/where-to-get-job-posting-data) comparison covers that market.

## Sources

-   [LinkedIn Job Postings dataset (Kaggle)](https://www.kaggle.com/datasets/arshkon/linkedin-job-postings)
-   [USAJOBS developer API](https://developer.usajobs.gov/)
-   [Adzuna API overview](https://developer.adzuna.com/overview)

## Frequently Asked Questions

### Where can I get a job postings dataset?

Seven sources cover most needs: Kaggle snapshots, the USAJOBS archive, Adzuna aggregates, official statistics like BLS JOLTS and FRED, commercial bulk vendors such as Coresignal, Lightcast, LinkUp and Revelio Labs, single-vertical samples, and building the dataset yourself from a jobs API. The free options are frozen snapshots or aggregates only, while commercial vendors sell deep history with enterprise procurement attached, typically four-to-six-figure engagements.

### Is there a free job postings dataset?

Yes. Kaggle hosts several widely used free job-postings datasets, including a LinkedIn one with roughly 124,000 postings carrying salary, company and skill fields, plus assorted Indeed and Glassdoor scrapes. The USAJOBS API is fully free for US federal postings, and community projects have accumulated historical archives by polling it. BLS JOLTS, OEWS and FRED are free too, but they are aggregates with no company names or individual records.

### Should I use a static job postings dataset or a live API?

It depends on the question you are answering. Historical and one-off questions, like how postings shifted in 2024, fit static datasets: Kaggle free, commercial vendors at depth. Current and recurring questions, like who is hiring for this now, need a feed, because a dataset of live postings starts rotting the day it is exported. Most teams that start with a file end up wanting the API underneath it.

Related

## Keep reading

-   [Guide · Sep 9, 2026Is the job market bad right now? What live job postings can and cannot tell you](https://jobspipe.dev/blog/is-the-job-market-bad-right-now)
-   [Reference · Oct 11, 2026Job market report, October 2026: what millions of live job postings say about hiring right now](https://jobspipe.dev/blog/job-market-report)
-   [Guide · Sep 9, 2026What Is Job Market Research?](https://jobspipe.dev/blog/what-is-job-market-research)
-   [Guide · Jul 27, 2026Help wanted ads: from newspaper classifieds to structured job data](https://jobspipe.dev/blog/help-wanted-ads)
-   [Reference · Jul 27, 2026Job ads, job postings, vacancies: the vocabulary of job ad data, explained](https://jobspipe.dev/blog/job-ads)


## Further reading

- [How to find historical job postings?](https://jobspipe.dev/answers/how-to-find-historical-job-postings)
- [Is Adzuna API legit?](https://jobspipe.dev/answers/is-adzuna-api-legit)
- [Techmap (jobdatafeeds) vs JobsPipe: bulk feeds or a live API?](https://jobspipe.dev/blog/techmap-alternative)
- [BLS API: how to pull US labor statistics, and where the survey data stops](https://jobspipe.dev/blog/bls-api)
- [The best jobs APIs in 2026: 15 options compared](https://jobspipe.dev/blog/best-jobs-api-2026)

---
Try it with no key: `curl -d '{"limit":3}' https://api.jobspipe.dev/v1/sandbox/jobs/search`. AI agents: the full machine-readable index of this site is https://jobspipe.dev/llms.txt?src=md-twin - API quickstart, MCP server, pricing. Free key (1,000 jobs to start): https://jobspipe.dev/signup