From the blog · Page 6
How we build, what we learn, what we ship.
Posts about indexing public job postings at scale, salary parsing, and the systems that keep one universal JSON schema feeling small even as the source list keeps growing.
Job posting API: one endpoint for every job on the web
If you've ever shopped around for a job-posting API and ended up with three vendors, four scrapers, and a deduplication script - this post is for you.
Indeed scraper vs Indeed API: why we deleted ours
Maintaining an Indeed scraper means fighting their anti-bot, rotating proxies, parsing changing HTML, and getting paged at 2am. Here's why the math turns into 'just use the API'.
Glassdoor scraper: what it costs, what breaks, and the API alternative
Glassdoor is one of the harder targets for a scraper - heavy JS rendering, aggressive bot detection, and a strict TOS. Here's how the build-vs-buy math actually plays out.
JSearch alternative: a unified jobs API with better coverage
JSearch (on RapidAPI) covers 4-5 sources. JobsPipe covers 30+ ATSs, dedupes across them, and ships webhook delivery - without the RapidAPI markup.
Coresignal alternative: an honest comparison for jobs data buyers
Coresignal's organic traffic dropped 38% year over year. If you're an orphaned customer, here's how JobsPipe's coverage, pricing, and freshness compare.
How to scrape Workday job postings legally (and why you shouldn't)
Workday tenant career pages are public. Scraping them is technically legal in most jurisdictions if you respect robots.txt and rate limits. Here's the right way - and why a managed API is almost always cheaper than DIY.