> ## Documentation Index
> Fetch the complete documentation index at: https://docs.freshtalent.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Plays that work

> Concrete searches and Targets recruiters run on FreshTalent — filters the product actually supports.

Each play uses real filters (or natural language that compiles to them). After the search: put people on a List, start a Target, Accept who to keep, then read Monitoring.

## 1. Palantir FDE leavers

The canonical loop. People who were Forward-Deployed Engineers at Palantir and left in the last year and a half.

```text theme={"theme":{"light":"github-light","dark":"github-dark"}}
ex-palantir FDEs, left 18mo
```

Filters: `company=palantir`, `role_family=forward-deployed-engineer`, `company_left_min_months_ago=18`.

Then **Targets** → **Start people search**, **Accept** from **Pending Approval**, Settings → Notifications for **Open to work** and **Left company**.

## 2. Open to work / Between roles FDEs

```text theme={"theme":{"light":"github-light","dark":"github-dark"}}
FDEs open-to-work
```

or `forward-deployed between-roles`. Put matches on `hot` at **To contact** the same day.

## 3. FDEs exploring

People whose current LinkedIn profile evidence suggests openness to a new employment role, as assessed by FreshTalent's AI. Unchanged openness can qualify. Open to work and Between roles are separate flags.

```text theme={"theme":{"light":"github-light","dark":"github-dark"}}
ex-palantir FDEs exploring
```

or `FDEs exploring`. Filter: `exploring=true`. Hover over or select the **Exploring** badge for an AI explanation, then select highlighted text to inspect the supporting snapshots or changes. Read [how exploration detection works](/guides/availability#exploring).

## 4. Company orbit (Anduril, SpaceX, …)

Open **Companies**, pick a team, read **Current team** and **Recent leavers**. Then **Targets** → **Company** → **Start company search**. **Accept** engineers you would actually hire.

## 5. Sticky alumni (long tenure, then left)

People who were at a company long enough to be real operators, not tourists.

Filters: `company=palantir`, `min_company_months=36`, optional `company_left_min_months_ago`. **Start people search** on that query.

## 6. Available for hire in a city

Filters: `role_family=software-engineer`, `github_hireable=true`, `location=San Francisco` (or remote-friendly city). Notifications for **Open to work** and **Joined company**.

## 7. Skill / stack niche

Filters: skills as `Foundry` or `Foundry;Palantir` with match any/all. Combine with a role family so you are not boiling the ocean.

## Agent prompt (copy into Claude or Cursor)

After [connecting MCP](/mcp-setup). Tool names below are MCP identifiers — they map to Search, Lists, Targets, Monitoring:

```text theme={"theme":{"light":"github-light","dark":"github-dark"}}
Search for Palantir forward-deployed engineers who left at least 18 months ago.
Show me the display-line rows. Put the best 10 on a list called hot at stage to-contact.
Watch that query as "Palantir FDE leavers". Show me proposed members I have not admitted yet.
When you are done, pull events since 24h for left_company and open_to_work.
```

That should resolve to `search` → `collect` → `watch` → `events`.