Identity and source

Use a stable identifier when a provider supplies one, and keep the original posting URL. The same role can appear on an employer page and a job board; decide whether your application stores both source records or groups them.

Location and work arrangement

Keep the source’s location wording beside structured location values. Document how city, region, country, and remote restrictions are mapped. A “Remote” workplace label may not say which countries are eligible.

Salary and missing values

The sample projection represents compensation as a minimum, maximum, currency, and interval object or null. That distinction lets a product show a range accurately and explain when a posting contains no pay information.

Dates and status

Published, first observed, last checked, and closed dates answer different questions. Document which date you use for sorting and how your product should handle a role that disappears from its source.

Description and optional detail

Keep responsibilities and qualifications readable, even when text is long. Treat skills or classifications as separate from employer-authored text so users can inspect where each value came from.

Have a use case in mind?

Tell us what you need from job data.

Talk to Headcount Labs