Daily Recruitee interview prep briefs in each interviewer's Slack

Every weekday at 7am, each interviewer gets a Slack DM about the candidates they are meeting today, including what earlier interviewers already asked.

Agentic Task
RecruiteeGoogle CalendarSlack BotHR & PeopleMeeting WorkflowsDaily Digests
PromptCreate

Every weekday at 7am, build and send a personal interview prep brief to each person who is running an interview today. Use a cron trigger, Monday through Friday at 7am in my working timezone.

Start by calling Google Calendar List Events on my primary calendar, scoped to today only, from midnight to midnight in my timezone. Expand recurring events into individual instances so each interview shows up as its own entry.

Keep only the events that look like candidate interviews. The strongest signal is an event with at least one attendee whose email domain is outside my company, combined with interview language in the title such as interview, screen, phone screen, onsite, or a candidate name. Ignore internal meetings, focus time blocks, out of office blocks, and all day events.

For each remaining event, take the external attendee and call Recruitee List Candidates with a search query on their name. If that returns nothing, try again with their email address. If no candidate comes back either way, skip that event silently and move on: send no message and do not report the skip anywhere. Internal meetings must never generate noise.

When there is a match, call Recruitee Get Candidate for the full profile, then List Notes for Candidate to read what previous interviewers already recorded. Use the note author and timestamps to work out who said what, when, and at which stage.

Then write a tight prep brief of under 300 words covering four things: who the candidate is, meaning current role, background, and the job they applied for; what stage they are at in the pipeline; what earlier interviewers flagged, both positives and concerns, attributed to the person who wrote them; and three suggested questions. The three questions are the most important part of the brief. They must specifically avoid re-treading ground that earlier interviewers already covered, and should push into the areas the existing notes leave open or unresolved.

Deliver each brief individually rather than posting it to a channel. For every internal attendee on the event, meaning everyone on my company's email domain excluding the candidate, call the Slack Bot Look Up User by Email operation with their calendar email address to resolve their Slack user, then use Send a Message to DM them their own copy of the brief. A three person panel should receive three separate DMs with the same brief. If an interviewer's email does not resolve to a Slack user, skip that person and still deliver to everyone else on the panel.

Keep the tone direct and skimmable, because interviewers read this on a phone in the few minutes before the call. Lead every brief with the candidate name, the role they are interviewing for, and the interview time.

Example output

Interview: Priya Raman, Senior Backend Engineer, 10:30am (45 min) Stage: Technical interview, round 2 of 4 Who she is: Backend engineer at Kestrel Logistics, six years in Go and Python. Applied through the careers site three weeks ago. What earlier interviewers said: Marcus (recruiter screen, 12 Aug) rated her communication highly and noted she is weighing another offer with a two week deadline. Dana (hiring manager, 15 Aug) covered system design at length and flagged one gap: no production experience with event driven architectures, worth probing rather than assuming. Questions that cover new ground: 1. Dana already went broad on system design, so go narrow instead: walk me through a failure you debugged that only showed up under production load. 2. Nobody has asked about testing yet. What does she consider adequate coverage on a payments path? 3. Marcus flagged the competing offer but never asked what she actually wants next. What would make this role the better choice for her?

What does this prompt do?

  • Checks your calendar each weekday morning and picks out the candidate interviews happening today.
  • Matches each candidate to their profile in Recruitee and reads the feedback earlier interviewers left on them.
  • Writes a short brief covering who the candidate is, what stage they are at, and what has already been flagged.
  • Sends it as a private Slack message to every interviewer on the invite, with three suggested questions chosen to avoid ground that has already been covered.

What do I need to use this?

  • A Recruitee account with your candidates and interview notes in it.
  • A Google Calendar where interviews are booked, with the candidate invited as a guest.
  • A Slack workspace where interviewers use the same email address they use on calendar invites.

How can I customize it?

  • Change the send time or which days it runs, for example 6:30am, or weekends too if you interview then.
  • Adjust how long each brief is and how many suggested questions it ends with.
  • Change how an interview is recognized, for example only events on a dedicated hiring calendar or with a certain word in the title.

FAQs

What happens to meetings that are not interviews?
Nothing at all. If no matching candidate is found in Recruitee, the event is skipped quietly and no message goes out, so your internal meetings never turn into noise.
Who actually receives the brief?
Each internal person on the interview invite gets their own private Slack message. A panel of three interviewers gets three separate DMs rather than one shared post in a channel.
How does it know which candidate an interview is for?
It looks at the external guest on the calendar invite and searches Recruitee for them by name, then by email address. Interviews booked without the candidate on the invite will not find a match.
Will it just repeat questions other interviewers already asked?
Avoiding that is the whole point. The brief reads the notes previous interviewers left in Recruitee and deliberately suggests three questions that push into areas nobody has covered yet.
How long is each brief?
Under 300 words, so an interviewer can read the whole thing on their phone in the couple of minutes before joining the call.

Related templates

Auto-fix your calendar when a flight slips, and flag what's at risk

When your flight moves, your calendar times get corrected automatically and you get a Slack note naming the meetings you're about to miss.

Google Calendar
AviationStack
Slack
Agentic Task
Build a credential rotation checklist when someone leaves

When someone leaves, we check which shared passwords they used in their final months and post a ranked rotation list to your security channel.

1Password
Rippling
Slack Bot
+1
Agentic Task
Weekly Amazon S3 bucket security audit posted to Slack

Every Monday, check every S3 bucket for public exposure, missing encryption and weak backup settings, then get the risks ranked in Slack.

Amazon S3
Slack Bot
Google Sheets
Agentic Task
Log Agorapulse social conversations to HubSpot contacts

Twice every weekday, the conversations from your social inbox land on the right HubSpot contact timelines, with a Slack recap for sales.

Agorapulse
HubSpot
Slack Bot
Agentic Task
Clean up HubSpot contacts from your Amazon SES suppression list

Every morning, find the addresses that hard bounced or filed a spam complaint, update the matching HubSpot contacts, and post a short Slack recap.

Amazon SES
HubSpot
Slack Bot
Agentic Task
Draft polite follow-ups for emails that never got a reply

Every weekday at 4pm, spot the threads that went quiet, stage a ready-to-send nudge in your mailbox, and get a ranked Slack recap.

Aurinko
Google Sheets
Slack Bot
Agentic Task

Stop walking into interviews cold.

Give every interviewer the candidate's history and three fresh questions before they join the call, without anyone digging through the ATS.