An illustrative view of how job listing, employer, role a…
.
Data Marketplace · Jobs & talent
Compare public Indeed listings by role, employer, location, compensation context, description, and posting history.
.
{
"listing_id": "illustrative-indeed-84",
"title": "Product Analyst",
"employer": "Example Retail",
"location": {
"country": "US",
"region": "CA"
},
"compensation": {
"min": 90000,
"max": 115000,
"period": "year"
},
"captured_at": "2026-08-07T…Schema and fields
Start with job listing, employer, role. Source identity, collection time, and field meaning stay connected so records can move into analysis without losing their context.
listing_id stringSource listing identity
title stringDisplayed role title
employer stringDisplayed employer
location objectDisplayed job location
compensation objectDisplayed pay context where present
description stringPublic listing description
listing_url urlPublic source URL
captured_at timestampCollection time
Records in this collection
Explore the Indeed on-demand API
Job listing
Employer
Role
Compensation observation
Posting event
Freshness and delivery
Define how frequently the selected query and market scope should be re-observed and how listing state changes appear in delivery.
Snapshot Start from a dated baseline Selected scope and collection window
Refresh Receive recurring updates Cadence and change behavior
Format Use JSON, CSV, or Parquet Schema, partitioning, and manifest
Validation Run repeatable checks Counts, fields, missing states, and version
Indeed applications
Use source-linked, time-stamped records for role and location demand, plus compensation research. Each application starts from the same documented fields and collection context.
01
Compare public listing patterns across markets, employers, and job families.
02
Study displayed salary or pay context while preserving currency, period, location, and source.
03
Distinguish first observed, changed, still observed, and no-longer-observed listing states.
From sample to production
Start with representative rows, run the joins and calculations that matter, and shape delivery around the system that will consume the data.
01
Select the entities, markets, fields, dates, and business output the collection should support.
02
Check identifiers, fields, joins, missing states, and source context with your own queries or models.
03
Choose the snapshot or recurring schedule, file format, partitions, manifest, and destination.
Indeed dataset FAQ
Compare public Indeed listings by role, employer, location, compensation context, description, and posting history. Core records include job listing, employer, role, compensation observation, posting event.
Common applications include role and location demand, compensation research, posting lifecycle analysis. Start with the fields and time window required by the business output.
Define how frequently the selected query and market scope should be re-observed and how listing state changes appear in delivery.
Use the on-demand API when your application chooses individual requests and timing. Choose this dataset for a prepared bulk snapshot or recurring file delivery.
Continue the data journey
Compare the adjacent dataset, open the source API, or continue into the relevant data, industry, and solution pages.
Start with real records
Tell us which job listing and employer data you need, plus the markets, fields, dates, and destination. We will map the collection to that requirement.