Frequently Asked Questions
What is JobSearcher?
JobSearcher is a data platform that aggregates, deduplicates, and normalizes job listings from thousands of sources across the web into a single searchable archive. Unlike traditional job boards that host employer-submitted posts, JobSearcher crawls the open web continuously to build a canonical record of every identifiable job opening — past and present.
How is JobSearcher different from Indeed or LinkedIn Jobs?
Indeed and LinkedIn are job boards designed for applicants to find and apply to roles. JobSearcher is a data infrastructure layer: it collects listings from those platforms and thousands of others, removes duplicates, and structures every posting with standardized occupation codes, industry codes, and location data. Job seekers can use JobSearcher to search across all sources at once, while developers and researchers use the API to access structured labor market data at scale.
What is a canonical job identifier?
A single job opening often appears on dozens of websites simultaneously — the employer's careers page, LinkedIn, Indeed, Glassdoor, and various aggregators — each with slightly different titles, descriptions, and formatting. JobSearcher assigns each unique role a canonical identifier that persists regardless of where the listing appears, making it possible to track a role across sources and over time without counting it multiple times.
What taxonomies does JobSearcher use for job classification?
Every listing is tagged with two federal classification systems. Occupations are mapped to O*NET-SOC codes maintained by the U.S. Department of Labor, which define roughly 1,000 detailed occupational categories. Industries are mapped to NAICS codes published by the U.S. Census Bureau, covering over 1,000 industry sectors. These standardized codes make it possible to compare hiring trends across companies, regions, and time periods using a common language.
How often is job data updated?
JobSearcher crawls thousands of sources continuously, with most active listings refreshed within 24 hours. New postings are typically ingested, deduplicated, and normalized within hours of first appearing on a source site. Historical listings remain in the archive indefinitely with full version history, so users can see when a role was first posted, when its details changed, and when it was removed.
Who is JobSearcher built for?
JobSearcher serves two audiences. Job seekers use the search interface to find openings across every major job board and employer site in one place. Developers, researchers, and businesses use the REST API to access structured job data programmatically — for workforce analytics, labor market research, competitive intelligence, hiring trend analysis, or building applications on top of real-time employment data.
What does the JobSearcher API offer?
The API provides programmatic access to millions of structured job listings through a standard REST interface. It supports full-text search, filtering by O*NET occupation and NAICS industry codes, geographic queries, and historical lookups. Three tiers are available: a free tier for developers and researchers, a Pro tier with higher rate limits and historical data access, and a Bulk tier for complete data exports and streaming updates.
How does JobSearcher handle duplicate listings?
When the same role appears on multiple websites, each version may have a different title, salary range, or description. JobSearcher's deduplication pipeline compares signals like employer name, location, posting date, and description similarity to determine when multiple listings refer to the same underlying position. Matched listings are merged under a single canonical identifier, with each source version preserved so users can see the complete picture.