How to find former employees of a company
On a professional network, filter people search by past company. For a list, run a person role search with the company's domain, role_is_current false and a window on the role end date; each match shows the past role and the person's current company.
Why you want them
- Boomerang hires: people who left two years ago know the product and the culture.
- Expert networks: a former employee of a target company is the expert a research call wants.
- References and warm paths: an alum who now works at your prospect.
- Backfill signals: when a senior person leaves, a recruiter has a role to fill.
- Churn risk: your champion at an account left, and nobody told the account team.
Page 1 for this search is a professional network's past-company filter and little else (aluminati, Apr 20, 2023, searches by name and photo). None of it answers when they left, what they did, or where they went.
The manual route
In people search, open the filters and set Past company to the target. Sales Navigator adds Past job title and lets you save the search. It works for one company, one search at a time, and you cannot export the result or put a date on when people left.
By API: the same search with the role flipped
A person role search filters roles, not just people. Set organization_domains to the target, role_is_current to false, and the match is anyone whose past roles include that company. The request fields role_position_start_date and role_position_end_date exist in the API reference; use the end date for the window.
Former employees, left since a date
curl -X POST https://api-v2.forager.ai/api/{account_id}/datastorage/person_role_search/ \ -H "X-API-KEY: $FORAGER_API_KEY" \ -H "Content-Type: application/json" \ -d '{"organization_domains":["example.com"],"role_is_current":false,"role_position_end_date":"2026-01-01","role_title":"\"Account Executive\" OR \"Sales\"","page":1}'
import os, requests r = requests.post( f"https://api-v2.forager.ai/api/{os.environ['FORAGER_ACCOUNT_ID']}/datastorage/person_role_search/", headers={"X-API-KEY": os.environ["FORAGER_API_KEY"]}, json={"organization_domains": ["example.com"], "role_is_current": False, "role_position_end_date": "2026-01-01", "role_title": "\"Account Executive\" OR \"Sales\"", "page": 1}, timeout=30, ) r.raise_for_status() data = r.json() if r.content else [] # an empty body means nothing was found
// illustrative values, not a record
{ "search_results": [{ "person": { "id": 123, "full_name": "Jane Doe", "linkedin_info": { "public_identifier": "jane-doe-example" } }, "role_title": "Account Executive", "organization": { "name": "Example Corp", "domain": "example.com" } }], "total_search_results": 17 } A search costs 1 credit per request. The exact filter shape for a date range (a single date or a start and end pair) is in the operation reference; check it when you write the request.
Reading a match
Each hit carries the role that matched (the past role at the target, with its title) and the person. The person's current organization is the "where they went" answer; take the person id into a person detail lookup when you need the full role history with dates.
Narrow by what they did
- role_title as a boolean query: the function they had at the target, not the one they have now.
- Seniority words for the leaders who left.
- person_locations when the job is local.
- role_years_on_position_start to require a minimum tenure, which filters out three-month stints.
Watch for leavers
- Run the search on a schedule with the end-date window sliding forward from your last run.
- Dedupe by person id against the leavers you already stored.
- Alert on the new ids: a backfill signal for recruiters, a churn flag for the account team.
From a match to a conversation
The old work address died with the job, so do not look it up. A personal email follows the person: send the person id to the personal emails lookup for a webmail address with a validation status, 5 credits when one is returned. The personal email guide covers the consent line that goes with it.
At scale
To do this across a whole market, license the people data feed: every person record carries its roles with start and end dates, so "left company X between these dates" is a SQL query in your warehouse, not a search per company.
The pieces this guide uses
Recipes
- $5 free credits
- No credit card
- Run your sample
Questions about this guide
Can I see when someone left a company?
Yes. Role records carry a position end date, and the role search accepts role_position_end_date as a filter. A person detail lookup returns the full role history with dates for one person.
Can I find former employees by job title?
Yes. With role_is_current false, the role_title query applies to the past role at the target company, so "Account Executive" OR "Sales" finds the former sales team.
How do I contact a former employee?
On a personal email or mobile, which follow the person. The old work address is dead. Send the person id to the personal emails lookup or the phone numbers lookup; each is charged only when it returns something.
Does the data show where they went next?
Yes. Each match carries the person, and their current organization is on the record. For the full sequence of roles with dates, run a person detail lookup with the person id.
Is this allowed under GDPR?
Role history is professional data people publish about themselves, and the rules for personal data still apply: a lawful basis, a narrow purpose, an opt-out you honor. Bring the details to a call with our team before you build a leaver watch in the EU.
What does people search cost for teams following this guide?
People search: people search 1 credit per request and people search: role details 1 credit per request, charged whether or not data comes back. 1,000 search requests use 1,000 credits: about $13 of Starter credits month to month, or about $10 on Pro with yearly billing. Self-serve plans are Starter, Growth, Pro and Scale. See plans and prices
Am I charged when nothing is found?
Yes. People search is charged per request, whether or not data comes back. Only mobile and email lookups are free when nothing is found, so try your inputs on a small run before you scale.
Can teams following this guide test people search for free?
Yes. Create a free account at app.forager.ai: it comes with $5 in free credits and an API key, and there is no credit card to sign up. Run it on records you already know, or book a demo and send us a list: we run it and show you what we find.
How do I know the data is right?
The test that counts is your own: send a list of profiles you care about. We run it and show you what we find, number by number, so you can measure hit rate and connect rate yourself.
How is the data sourced, and what about privacy?
Bring your legal and security questions to a call with our team, and we take you through how Forager data is sourced and the terms that cover people search for teams following this guide. Forager's privacy policy is public, and anyone can send a request about their own personal data through the consumer rights form on forager.ai.
Do I need a subscription?
Not to test: a free account comes with $5 in credits. To keep using people search, choose a monthly or yearly plan. Monthly plans cancel anytime and unused credits roll over; yearly plans grant all credits upfront and cost 10% less. Larger volumes are agreed with our team.
Where can I use Forager people search?
Native in Clay and Zapier, partner-built in Deepline and Cargo, delivered as a data share to Snowflake, Databricks and Amazon S3 and called through the API from your own code, Make, n8n and Google BigQuery. Everything else connects through the REST API with one API key.
Written answers are not available right now. The matching pages above still help, or book a demo and ask the team.
- $5 free credits
- No credit card
- Run your sample
Keep reading
Glossary
Best-of guides
Related guides
Sources
- Forager docs: People search by job title and company (read Nov 1, 2026)
- Forager docs: OpenAPI reference (role_position_start_date, role_position_end_date) (read Nov 1, 2026)
- Forager docs: Person feed schema (read Nov 1, 2026)
- Forager docs: API credits and pricing (read Nov 1, 2026)
- aluminati.net: How to find former employees on LinkedIn (Apr 20, 2023, updated May 12, 2023) (read Nov 1, 2026)