← all playbooks

Find candidates who have said publicly that they are open to work

A ranked list of people who match the spec and show a public open-to-work flag or another visible sign of availability, each marked with the signal they showed, their dated work history, and a personal email or LinkedIn profile.

use when
a role has to be filled fast and you want to start with the people who have raised a hand, without the open-to-work filter in LinkedIn Recruiter
starts from
A job spec

The prompt

Paste it into Claude Code or the Claude desktop app with Hyreflow connected. The first line tells your agent to use Hyreflow, so it reads the play, asks before it spends anything, and hands the work back to you.

paste this into Claude
Use hyreflow and find <ROLE_TITLE> candidates in <LOCATION> who are open to
work.

<PASTE THE SPEC, OR DESCRIBE THE ROLE IN A PARAGRAPH>

How I want it run:
- Search for people carrying the open-to-work flag, always paired with the
  titles, skills and location from the spec. Tell me how many match before
  you pull them.
- Pull each person's real work history. Mark anyone who has started a job
  in the last <MONTHS> months, the flag is probably stale.
- Read the profiles for other signs of availability: "seeking" wording, a
  contract ending, a recent end date. Note which signal each person showed.
- Score against the must-haves and show me the reasoning.
- Personal email and LinkedIn for the ones who pass. Never work email.

Run five first and tell me what the full run costs before you do the rest.
I want <N> people, ranked, as a CSV. Do not contact anyone.

Replace every <PLACEHOLDER> with your own detail. Everything else can stay as written.

What you need first

  • A job spec, or the titles, skills and location that matter
  • A location, with a radius or a remote policy
  • A Hyreflow workspace with credits

Tools it can reach for

The agent picks per step from what your workspace has. Nothing here is required by name.

What happens when you run it

Free steps are marked free. Anything that spends credits is marked, and the agent asks before the first paid run of any size.

  1. 1

    Turn the spec into a search

    free

    Titles with their real-world variants, must-have skills, seniority and the commute belt around the location. The flag is never searched alone, because on its own it matches a pool far too large to be any use.

  2. 2

    Count the flagged pool first

    credits

    One people database in the stack records the open-to-work badge. The agent pulls a single row first, which also reports how many people match in total, so you see the size of the pool before you pay for it.

  3. 3

    Pull the flagged people

    credits

    The badge filter combined with your titles, skills and location, sized to the number you asked for plus headroom, because some people fall out at every later step.

  4. 4

    Add people who said it in a post

    credits

    Optional. A keyword search over public LinkedIn posts from the past week, narrowed by the role in the author's headline, finds people who announced a search without touching their profile. Each request is charged whether or not it finds anyone.

  5. 5

    Pull the dated work history

    credits

    A badge in a database is a snapshot. The career history shows whether the person has started somewhere since, which is the usual reason a flagged profile turns out to be stale.

  6. 6

    Read for quieter signals, then score

    credits

    Each profile is read for the other signs: seeking wording in the headline, a contract ending, a recent end date, an ex-employer prefix. Everyone is then scored against the must-haves, with the signal they showed kept on the row.

  7. 7

    Find contact details for the survivors

    credits

    Personal email and LinkedIn only, walked through the providers in a set order that stops at the first hit, then a deliverability check. A miss usually costs nothing.

What a run costs

Credits are spent per candidate the play actually works, and a lookup that finds nothing usually costs nothing. The two figures are the run where the first provider answers and the run where every lookup walks its full chain.

candidatesif the first provider answersif every lookup walks the chain
25$3.939 credits$14140 credits
100$16160 credits$55550 credits
500$78780 credits$2732730 credits
1,000$1551550 credits$5455450 credits

Free before anything is charged

  • Turn the spec into a search

