Former Employees Finder — Company Alumni, Founders & Execs

What does Former Employees Finder do?

Former Employees Finder turns a company website domain into its alumni list: people who used to work at that company and work somewhere else now. Enter stripe.com and get former Stripe employees with their LinkedIn profile URL, current job title, current company and location.

It is built for sales teams prospecting ex-employees of a customer or a competitor, recruiters sourcing from a company's alumni, and investors tracking where a team went.

• One or more company domains in, one row per former employee out.
• Every row says where the person works now: title, company, company domain, seniority.
• People who only changed roles inside the company are left out. A promotion closes one position and opens another, and without this rule a quarter to two fifths of "former" matches are current staff.
• A free preview names the company each domain resolved to and counts its former employees before you pay for anything.
• Domains that are not on record, or that resolve to something that is not named like the domain, come back as free rows that say why.
• Runs from the Apify Console, the API, a schedule, or an MCP client. No cookies and no login.

What data do you get for each former employee?

Field	Example	Filled
fullName	Jane Doe	every row
linkedinUrl	https://linkedin.com/in/jane-doe-example	every row
headline	VP Sales at Acme Analytics	most rows
currentTitle	VP Sales	when a current job title is on record
currentCompany	Acme Analytics	when the current employer is on record (151 of 160 rows in a test run)
currentCompanyDomain	acme-analytics.example	when the employer's site is on record
currentSeniority	vp	one of cxo, vp, director, manager, founder, other
currentRoleStartYear	2024	the year the current job started: the closest thing on the row to a leaving date
formerCompany	Stripe	every row: the company this person was found under
formerCompanyDomain	stripe.com	every row: the domain you entered
location, countryCode	Austin, Texas, United States, us	most rows
hasWorkEmail, hasPersonalEmail	true, false	whether an address of that kind is on record for the person
updatedAt, _freshness	2026-03-17T03:29:17Z, updated_1y	when the record was last refreshed
_status, _input	found, {"domain":"stripe.com"}	every row

What is not on the row: the job title the person held at the former company and the dates they worked there. The list is built from current-position data, so a row proves "used to work there, works elsewhere now" without carrying the old role. When you need the full career history for a shortlist, pass the linkedinUrl column to Profile Lookup.

How do you get a list of a company's former employees?

1. Enter one or more company website domains (stripe.com, up to 20 per run).
2. Press Start with the preview on. You get one free row per company: the company name the domain resolved to, its headcount, and how many former employees are on record.
3. If the company and the number look right, turn the preview off, set the maximum people per company, and run again. Export the dataset as CSV, Excel or JSON, or read it through the API.

How much does it cost to find former employees of a company?

Event	Price	When
Alumni page (up to 50 distinct people)	$0.10	after the rows have landed in your dataset
Count preview	$0	always
Empty result, unknown domain, ambiguous domain, invalid entry	$0	always

That is about $2 per 1,000 former employees. Pages are counted per company: 120 people from one company are three pages ($0.30), and a company with 8 former employees on record is one page ($0.10). maxResults caps the people per company, so the most a run can cost is known before it starts. The platform's Actor start event applies to every run and is shown on the pricing tab.

A page means fifty different people. The same person can be on record more than once; repeats are dropped and never count toward a page.

Input

{
  "companyDomains": ["stripe.com", "n26.com"],
  "previewOnly": false,
  "maxResults": 100,
  "countries": ["us"],
  "leftAfterYear": 2024,
  "seniority": ["cxo", "vp", "director"]
}

Field	What it does
companyDomains	Required. Company website domains, without a path. Up to 20.
previewOnly	On by default in the Console: free count per company instead of rows.
maxResults	People per company. Default 100, maximum 50,000.
countries	Where the former employees live now, as two-letter codes, up to 5. Empty means every country.
leftAfterYear	Keep people whose last day at the company falls in this year or later. People with no end date on record are left out when this is set.
onlyWithCurrentEmployer	On by default: every row has a current job on record. Turn off to include people with none.
titleKeywords	Words to match in the current job title.
seniority	Seniority of the current role: cxo, vp, director, manager, founder, other.
pastTitleKeywords	Words to match in any past job title of the person. The match is not tied to the job at this company.

When countries is empty the rows arrive in country-code order. A capped run then fills up with the alphabetically first countries, so set the countries you care about if you only want part of the list.

Output

A found row:

