The job of this console
Book interviewers, capture outcome, push the candidate forward or out. Keep the req attached.
People · ATS
Interviews
Scheduled interviews on candidate × requisition — calendar coordination, not the project calendar of delivery work.
Scroll to Flowcharts. Scenario: Schedule an interview loop.
Hiring loops
Time on the candidate, not on a deliverable
Interviews schedule loops for ATS candidates. They are not Task due dates and not attendance marks.
People → Interviews
Route
/recruiting/interviews
Org flag recruitingEnabled
HR Admin · Admin
Seat at the table
HR Admin and interviewers in scope. Candidates see invites, not this register.
The working rhythm
Open upcoming, schedule, record outcome, return to candidates.
Moments that bring you here
On-site week. Panel conflict. A late reject after loop. Reschedule.
ⓘ
ATS event
Delivery calendar and holidays stay on their own screens.
Flowcharts
1 — Schedule and outcome
Book the loop, record the result on the candidate.
flowchart TD
A[Open Interviews] --> B[Pick candidate]
B --> C[Schedule loop]
C --> D[Interview happens]
D --> E[Record outcome]
E --> F[Advance or reject candidate]
- 1OpenPeople → Interviews.
- 2ScheduleCandidate + interviewers.
- 3OutcomeWrite on the candidate.
- 4AdvanceOffer or reject.
Overview
Interviews are ATS events. Project calendar and People holidays are different calendars.
How to use
1. Outcome on candidate
Do not leave the decision only in chat.
2. Interviewers
Need time, not a project assignment.
3. No-show
Record it so the funnel stays honest.