Recruiter Discovery Workflow

Weekly recruiter discovery finds high-fit talent contacts, recommends engagement, and keeps career targeting current without sending anything automatically.

The recruiter-discovery automation supports Kevin's outbound career motion alongside Career Pipeline Workflow. It is relationship discovery and outreach planning, not a message-sending loop. Source: automations/recruiter-discovery.md, 2026-05-31

Routing

Use this workflow for recruiter and talent-partner discovery. Use Career Pipeline Workflow for role discovery and Application Standout Protocol for a specific application package.

Trigger

• Weekly automation from automations/recruiter-discovery.md.
• Manual request when Kevin changes target companies, starts a search, or wants warm recruiter relationships before needing them.
• Follow-up when a previous connection request was accepted and needs a next action.

Inputs

• Target company list, role archetypes, and career strategy from Career Profile.
• LinkedIn profile, public LinkedIn search, recruiter posts, and company hiring pages when available.
• Prior recruiter-discovery outputs and any known connection status.
• Writing and Content Skills for personalized notes.

Runbook

1. Read Career Profile and identify current target-company tiers.
2. Search recruiters, talent partners, recruiting leads, and founders who publicly hire for relevant engineering roles.
3. Deduplicate existing connections and pending requests.
4. Score each contact by company tier, active role relevance, mutual connections, public engagement, and cross-company network value.
5. Recommend 5-10 priority contacts with a reason, pre-connect action, and concise personalized note.
6. Identify 2-3 posts worth engaging with before connecting when public activity exists.
7. Record accepted, pending, stale, and follow-up states when known.
8. When Kevin declines an inbound role but wants the relationship warm, record or update Career Contact Ledger with the source, specific relationship value, not open state, and reconnect trigger. A warm close is not permission for further submissions.

Promotion

Update Career Profile only when company targeting, role targeting, or networking strategy changed. Do not create person pages for every recruiter from a scan. Create or update a person page only when the recruiter becomes materially relevant beyond a one-time recommendation.

Output

Write outputs/<YYYY-MM-DD>/recruiter-discovery/<agent>.md with target updates, recruiter discoveries, engagement targets, connection recommendations, warm-close relationship updates, and pipeline status. Never auto-send connection requests or messages.

Validation

Every recommended outreach item needs a company, role/title, why-connect rationale, and personalization signal. Generic recruiter lists are a failed run with extra formatting.

Run Contract

This workflow follows Workflow Run Contract: name the sources, write output or no-op proof, promote only durable facts, update state only when the run really completed, refresh generated surfaces when durable pages or skills change, and log user-visible work.

---

Timeline

• 2026-07-01 | Expanded into a weekly relationship-discovery contract with routing, trigger, inputs, scoring, promotion boundaries, output, and validation. Source: User request, 2026-07-01
• 2026-05-31 | Workflow page created from recruiter-discovery automation. Source: automations/recruiter-discovery.md, 2026-05-31
• 2026-07-22 | Added Career Contact Ledger as the owner for warm career closes: preserve genuine future relationships, keep Kevin explicitly unavailable, and require fresh approval before recruiter submissions resume. Source: User request, 2026-07-22