PROCESS
Candidate:
Primary process used to track each applicant’s progress through the hiring
pipeline and to store core context (identity, contact, resume, source, target close
date, and immediate next step).
Job Requisition:
Supporting process that provides role context (role, department, location, hiring
manager, priority). Multiple Candidates can link to a single requisition to
centralize hiring demand.
Interview: Related process linked to Candidate as a multi-entry list. Each
interview entry captures the meeting type, interviewer, schedule, outcome, and
notes, and appears inline on the Candidate record for quick review.
Flow
Pipeline stages on Candidate define the lifecycle: Sourced → Screening →
Interview → Offer → Hired/Rejected. Movement between stages happens after key
events (e.g., interview outcome recorded) so every transition has a traceable
reason.
Interviews are created directly from the Candidate, scheduled, and updated with
outcomes. Stage changes are then applied on Candidate to reflect decisions.
Job Requisitions anchor demand and reporting; Candidates reference a
requisition so pipeline views can be filtered by role, department, or manager.
User Journey
A recruiter receives an inbound application for “Data Analyst — Bengaluru” and
creates a Candidate linked to that requisition. They attach the resume, note the
source, set a target close date, and define the next step as Schedule HR screen.
An Interview entry is added under the Candidate and assigned to an interviewer
with a date. After the conversation, outcome is recorded. If positive, the recruiter
adds Tech Round and advances the Candidate to Interview; if not, they set the
Candidate to Rejected with a short note for auditability.
When the Tech Round is positive, the recruiter moves the Candidate to Offer and
updates the next step to “Prepare offer letter.” Upon acceptance, the Candidate
is set to Hired, completing an auditable path from sourcing to decision.
How this solution will be used?
Daily triage: The List view surfaces stage, role, source, next step, and
target close date so recruiters can prioritize outreach and scheduling
without opening every record.
Scheduling: The Interviews list highlights upcoming conversations across
candidates and shows outcomes immediately in the Candidate context.
Reporting hooks: Because Candidates link to Job Requisitions and
Interviews record outcomes, it is easy to filter pipelines by
role/department and analyse conversion at Screening, Interview, and
Offer.
Why is it useful?
1. Clarity: A single place to see where each candidate stands, what’s next,
and by when reducing follow-ups and missed handoffs.
2. Speed: Inline interviews and simple stage updates minimize clicks and
training time, enabling faster cycle times from sourcing to decision.
3. Accountability: Stage transitions are tied to interview outcomes and notes,
creating a lightweight audit trail for fair, transparent hiring.
4. Scalability: Separate processes for Candidate, Job Requisition, and
Interview keep the model modular—easy to extend with approvals,
templates, or analytics without redesigning the core.