{
  "_status": "found",
  "_input": { "domain": "stripe.com" },
  "_freshness": "updated_1y",
  "fullName": "Jane Doe",
  "linkedinUrl": "https://linkedin.com/in/jane-doe-example",
  "headline": "VP Sales at Acme Analytics",
  "currentTitle": "VP Sales",
  "currentCompany": "Acme Analytics",
  "currentCompanyDomain": "acme-analytics.example",
  "currentSeniority": "vp",
  "currentRoleStartYear": 2024,
  "formerCompany": "Stripe",
  "formerCompanyDomain": "stripe.com",
  "location": "Austin, Texas, United States",
  "countryCode": "us",
  "hasWorkEmail": true,
  "hasPersonalEmail": false,
  "updatedAt": "2026-03-17T03:29:17.804Z"
}

A miss, free of charge:

{
  "_status": "unresolved_domain",
  "_input": { "domain": "acme-analytics.example" },
  "_error": "No company on record under this website domain. Check the spelling, or use the domain of the company's main site."
}

The free preview row:

{
  "_status": "preview",
  "_input": { "domain": "stripe.com" },
  "formerCompany": "Stripe",
  "formerCompanyDomain": "stripe.com",
  "formerCompanyEmployees": 17285,
  "_total": 7276,
  "_totalCapped": false
}

Other statuses, all free: ambiguous (the domain resolved to a record that is not named like the domain; the row says which), domain_too_broad (a hosting or mail platform that many unrelated businesses list as their site), invalid (not a domain), no_results (the company resolved and nobody matched your filters).

Can I use Former Employees Finder through the API, MCP or automation tools?

• API: start a run and read the dataset with the Apify API or the JavaScript and Python clients.
• MCP: add the Actor to the Apify MCP server and call it from Claude, ChatGPT or any MCP client.
• Make, n8n, Zapier: use the Apify connector to run the Actor and pass rows on.
• Schedules: run the same domains monthly and compare datasets to spot new leavers.

What is a company alumni list used for?

• Sales: people who used your product at their last company and now work somewhere that does not have it.
• Competitive prospecting: former employees of a competitor know the category and already sit at other companies.
• Recruiting: alumni of a company whose training you trust, filtered by current seniority and country.
• Investing and research: where a company's former staff went and who founded something (seniority: ["founder"]).

FAQ

How do I find former employees of a company?

Enter the company's website domain, keep the preview on and run. The preview row shows the company name and how many former employees are on record. Turn the preview off to get the people.

How accurate is the list?

Measured on our test sample on 2026-09-30, three companies (one large US technology company, one mid-size software company, one European bank): of 40 rows checked against the person's full profile record, 35 (87.5%) showed only closed positions at the company, 2 (5%) still showed an open position there, and 3 (7.5%) could not be confirmed because the current record no longer names that position. Two more sampled rows pointed at profiles that had since been removed. One of the two "still there" rows had no current job on record, a case the default onlyWithCurrentEmployer setting now leaves out.

A move from a parent company to a subsidiary with its own company page counts as leaving.

Which company does a domain resolve to?

A domain is resolved to one employer: the largest record on file that is named like the domain. Many unrelated records can list a well-known site as their own, so a record that is not named like the domain is refused as a free ambiguous row instead of being searched. On 18 well-known company domains we tried on 2026-09-30, 15 resolved to an employer and 3 came back as free refusals. Always read formerCompany and formerCompanyEmployees in the free preview before buying pages: a company can be on record under a different domain than the one you expect, and a small headcount next to a famous name means the domain belongs to a side entity.

Am I charged when nothing is found?

No. Domains that do not resolve, ambiguous domains, invalid entries, the count preview and searches that match nobody are all free rows. Only pages of delivered people are charged.

Can I run it in bulk or from a CSV?

Up to 20 domains per run, up to 50,000 people per company. For a longer list of companies, split it across runs through the API or a schedule. CSV upload is not part of this Actor.

Does it need cookies, a login or an API key?

No. The Actor does not log in to or crawl any website at run time. Answers come from our own database of professional profile records.

How fresh is the data?

It is a snapshot, not a live feed. In our test sample on 2026-09-30 the most recent departures recorded were from April 2026; people who left after that are mostly not on the list yet. Records are refreshed on different dates: 34 of 84 sampled rows had been updated within the previous 12 months. Each row carries updatedAt and a _freshness bucket so you can filter.

Can I get only recent leavers?

Set leftAfterYear. The filter works on the year a person's position at the company ended, so 2025 returns people who left in 2025 or later. People whose end date is not on record are left out when the filter is set.

Why is the preview count higher than the rows I received?

The count is of records, and one person can be on record more than once. The run delivers each person once, so a full list can come out shorter than the preview.

Is it legal to build a list of former employees?

The rows are business profile data: name, public profile link, employer and job title. Whether you may use them, and how, depends on your purpose and the law that applies to you. Read the permitted-use section below; you are responsible for having a lawful basis, particularly before contacting people in the EU or the UK.

Use Former Employees Finder with AI agents and MCP

This Actor works as a tool for AI agents. Add it to Claude, ChatGPT, Cursor or any other MCP client through the Apify MCP server:

