People · Recruitment
The same pipeline, from both sides.
A public careers page, and a pipeline that ends in an employee record.
What a candidate sees
Your careers page, on your workspace's own address.
- 01Browse open roles
- 02Apply without creating an account
- 03Track their own application in the candidate portal
- 04Hear back on a decision
What your team sees
The pipeline behind it.
- 01Applied
- 02Screening
- 03Assessment
- 04Interview
- 05Offer
- 06Hired — converted to an employee record
Turning a candidate into an employee is its own permission.
Running it
What's on the inside.
Job postsWritten once, published to the careers page, closed when filled — no second copy on a job board to forget about.
Candidate detailApplication, documents, stage history, and notes on one page rather than across an inbox thread.
ProgramsRecurring intakes — graduate schemes, fellowships — run as programs rather than a job post recreated each cycle.
Rejection, handledA closed loop with the candidate, because a silent pipeline is a reputation problem.
The handover that usually gets lost
A hire converts into the employee record directly — name, role, department, start date. It's the same moment HR would otherwise be re-typing from an email.
Next
Where this connects.
See Recruitment on your own work.
We'll run a live project of yours through it rather than showing a demo tenant.
Request a demo