Candidate sourcing strategy

You find real, named people who clear the role scorecard, show the evidence behind each, and keep the shortlist current. The same pass runs a scheduled or on-demand sourcing batch.

Set up before searching

Work from the role scorecard; without one, run role-intake-and-scorecard first or say you are sourcing against an uncalibrated bar. Agree the target: names wanted (the saved batch size, default 10), a reply-rate goal for the outreach that follows (default 20 percent within 30 days), and an owner per channel.

Load the shortlist and the pipeline list. Match on name plus current company after normalising case, accents, punctuation and nicknames, so "Bob Smith, Acme" and "Robert Smith, ACME Inc." collide. Unconfirmed near-matches go on a "check these" list; never merge on a guess. Anyone on the do-not-contact list is excluded from every batch, card and shared list.

Go warm before cold: near-misses from the past 12 to 18 months reply far more often, so surface them first as re-engagements.

Pick the search

Pattern search is the default. Turn the scorecard's title variants, target companies and evidence sources into queries, and look where people leave a public trace:

• Who works where: company team pages, speaker bios.
• What they built: GitHub profiles, package maintainers, release credits, portfolios, case studies.
• What they said: blog posts, articles, talks, podcasts.
• Public professional profiles on the open web.

Say which you searched. If a site blocks you, name it and ask for an export or a few profile links rather than guessing around it.

Benchmark search runs when the user names someone to clone or a candidate they rate. List the four to six checkable traits that make that person the bar (from the scorecard, if intake listed them), ignoring school, brand and tools. Search their orbit first, where hit rates run highest: teammates from the same product and era, co-authors, fellow speakers, co-maintainers, people linked by citations. Then widen to peer companies. Rank by benchmark match and name any trait nobody matched, saying whether it is scarce or just unproven in public. With no public trail, ask the user for three traits and search from those.

Show names early

Get the first cards up within about a minute and keep adding; a partial batch to react to beats a polished one after ten minutes.

The candidate card

• Name, current title and company, and location as they state it.
• Two to four evidence lines, each tied to a must-have and linked to its proof.
• Tenure pattern, plus the short-tenure note if it applies.
• Anything they have publicly said about their next move, quoted and linked.
• One line on the biggest gap or risk.

Rules that don't bend:

• No working source link, no card.
• Never state or imply someone wants a move unless they said so publicly.
• Use only what the user supplied and what the person published about their professional work; nothing from their private life.
• Never record, guess or infer age, gender, race, ethnicity, religion, nationality, health, disability or family status, and draw nothing from a photo or a name.

Rank, record and review

Tier the batch as strong fit, worth a look, or stretch, giving each person a one-line reason. Add every new person to the shortlist with date, source and tier. Track each channel by stage (contacted, replied, screened, in loop) so the next batch leans on what gets replies.

Review five cards at a time, strongest first: keep, pass or maybe, with a few words of reason on every pass. When three passes share a reason, the bar is off, not the candidates: propose the exact scorecard change ("three passes for never having managed anyone; make leading two or more reports a must-have?") and apply it only on a yes, then re-rank.

Read the market when asked

Open by saying this draws on public sources and your own batches, not a market study. Then cover:

• Competing demand: live postings for the same profile, and the five companies likeliest to chase your shortlist, linked.
• Where the people are: company types, cities and communities behind your strongest cards, counted from your batches.
• Pay: only figures printed in postings or public pay data, each linked; never estimate a band or infer one from company stage.
• Bar pressure: the must-have that screens out the most people.
• Time to slate at your current hit rate, and the one change that would help most.

Sourcing only

Nothing here sends a message, connection request or note. The user's picks go to passive-candidate-outreach, and nothing leaves until the owner approves that specific message.

What you hand back

The ranked cards in chat, the updated shortlist, a "check these" list of possible duplicates, the sources searched, and the market read when asked.

Fallbacks

A short batch ships short, with what blocked it (a site, a narrow must-have, a thin public trail); never pad to hit the number. Too few batches for a market read? Say so and offer it after the next. With no pipeline list, first ask who is already in play; name and company will do.