Live jobs and applications
Publish the vacancy once and check what a candidate sees. Close it when it fills, then watch the application route follow the change. This prototype shows the board behaviour your desk can evaluate before we scope a real site or ATS connection.
Try this: start a fictional application in the Candidate view, expire the role in Owner, then return to Candidate. The draft is kept and cannot be submitted. Engine room is the optional technical view. All records are fictional and applications stay in this browser.
The example uses this as the hiring organisation, or marks it confidential when blank. It is never set to the agency.
One vacancy, with everyone reading the same version.
The role has been filled. Somewhere, a third copy of the advert is still cheerfully recruiting for it. A shared record gives the website a way to know when to stop.
Try the jobs engineThe owner enters the vacancy facts once. Required fields and dates are checked before publication.
Owner, candidate and engine-room views read the same published record.
The public role, application route and machine-readable feed follow that shared state.
A filled or expired role leaves active results and stops accepting applications, including a stale application already open.
Illustrative vacancy data. The working demo stores synthetic records in your browser and submits no real applications.
Want this fed from your real ATS?
The connections here are examples. Tell us your ATS and the vacancy or application job you need; we check your account's actual capabilities before quoting the connection.