> For the complete documentation index, see [llms.txt](https://docs.coresignal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coresignal.com/jobs-data/overview.md).
# Multi-source Jobs Data Overview
Deduplicated, fresh job postings from multiple sources delivered daily to quarterly. Built for investment research, HR tech, and sales intelligence.
Jobs Data is designed to be used for **investment, market research, HR tech, and** **sales tech**.
| **Job boards and aggregators** | Jobs data helps identify the best-in-class listings with high-coverage data from job boards, company career pages, and ATS globally. |
| ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Used by employers, RPOs, and consultancies** | Explore labor market trends, and make competitive monitoring or sourcing easier. |
| **Extract sales intent** | Jobs data, extracting sales intent becomes even more convenient. |
| **Deduplicated job feed** | Eliminated clutter and confusion by ensuring each job posting appears just once. Records that refer to the same entity across multiple sources are identified and merged into a unified job record. |
| **Fresh and historical data** | Continuous 24/7 discovery of job postings. It includes refreshing active job postings as well as expired listings. |
***
## Summary
| Feature | Details |
| ------------------ | ------------------------------------ |
| Available via | Flat files and API |
| Delivery frequency | Daily, weekly, monthly and quarterly |
| Available formats | Parquet, JSONL |
| Scraping since | 2025-05 |
## Related links
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.coresignal.com/jobs-data/overview.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.