InfuseOS Workflow Stack #10: The Hiring Pipeline Engine

Web Search → Gmail → Calendar → Google Docs → Drive (hire faster, stay consistent, don’t drop candidates)

Hiring breaks for the same reason everything breaks: ops debt.

Candidates don’t fall out of your funnel because you picked the wrong person. They fall out because:

• outreach is inconsistent
• scheduling drags
• interviewers aren’t aligned
• notes are scattered
• debriefs don’t happen
• decisions slip a week (and the best people disappear)

This workflow turns hiring into an execution loop you can run in one command: source → contact → schedule → interview packet → scorecards → debrief → decision email, all stored cleanly.

What you get (every run)

• A Drive folder: Hiring / [Role] / [Candidate Name]
• A Google Doc: Interview Packet — [Candidate] — [Role]
  • role summary + evaluation rubric
  • interview plan (stages + who asks what)
  • scorecards (per interviewer)
  • debrief section + hiring recommendation
• A scheduled calendar event (or 3 options to choose from)
• Ready-to-send Gmail emails (outreach, scheduling, follow-up, pass/offer-next-step)

Workflow playbooks (single prompts, multi-tool execution)

1) Build the role kit (rubric + interview plan + question bank)

Research best-practice interview loops for hiring a [ROLE] at a fast-moving startup. Create a Google Doc titled “Role Kit — [ROLE]” with: (1) success profile, (2) must-have signals, (3) red flags, (4) 10 interview questions per category (technical, systems, collaboration, execution), (5) a scorecard rubric (1–5) with definitions, and (6) a recommended interview loop (stages + time + interviewer responsibilities). Save it to Drive under “Hiring/[ROLE]/Role Kit/”.

2) Candidate outreach that’s actually personalized (research → email → tracker doc)

Research [Candidate Name] quickly (public info only) and extract 3 personalization points. Draft a concise outreach email for [ROLE] (tone: founder, direct, respectful). Create a Google Doc titled “Candidate Outreach — [Candidate Name]” containing the email + 3 follow-up variants. Save it to Drive under “Hiring/[ROLE]/[Candidate Name]/”. Then send the initial outreach via Gmail.

3) Scheduling that doesn’t stall (thread → 3 options → booked → confirmation)

Find the email thread with [Candidate Name]. Propose 3 options next week for a 30-minute intro call between 10am–4pm. After I pick A/B/C, create the calendar event titled “[Candidate] — [ROLE] Intro” and send the confirmation email with the time, video link details (if applicable), and what we’ll cover.

4) Generate the full interview packet (candidate + role kit + stage plan)

Create an “Interview Packet — [Candidate Name] — [ROLE]” Google Doc using our “Role Kit — [ROLE]”. Include: candidate summary (from our email thread), interview stages, goals per stage, tailored questions, and a scorecard section for each interviewer. Save it in Drive under “Hiring/[ROLE]/[Candidate Name]/” and include links to any candidate materials you find in Drive.

5) Post-interview debrief → decision email (no more limbo)

Create a debrief section in the candidate’s Interview Packet with: (1) key signals, (2) concerns, (3) open questions, (4) recommended next step. Draft the decision email based on the outcome: (A) move forward and propose 3 times for next round, or (B) respectful pass. Show me the email before sending.

The master prompt (copy/paste)

Run the Hiring Pipeline Engine for [ROLE] and [Candidate Name]. Create/locate a Drive folder “Hiring/[ROLE]/[Candidate Name]/”. Pull context from the Gmail thread with the candidate. Generate a Google Doc “Interview Packet — [Candidate] — [ROLE]” using our role rubric: stages, goals, tailored questions, and scorecards. Propose 3 intro call times next week; after I choose, book the calendar event and send the confirmation email. Then prepare next-step email templates (advance/pass) and keep them in the candidate folder.

Add control if you want:

Draft everything first and show me the emails before sending.

Quick prompts (still cross-tool, outcome-based)

• “Make this candidate real”

Create the candidate folder + interview packet + scorecards + scheduling options from the existing email thread.

• “Stop interviewer chaos”

Build a role rubric + question bank + stage plan in a Doc, and reuse it for every candidate.

• “Never leave candidates hanging”

After each stage, update the packet with a debrief and draft the correct next-step email immediately.

Why this stack is different (and why it matters)

This isn’t “write emails” or “schedule meetings.” It’s a repeatable hiring system that produces the artifacts teams actually need:

• consistent evaluation
• fast scheduling
• clean documentation
• decisive next steps