Live jobs board

Give candidates a clear route to the roles you actually have

Let someone find a relevant vacancy, understand it on a phone and apply through the agreed route. Keep the page aligned with the record your desk maintains, so a filled role stops taking applications. The working demo lets you try that behaviour with fictional vacancies.

02One vacancy recordIllustration
One vacancy record: Prepare one recordThe owner enters the vacancy facts once. Required fields and dates are checked before publication. Owner record → Shared live state → Public role and feed. Illustrative vacancy data. The working demo stores synthetic records in your browser and submits no real applications.
Step 1 of 4
  1. The owner enters the vacancy facts once. Required fields and dates are checked before publication.

  2. Owner, candidate and engine-room views read the same published record.

  3. The public role, application route and machine-readable feed follow that shared state.

  4. A filled or expired role leaves active results and stops accepting applications, including a stale application already open.

The owner enters the vacancy facts once. Required fields and dates are checked before publication.

Illustrative vacancy data. The working demo stores synthetic records in your browser and submits no real applications.

What a working board gets right

One source of truth

Every view reads the same records. What the owner publishes is what the candidate sees and what the machine reads. No third copy drifting out of date on a subdomain nobody edits.

A page for each role

Each role has a shareable web address and a description visible without a login. Candidates can assess the vacancy, and the page facts agree with its structured job data.

Honest expiry

Filled and expired roles leave the active results and stop accepting applications. A role expiring mid-application is handled with a clear recovery, not a silent failure.

Machine-readable, carefully

Structured job data belongs on a single real vacancy detail page and describes the hiring employer, not automatically the agency. We do not populate salaries or apply routes without the facts to back them.

Make real vacancies eligible for Google's job results

Correct job markup makes a page eligible for job results. Crawling, indexing and display remain the search engine's decision, so eligibility cannot promise an appearance or a publication date.

So the honest objective is a role that is rendered, readable and marked up where the facts support it, with visibility observed after publication rather than declared at launch.

The demo uses fictional vacancies. Its technical view shows an illustrative code example; those roles are kept out of search and no real application is submitted.

Try publishing and closing a fictional role

Open the jobs demo, check the candidate view and see what happens when a vacancy closes. Reset it when you have finished.