What moves the number

  • The channel. This play buys personal email, because these are candidates, and a work inbox is the wrong place to approach one. A personal address costs more to find than a work one.
  • Coverage on people search, work history and personal email. The chain stops at the first provider that answers, and only that provider bills.
  • How many candidates survive the free filters. Everything dropped before the paid steps costs nothing.
  • The scoring and drafting steps run on the metered agent, charged on what they read and write rather than per candidate, so they sit outside this table.
  • Providers you connect with your own key. Those calls bill your account, not your credits.

An estimate, not a quote, priced at the volume credit rate. Your agent sizes the run against your own workspace and tells you what it will cost before it spends anything.

What the flag is, and what it is not

Recruiters moving off LinkedIn Recruiter ask about this filter before anything else, so here is the plain answer. There is an open-to-work search, it works, and it is not the one you had.

The filter you had includes a private setting, which members share only with LinkedIn's own recruiter product. Nobody outside LinkedIn can see that part. What exists outside is the public version: the badge a person chose to show everyone, as recorded by one people database, along with the things people write when they are looking. "Seeking my next role" in a headline. A contract end date. A post saying they are free from next month.

That is a smaller pool than the one you had, and a more deliberate one. Someone who shows the badge publicly has decided their employer can know. For a contract role, an urgent backfill or a volume desk, those are the first people to call.

What you get back

A CSV ranked against the spec, one row per person: current title and employer, dated history, the score and its reason, and a column naming the signal they showed, whether badge, profile wording, post or a recent end date. Personal email where one was found, LinkedIn profile for everyone. Nobody has been contacted.

Variations worth knowing

Tenure instead of the flag. The same database filters on time with the current employer. People a couple of years into a role who show no flag are often more movable than flagged people everyone is calling. Ask for both lists and compare them.

Contract desks. Add the contractor wording to the read step: "available from", "contract ending", "immediately available". For contractors the profile text is often a better signal than the badge.

Widen to the passive market. When the flagged pool is thin, the next step is a full talent map, where open-to-work is one angle among five. For one role and a standard search, start from the job spec.

Where this goes wrong

Searching the flag alone. Without titles and a location it matches a pool the size of a country. The play always pairs it with the spec, and you should keep it that way if you rewrite the prompt.

Reading no flag as not interested. Most people who would move never show a badge. This play finds the ones who raised a hand. It says nothing about everyone else.

Trusting a stale badge. A database records what it saw on its last visit. The work history check catches people who have started a job since. It cannot catch someone who accepted an offer yesterday.

Filtering on anything protected. Availability is a fair criterion. Age, family circumstances and the reason someone is out of work are not, and the play does not score on them.

Questions

Is this the same as the open-to-work filter in LinkedIn Recruiter?

No, and it is worth being exact about the difference. A LinkedIn member can show that they are open to everyone, as the visible badge, or only to people using LinkedIn's own recruiter product. The second setting is private and stays inside LinkedIn. No outside tool reads it, this one included. What the play searches is the public badge as one people database has recorded it, plus what people write on their profiles and in posts. Expect a smaller pool than the filter you had.

How fresh is the flag?

As fresh as the database's last look at that profile, which varies by person and is not shown. That is why the play pulls dated work history before scoring. Someone who has started a job since is marked, and you do not pay for contact details on people who have already landed.

Why does only one source carry it?

Because only one of the people databases in the stack records profile badges at all. The practical effect is that a thin result cannot be topped up by another provider running the same filter. When the flagged pool is small, the honest next move is a normal search ranked on other signs of movability, not a looser flag search.

Are open-to-work candidates weaker candidates?

No, but they are a particular slice. The flag skews towards people between jobs, contractors coming off an assignment and people whose employer is cutting. Plenty of them are excellent. They are also the most contacted people in any search, so speed and a specific message matter more here than anywhere else.

Can I run this every week for a standing role?

Yes, once a manual run has shown that the filters are right. It converts into a scheduled workflow that repeats the search and leaves the list waiting in your workspace. It does not contact anyone. Prove it by hand first, because a loose title filter repeated every week is a weekly bill for the wrong people.