https://mcp.apify.com?tools=b2bsearch/former-employees-finder

• Fast enough for a tool call. A small request finishes in seconds, so the agent gets its answer inside one call.
• Free count first. "previewOnly": true returns the number of matches and charges nothing — let the agent size the segment before it buys rows.
• The agent pays only for results. Prices are per result (see the pricing section above) and every miss is a free row. Cap what one call may spend with maxTotalChargeUsd.
• Rows explain themselves. Each row has a _status; a row that is not a result says why in _error, so the agent can decide what to do next without guessing.
• Bounded cost. maxResults limits how many rows one call can deliver and bill.

Input an agent can send as is:

{
  "companyDomains": [
    "stripe.com"
  ],
  "countries": [
    "us"
  ]
}

The same Actor is available as a tool in LangChain, CrewAI and the OpenAI Agents SDK, and as a step in n8n, Make and Zapier through the Apify integrations.

Related Actors: which one should you use?

Need	Actor
Email → LinkedIn profile URL	Email to LinkedIn
Email → current company and job title	Email to Company
Email → phone numbers on record	Email to Phone
Email → X (Twitter) profile	Email to Twitter
Email → Facebook profile	Email to Facebook
Email → full professional profile	Reverse Email Lookup
LinkedIn URL → full profile	Profile Lookup
LinkedIn URL → email addresses on record	LinkedIn Email Finder
LinkedIn URL → phone numbers on record	LinkedIn to Phone
X (Twitter) handle → email	Twitter to Email
X (Twitter) handle → LinkedIn profile	Twitter to LinkedIn
X (Twitter) handle → phone numbers on record	Twitter to Phone
Facebook profile → email	Facebook to Email
Facebook profile → phone numbers on record	Facebook to Phone
Facebook profile → LinkedIn profile	Facebook to LinkedIn
GitHub username → email	GitHub to Email
GitHub username → LinkedIn profile	GitHub to LinkedIn
Name + company domain → work email	Work Email Finder
Name + company domain → LinkedIn profile	Name to Profile
Name + company domain → phone numbers on record	Name to Phone
Handle on any of three networks → full profile	Social Handle Lookup
Company domain → company record	Domain to Company
Company domain → decision makers	Decision Maker Finder by Domain
Company domain → current employees	Company Employees
Company domain → former employees	Former Employees Finder (this Actor)
Filters → list of people	People Database Search
Filters → leads with an email, from $1.50/1k	B2B Leads Finder
Filters → list of companies	Company Database Search
CSV of emails, URLs or names → profiles in bulk	Bulk People Enrichment

Free Apify plan

A run started from a free Apify plan delivers the first 100 results and stops; the run's status line says so. Any paid Apify plan lifts the cap. The rows are the same rows a paid run returns.

Feedback and reviews

How did it go? A rating in the Reviews tab of this Actor tells the next buyer what to expect; we read every word, good or bad. Got a wrong or stale row? Open the Issues tab with the run ID. Issues are public, so leave out emails, phones and names; the run ID is enough for us to find the row. We check every report, fix what is ours to fix and answer in the thread.

Disclaimer and permitted use

Independent product. This Actor is an independent tool. It is not affiliated with, endorsed by, or sponsored by LinkedIn Corporation. LinkedIn® is a trademark of its owner. It is named here only to describe the kind of public profile link this Actor returns.

No platform access. This Actor does not log in to or crawl LinkedIn or any other service. Every answer comes from our own database of business profile records. It never returns passwords, direct messages, or content from accounts that are not public.

Permitted use. Business-to-business purposes only: sales prospecting, recruiting outreach, CRM enrichment, and market research. You may not use this Actor or its output to:

• stalk, harass, threaten, dox or publicly expose any person;
• decide on anyone's eligibility for credit, employment, housing or insurance. This Actor is not a consumer reporting agency and its output is not a consumer report under the U.S. Fair Credit Reporting Act;
• send unsolicited bulk messages, or place autodialed or prerecorded calls or texts without the consent the law requires;
• profile people by health, religion, political opinion, sexual orientation, ethnicity or union membership;
• build or resell a contact database from the results.

Your responsibilities. You decide which companies to look up and what to do with the result. You are responsible for having a lawful basis for that use and for complying with the laws that apply to you, including GDPR and UK GDPR, ePrivacy and PECR, CCPA/CPRA, CAN-SPAM, and the TCPA and Do Not Call rules. Honor every opt-out you receive.

Removal requests. To have a person's data removed, open an issue on this Actor with only the profile link. Nothing else is needed, and the record is removed from every listing.

Accuracy. Records can be incomplete or out of date, and a person listed as a former employee may have returned to the company since. Output is provided as is. Check before you rely on it.