Grok Bot for recruiting: inbound screening on fixed criteria and a pipeline stall watch
Not tested yet: Eric Siu's video shows the full setup; we read only the post text. Recheck the video for criteria and approval steps. HRBP is a listing from a recruiting software company; we haven't installed it. Reported, not yet confirmed.
How a founder runs talent Bots against the same hiring criteria every time, how a recruiting CTO has a Bot find where candidates stall, and what to keep human.
Work value 3/10
Our first recruiting playbook covers interview prep, scorecards and outbound sourcing. This one covers the other end of the funnel: candidates who apply to you, and the ones who get stuck between stages. It is for a recruiter, a hiring manager, or a founder doing their own hiring.
Not tested: The Daily Bot has no ATS or candidates, so we haven't run these setups. Everything below comes from the linked posts and docs.
What recruiting uses it for#
- Screening inbound on the same rules every time. Eric Siu, founder of the ad agency Single Grain, posted on Sep 21: "We're using Juicebox and Grok Bot talent bots to make recruiting more repeatable." He lists what the system handles: "Inbound candidates," "Hiring criteria," "Candidate interest," "AI evaluation questions" and "Shortlisting." The point, he says, is "to apply the same criteria every time and spend human attention on the strongest candidates."
- A concrete criterion. Siu gives one: "two promotions across two companies with 3-year average tenure." Writing criteria that specific is what lets a Bot check them.
- Finding where candidates stall. Jony Musky, co-founder and CTO of a recruiting software company, describes a Bot called HRBP that "checks pipeline health, shows where candidates stall by stage, tells you when to push the search (sourcing, multipost, AI screens), and shortlists who is actually worth interviewing." He sells recruiting software, so read it as a vendor's description.
- Running recruiting loops. Kevin Niparko, a PM at SpaceXAI, lists a "Recruiter: finding undiscovered talent and managing recruiting loops" on his own Bot team in Grok Bot for PMs.
Connectors to set up#
Connect your ATS, the Gmail inbox where applications arrive, a Google Sheet or Notion page with the written criteria, and Slack for the hiring channel. Add them from Connect apps in the sidebar (Cursor's docs). If your ATS has no plugin, the Bot can sign in on its own computer, and you take over for the password and two-factor steps (Take over for sensitive steps).
Siu runs the criteria through Juicebox, which he says "also coordinates the agents running each step." You don't need it to copy the pattern. A shared criteria doc works with any ATS.
Routines#
No source here publishes a clock time. Siu's broader advice for every Bot is "Keep a human in the loop until the bot earns more freedom," from his Sep 2 post. So:
- Run the example prompt by hand on yesterday's applicants for one role. Compare its Shortlist with yours.
- Tighten the criteria doc wherever you disagreed. Then ask the Bot to save the method as a skill (Save a skill).
- Add the weekly Pipeline stall check from the routine above, with a quiet rule. Click Test on it first (Routines).
Example prompt#
This is our prompt, built from Siu's five steps. It stops before anyone is moved or contacted:
Read the hiring criteria doc for this role. Review every new inbound applicant in the ATS since yesterday. For each one, check the criteria one by one and quote the line in their resume or profile that meets or misses it. Sort them into Shortlist, Maybe and No with one line on why, and list anything you couldn't verify. Draft a short reply for the Shortlist only. Don't move anyone in the ATS, don't reject anyone, and don't contact any candidate.
What to expect#
These are self-reported, and none comes with a time figure or a hiring result. Siu's claim is consistency: the same criteria applied to every candidate. Musky's is visibility: which stage is the bottleneck this week.
Gotchas#
- Candidate privacy. Cursor's Talent scout starter says to "Keep external outreach behind approval, and have the Bot respect candidate privacy and each source's terms."
- Criteria can encode bias. A rule like Siu's tenure signal screens people out at scale. Have a person review the No pile, and check your criteria against your local hiring law before you automate them.
- Rejections stay human. The example prompt drafts replies for the Shortlist only. Siu says most of his Bots "cannot automatically send, publish, or change live pages."
- One job per Bot. Siu: "We made the mistake of trying to build one super-agent that could do everything. It became harder to manage, harder to evaluate, and less reliable." Keep screening and the stall check in a recruiting Bot that does nothing else.
- Busy inboxes cost usage. Each run spends usage, and a frequent schedule "can use a week of usage in a day" (Routines). Daily screening is usually enough.
Related#
- Grok Bot for recruiting: interview prep, scorecards, and sourcing batches
- One job per Bot, or one Bot for everything? How to decide
- Make Grok Bot routines stay quiet when nothing changed