Freshness

How often we scrape

We use different scraping frequencies based on the source and volume of job postings:

• Every 10 minutes: High-volume job boards and frequently updated company career pages
• Every hour: Medium-traffic job sources with regular updates
• Daily: Smaller job boards and company websites with lower posting frequency

How fast we discover jobs

Within 48 hours, we capture approximately 98% of all new job postings across our monitored sources. Here's the full breakdown:

Because discovery continues over subsequent days, job counts for today may appear lower than final numbers. You'll see the most comprehensive data after about 2-3 days.

Why some jobs are discovered later

A small percentage of jobs have a gap between their posted_at date and their discovered_at date. This is caused by delays in the chain between the company and us:

• ATSs sync delay with job boards: The ATS that a company uses lets them sync jobs with a major job board, but the recruiter can choose which jobs to push to that job board because they charge for it. They may not initially sync it and do it after a few days to try to get more candidates. But the integration may keep the original date when the job was posted first, and show that in the final job board, instead of the date when the job was pushed. In this case, there will be a gap of a few days.

• Job board scraping delay: A job board scrapes company career pages periodically, running daily. If a company posts a job at 14h and the job board scraper visits it at 10h every day, that job won't be available in the job board until the day after. For companies that post many positions, it makes sense for job boards to visit those career pages with a high frequency. But visiting every career page of every company in the world periodically has a cost, so for smaller companies that very occasionally post jobs, doing it on a weekly basis could help those job boards save money. So imagine they visit one of these companies' career site every Monday. If they post a job on Tuesday, they won't visit it again until next Monday, so there will be a 6-day difference between posted_at and discovered_at

• Job board publishing delay: If someone publishes a job directly on a job board we scrape, this job board may also let them set a custom posted_at that is days before the current date. But the job is not available at that job board until the very moment when that person publishes it there, and even if the reported posted_at is previous to that, that job wouldn't have been discovered before because that person hadn't published it in that job board yet.

Why old jobs appear as recently posted

You might see jobs with older original posting dates appearing in recent results. This happens because companies often repost the same job on platforms like LinkedIn or other job boards.

Here's what's happening:

When a company reposts a job, they're essentially re-advertising the same position. This is common when:

• They're still hiring for the same role after filling a previous opening
• They want to refresh visibility for an ongoing search
• They're expanding the team and need multiple people for the same position

The job URL on LinkedIn or other job boards stays the same, but the posting date updates to reflect when it was reposted. Since the company is actively promoting it (and often paying to boost visibility), we treat it as a current, active opportunity.

So if you filter for jobs posted on a specific date, you'll see both:

• Brand new job postings
• Previously posted jobs that were reposted on that date, as long as the original posting date is not the last 30 days. If it is, we will discard it as we'll consider it a duplicate. More info on deduplication here.

This ensures you don't miss out on legitimate opportunities that companies are actively trying to fill, even if the original posting was weeks or months earlier.