A free, hosted job listings API with 1.8M+ listings across 60k companies. Get comprehensive active and historical job data from 30+ applicant tracking systems, with companies spanning industries and stages.
The normalization layer is where I'd want to understand the depth of work done. Thirty-plus ATSs means thirty-plus ways to express job title, seniority, and employment type — and raw aggregation without opinionated normalization just moves the cleanup problem to whoever's consuming the API. How standardized are fields like seniority level or work location across sources, or is that still left to the builder?
About Job Postings API on Product Hunt
“View, monitor, and analyze 1.8M+ US jobs”
Job Postings API launched on Product Hunt on June 7th, 2026 and earned 145 upvotes and 4 comments, placing #4 on the daily leaderboard. A free, hosted job listings API with 1.8M+ listings across 60k companies. Get comprehensive active and historical job data from 30+ applicant tracking systems, with companies spanning industries and stages.
On the analytics side, Job Postings API competes within API, Artificial Intelligence and Data — topics that collectively have 570.9k followers on Product Hunt. The dashboard above tracks how Job Postings API performed against the three products that launched closest to it on the same day.
Who hunted Job Postings API?
Job Postings API was hunted by Sam Crombie. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Job Postings API including community comment highlights and product details, visit the product overview.
Sam Crombie
The normalization layer is where I'd want to understand the depth of work done. Thirty-plus ATSs means thirty-plus ways to express job title, seniority, and employment type — and raw aggregation without opinionated normalization just moves the cleanup problem to whoever's consuming the API. How standardized are fields like seniority level or work location across sources, or is that still left to the builder?