JobPosting structured data
Also called schema.org JobPosting, Google for Jobs markup.
Machine-readable markup employers add to a posting so search engines and aggregators can read its title, location, salary, and dates directly.
When an employer marks up a posting with schema.org JobPosting fields, the title, employment type, location, posted date, valid-through date and salary become structured data rather than prose. Search engines and job aggregators consume that directly, which is how the same role appears accurately across many sites without anyone re-keying it.
For a job seeker this explains a few otherwise puzzling behaviors. Search filters for salary or remote status only work on postings that declared those fields, so filtering aggressively silently hides roles that simply didn't publish the data. And a `validThrough` date that has passed is why a role vanishes from search while its page still loads.
It also explains the freshness differences between sources. A well-marked-up posting propagates with correct dates; one that has to be scraped from rendered HTML often arrives with the date the crawler found it, which is why the same job shows three different "posted" ages across three sites.
Job board
A site that lists openings from many employers — either posted directly by them or scraped and aggregated from their careers pages.
Job posting
The employer's public description of a role — part specification, part marketing, and rarely a literal list of requirements.
Evergreen requisition
A permanently open posting used to collect candidates for a role the company hires continuously — or isn't hiring for right now at all.