Recruiting · Talent Room
Move an approved role into a real employee record.
Hiring loses accountability when approvals, interviews, scorecards and offers live in separate tools.
This is a capability inside Lightning Pharos, not a separate product.
Approve a requisition and move candidates through your stages.
01 · What ships
The complete working surface.
The hiring process, in the system where the hire will exist.
- 01
Requisitions that need an approval before a role can be opened
- 02
Pipelines per role, with candidates moving through your stages
- 03
Interviews with panelists and structured scorecards
- 04
Structured scorecards, so a decision has evidence behind it
- 05
Offers that create the employee record on acceptance: nobody re-types the hire
02 · Connected work
One action. One history. More than one team.
Pharos keeps the source action and the records it affects on one inspectable event path.
- 01 / 03
Source action
Approve a requisition and move candidates through your stages.
- 02 / 03
Governed event
Interviews, scorecards and the offer stay on the role and candidate.
- 03 / 03
Connected result
An accepted offer creates the employee record without retyping the hire.
03 · What it needs
Connected by design.
Pharos requires these modules first because the workflow depends on their records. The dependency is enforced in the product.
04 · Where it stops
The boundary is part of the product.
A hiring-process tool, not a sourcing suite: no candidate merge, job-board posting, CV parsing, assessments, talent pool, external calendar or email integration, interviewer-availability check, or offer-letter generation.
Bring your exact workflow to a walkthrough and we will show where Pharos fits and where it does not.
Continue the system