How to Define a Candidate Discovery Hypothesis

When a search produces the wrong kind of candidates, changing the channel or adding keywords can hide the real problem: an untested assumption about where relevant people will appear and what their public evidence will look like.

A candidate discovery hypothesis is a narrow, testable claim about a search. It states the route, expected background, job-related supporting signal and observation that would weaken it. It is a test, not a candidate quota or hiring forecast.

Separate the claim from the evidence

Start with the assumption in plain language: "People who have done this type of work may be found through this route." Remove words that cannot be checked. "Great operators", "culture fit" and "top talent" are preferences until the role owner defines an observable, job-related signal.

Use this sentence pattern:

If we search [defined route] for [work background] in [approved scope], we expect [observable signal] to appear often enough to meet [team-set threshold]. The claim is weakened if [falsification check] occurs. We will then [next action].

The threshold belongs to the hiring team. It is a decision rule for this search, not a market benchmark. Set it before reviewing results so a plausible profile does not change the standard.

Define the test in six moves

1. Name one assumption

Choose one proposition, such as "reliability engineers with customer-facing API ownership may be discoverable without the exact title 'platform engineer'." Do not combine title, location, seniority and compensation assumptions. A claim that can fail for four reasons cannot tell you what to fix.

2. Describe the expected work signal

Write what a reviewer could point to: ownership of an on-call system, a documented migration, a shipped service or a responsibility stated in a professional profile. A keyword, employer prestige or title can be a lead, but is not automatically evidence of the work claimed.

3. Set evidence thresholds

Use explicit levels rather than an opaque pass/fail label:

• Supported: the pre-set minimum number of reviewed records shows the defined signal, with no unresolved hard constraint.
• Weakened: the signal appears, but below the minimum or only in an ambiguous form.
• Inconclusive: the available sources do not show enough job-related detail to test the claim.
• Contradicted: a defined disconfirming pattern appears, such as the route consistently producing a different kind of work.

"Inconclusive" matters. Missing public evidence is not proof that a person lacks the capability; it is a reason to verify, change the question or stop relying on that signal.

4. Predeclare the falsification check

Write down what would make you stop defending the idea: repeated records whose titles match but whose work does not, a hard location boundary the route cannot satisfy, or reviewers unable to agree whether the signal is present. A check should be observable and tied to one decision, not "the results feel weak".

5. Run a traceable review

Capture the route, review date, source, observed wording, interpretation, unknowns and decision. Keep duplicates together. Ask a subject-matter reviewer to examine borderline cases when the evidence rule is consequential. The purpose is to test the claim, not build a flattering list.

6. Choose the next action

If supported, keep the claim as an approved route and state what needs human verification. If weakened, revise one part and record why. If inconclusive, ask whether a person can verify the missing fact through a legitimate process. If contradicted, retire the claim and write the replacement question.

Candidate discovery hypothesis worksheet

Copy this table into the role record. Thresholds and names are for the team to set.

Example: diagnose the failed assumption

Example only: suppose the team expects strong infrastructure candidates to use a familiar title. The first review set contains matching titles, but most descriptions list ticket handling rather than production ownership. The title assumption is weakened; adding title variations is not the immediate answer. Test the work signal, retain uncertain records for verification and ask whether production ownership is essential.

If relevant ownership appears under several titles, the claim is supported for this search. That does not establish interest, availability, authorship or job performance. It only says the discovery assumption is worth retaining while people responsible for contact and assessment do their work.

Failure analysis: what the result is telling you

Keep AI output inside the test boundary

Talent Summoner is our product for AI candidate sourcing, CV ranking and outreach you confirm before it sends. Its current candidate-sourcing workflow, checked 3 October 2026, starts with a role description, searches LinkedIn, GitHub and other public professional sources across 200M+ profiles, and returns ranked candidates against must-haves and nice-to-haves with plain-English reasoning. Use that output as a review set, but a rank is not evidence that the claim is true. People still inspect sources, verify material facts, contact candidates, interview and decide.

If you already have CVs, candidate ranking addresses a different question: how supplied documents compare with a job description. Keep it separate from a discovery test so a well-ranked pile is not mistaken for evidence about where new candidates can be found.

The ICO's recruitment-AI guidance, published 6 November 2024 and checked 2 September 2026, tells organisations to consider a DPIA, lawful basis, documented responsibilities, fairness and accuracy monitoring, transparency and minimum necessary personal information. This is general information, not legal advice; apply the rules for the organisation and jurisdiction. NIST describes its AI Risk Management Framework as voluntary guidance for incorporating trustworthiness into AI design, development, use and evaluation. Neither source turns a sourcing hypothesis into a hiring standard.

Next step

Write one assumption, observable signal, team-set threshold and falsification check in the worksheet. Name the decision owner, then start a candidate sourcing search or test existing material with candidate ranking. Record the result before changing the brief.

FAQ

Talent Summoner product facts read from our live candidate sourcing and candidate ranking pages, verified 3 October 2026. We re-verify this page quarterly — tell us if something changed.