WorkerKitJoin the waitlistAI workers for Recruiting
AI workers for recruiting teams that move candidates through the pipeline, schedule interviews, and keep every hiring thread tidy. Connect Google Calendar, Gmail, and your tracker, then let the firewall keep candidate data scoped and private.
- Recruiting Coordinator Language model Keeps candidate threads moving: replies drafted, interviews scheduled, and the pipeline board current.
- Interview Panel Schedule Review Language model Checks interview panel timing, attendance responses and preparation gaps.
- Interview Guide Coverage Review Language model Checks a role-specific interview guide for observable job-related criteria.
- Interview Panel Preparation Workflow Language model Combines panel logistics and the role guide into a structured interview preparation pack.
What is a Recruiting AI worker?
A Recruiting AI worker is an AI agent set up to run one recruiting job unattended, such as moving candidates through a pipeline, scheduling interviews, or keeping hiring threads organized. It typically touches Google Calendar and Gmail or Outlook, an Asana or Notion candidate tracker, and Slack hiring channels, and only the calendars, threads, and fields you approve.
What these workers do
Schedule interview slots
Read interviewers' Google Calendar availability and propose times to candidates by email, leaving the final booking to the recruiter to confirm.
Move candidates through the pipeline
Watch reply emails from candidates and flag which ones are ready to advance a stage on the Notion tracker for a recruiter to action.
Chase pending interview feedback
Find interviews from yesterday with no scorecard filed and nudge each interviewer in Slack so decisions are not held up.
Summarize a candidate thread
Condense a long Gmail thread with one candidate into a short status so the next recruiter picks up without rereading everything.
How a Recruiting AI worker runs
What a recruiting worker connects to
A recruiting worker connects to the tools hiring runs on. Point it at Google Calendar and Gmail or Outlook for scheduling and outreach, Asana or Notion for the candidate tracker, and Slack for interview feedback. Candidate data is personal, so you approve exactly which calendars, threads, and boards it can open, keeping other candidates and teams out of scope.
When it runs
- On a schedule for a daily pipeline check or a feedback chase.
- On a trigger when a candidate replies or an interview ends.
- On demand when a recruiter needs a candidate's status fast.
What stays under your control
The firewall protects candidate privacy. You can keep the worker read-only so it schedules and summarizes without emailing on its own, redact identifiers before they reach the model, and block specific contacts. Per-board scope keeps it inside the roles you name, rate limits keep outreach measured, and the audit trail records every thread it opened. You can revoke access to any calendar or board instantly.
Recruiting questions, answered.
Can a recruiting AI worker email candidates for me?
Only if you grant send access. By default a recruiting worker drafts scheduling and outreach emails and leaves them for a recruiter to review and send. You can keep it draft-only, block specific contacts, and cap how many messages it produces. This keeps a human on candidate communication while the worker handles the coordination and prep behind it.
How does it keep candidate data private?
A recruiting worker runs behind the firewall, which redacts candidate identifiers before they reach the model and scopes the worker to only the threads and boards you approve. Other candidates stay invisible, sensitive contacts can be blocked, and DLP scanning flags anything risky. Every thread and record it opens is logged, and you can revoke its access at any time.
Can it schedule interviews across calendars?
Yes, a recruiting worker can read the interviewers' Google Calendar availability you scope in and propose times, leaving the booking to a recruiter unless you allow writes. Free or busy detail can be limited, and calendars you exclude stay hidden. You control which calendars it reads, and every availability check is recorded in the audit trail for review.
Will it advance candidates without a recruiter?
No, unless you grant write access a recruiting worker only flags which candidates look ready to advance, leaving the stage change to a recruiter. Most teams keep it read-only on the tracker. When you do allow writes, the firewall confines them to the fields you approve, logs each one, and lets you revoke that access whenever you choose.