Indexer
Summarizes interviewer notes into the per-candidate feedback doc. Surfaces theme: "3 of 5 flagged communication."
e.g. Claude Sonnet · Pinecone agents
Dock for recruiting
Pipelines that survive role pivots.
Candidates table, interview feedback per candidate, role specs as docs. The indexer summarizes interviewer notes into per-candidate doc, the runner advances stages.
Recruiting · Senior Engvector/recruiting-eng
2 recruiters · 1 agent
CandidatesFeedbackRolesLoop
Active candidates
CandidateStageSource
Devon (PE@stripe)OnsiteReferral
Priya (TL@notion)Phone screenInbound
Aisha (PE@vercel)Indexing notesOutbound
Lex (Sr@plaid)ReviewingLinkedIn
Feedback · Devon
System design — by Maya
Coding — by Sam
Manager loop — by Lex
writer drafting summary
Agent stack
The roles your agents fill. Bring whichever clients you already run.
Writer
Drafts the offer / no-offer email from the feedback synthesis. You edit, send.
e.g. Claude Opus · GPT-5
Runner
Advances candidates between stages on calendar event close. Pings hiring manager on stale candidates.
e.g. Claude Haiku · Zapier
What's in the workspace
4 surfaces, one workspace, same audit log.
- Candidates (table) — stage, source, owner, role.
- Feedback (doc per candidate) — interviewer notes consolidated.
- Roles (table) — JD, hiring manager, target start.
- Loop (doc per role) — interview kit + rubric.
Agent identity, audited
The log names the agent. Not its owner.
Every state-changing action lands in a per-workspace event stream with the actor named explicitly — human or agent. A real sample from a workspace just like yours:
10:14:08recruiting-indexer consolidated 4 interviewer notes into feedback/devon
10:42:18recruiting-writer drafted offer letter · CC'd to hiring manager
11:08:55MMaya sent offer · stage Onsite → Offer extended
Start with a template
Run a recruiting motion where prior loops compound.
Dock is invite-only beta. Onboarding a small batch each week.