Skip to the content

DatasetsIn development

The data, not the scraping.

EnrichedNow Datasets is for teams who want web data delivered, without running or watching a scraper. The first dataset is job openings: company records, and each company’s job postings with their history. It is in development and is not available to buy yet.

The button opens an email to us. There is no form and no waiting list.

The first dataset

In development

Job openings

Company records keyed by website domain, and under each company its job postings: when each was first seen, when it was last seen, and when it was found closed.

A scrape tells you what a site lists today. The dataset keeps what was read before, so it can also say when an opening appeared, how it changed and when it went away. A value the source does not give is null, never an empty string, a zero or a guess.

Company records
One record per company, keyed by its website domain, so the data joins to your own company list.
Job postings
Each posting with a stable id, the company it belongs to, and where it was read.
First and last seen
When we first saw a posting and when we last saw it, as times of reading, not of loading.
A closed signal
A posting is marked closed when complete reads of its source stop listing it. A read that failed closes nothing.
History
Every sighting, every field that changed with its old and new value, and each closing and reopening.
Delivery
By API and files. Details at early access.

The company record

One record per company. Its key is the company's website domain.

  • The key

    The website domain, the name last seen for the company, and every name seen for it.

    • domain
    • name
    • names
  • Where it hires

    The careers page and the applicant tracking system behind it, when they are known.

    • careers_url
    • ats
  • When we looked

    When the company was first and last seen, and how the latest read went, so that no openings can be told from a read that failed.

    • first_seen_at
    • last_seen_at
    • last_read.at
    • last_read.status
    • last_read.last_complete_at
  • Its openings

    How many of its postings are open, and how many closed.

    • postings.open
    • postings.closed

The job posting

One record per posting, under its company. The same posting keeps the same id from one read to the next.

  • The opening

    The title as the posting wrote it and cleaned, the dates the posting gives, and labels for seniority and function read from the title by rule.

    • id
    • title
    • title_clean
    • employment_type
    • seniority
    • function
    • posted_at
    • valid_through
    • description
  • The company

    The company the posting belongs to, by domain and by name.

    • company.domain
    • company.name
  • The place

    The location as written, its parts where the source gave them, a country code, and whether the job is remote.

    • location.raw
    • location.city
    • location.region
    • location.country
    • location.country_code
    • location.remote
  • The pay

    Only when the posting states it. Never estimated and never converted.

    • salary.raw
    • salary.min
    • salary.max
    • salary.currency
    • salary.period
  • The source

    The posting's page, where to apply, and where it was read: an applicant tracking system, a web page or a job board.

    • url
    • apply_url
    • source.name
    • source.provenance
    • source.trusted
    • source.external_id
  • Its life

    Whether it is open or closed, when it was first and last seen, and when it was found closed.

    • status
    • first_seen_at
    • last_seen_at
    • closed_at
  • Its history

    The events of its life, the fields that changed, its sightings, and how often it reopened.

    • history.events
    • history.changes
    • history.sightings
    • history.reopened_count

How a posting is found closed

Only a complete read of a source counts. When complete reads of the source a posting came from stop listing it, the posting is marked closed, with the time of the read that confirmed it. A read that failed or was cut short closes nothing, and a closed posting that is seen again is open again, with both events kept in its history.

Where a posting was read

Every posting says where it came from. Postings read from an applicant tracking system are the company’s own list, and they are what you get unless you ask for more. Postings read off a web page or from a job board are kept and flagged, and returned only when you ask for them.

What is not settled yet

A dataset is bought on its numbers, and we do not have numbers we would stand behind yet. So this page gives none.

Price
There is no price list. We will not publish a number before it is one we will charge.
Size and reach
We publish no counts of companies, openings or countries. You will see what the data covers at early access, before you pay for anything.
How often it is refreshed
Not decided. Every posting carries when it was first and last seen, and every company when it was last read, so you can always tell how old the data is.
The final schema
The fields on this page are the data as it is built today. Anything added or changed is confirmed at early access.

One dataset now. More planned.

Job openings come first. Other kinds of data are planned, and we will name them here when they are decided. If there is data you would buy, tell us: it shapes what we build.

Need job openings now, and happy to run the scrapes yourself? The Scraper API is available today. It returns what a site lists at the moment you run it, without the history.

How early access works

  1. 1. You write to us

    Say which companies, places or kinds of job you care about, and what you would build with the data.

  2. 2. We reply

    With what the data holds today, how it would reach you, and what is still missing.

  3. 3. You decide

    Nothing is charged for asking, and nothing is sold until the dataset is ready to be sold.