How to Find a Data Scientist's Email Address (2026)

You find a data scientist's email by looking it up in a data source first and guessing from a name pattern only when the lookup is empty. A lookup returns an address someone has already tested. A guess is a coin flip you must verify.

Data scientist addresses come from four places. A data provider holds a work address it collected and checked. A paper, conference talk or GitHub profile sometimes lists an address, often a university or personal one. A name pattern gives you a guess. A company site rarely shows anything beyond a shared inbox.

Only the first is worth building a process around. The other three are fallbacks, and this guide follows that order.

Data scientists are individual contributors or team leads, not executives. They pick tools, run experiments and recommend what the team buys. They get vendor mail too, so a short, specific message works better, and a wrong address costs you sender reputation.

This guide uses the LeadOcean API. Every step has a request you can run.

TL;DR

• It takes about 15 minutes to size the audience, find one data scientist's address and read its status.
• The walkthrough spends about 4 records: up to 3 from the search and 1 from the reveal. Counts are free.
• Send only to verified, catch_all_valid or catch_all. Anything you guessed gets verified first.

Prerequisites

• A LeadOcean API key from app.leadocean.io. The free plan has 1,000 records, one-off, and no card.
• The key in your shell as $LEADOCEAN_API_KEY.
• curl and jq.
• A target company domain. The examples use acme.com.

export LEADOCEAN_API_KEY="paste-your-key-here"

Step 1: Size the data scientist audience for free

Count how many data scientists you can mail before you spend a record. Send count=true and limit=1 as query parameters. Arrays go comma-separated.

curl -s -G https://api.leadocean.io/v1/people/search \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  --data-urlencode "title=Data Scientist" \
  --data-urlencode "salesRegion=EMEA" \
  --data-urlencode "emailStatus=verified,catch_all_valid,catch_all" \
  --data-urlencode "count=true" \
  --data-urlencode "limit=1" | jq '.meta | {total, totalIsExact, countOnly}'

salesRegion takes NORAM, LATAM, EMEA or APAC. Swap in country=DE for one market. REST meta.total stops at 100,000, so a very large audience comes back as a floor with totalIsExact false.

Title values are keywords, so the count includes "Senior Data Scientist" and "Lead Data Scientist". We did not filter by job level, so every level is counted. Add employeeRange=201-500 to focus on mid-size companies.

Step 2: Find the data scientist at your target company

Search by company domain and title. The search returns a thin row with no address in it. The row carries a person_id and flags that say whether we hold an email.

curl -s https://api.leadocean.io/v1/people/search \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "domain": ["acme.com"],
    "title": ["Data Scientist"],
    "limit": 3
  }' | jq '.data[] | {person_id: .meta.source_ids.person_id, contact_data}'

Each person returned costs 1 record. Keep limit small. A company can have dozens of data scientists, so add "seniority": ["senior"] or a keywords filter such as "machine learning" to reach the right team.

Step 3: Reveal the address

Send the person_id to enrich with reveal_email set to true. Enrich takes exactly one of linkedin_url, email, phone or person_id. There is no name plus domain lookup, which is why Step 2 comes first.

curl -s https://api.leadocean.io/v1/people/enrich \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"person_id": "PERSON_ID_FROM_STEP_2", "reveal_email": true}' \
  | jq '.data.contact_data | {email_status, contact_emails}'

This costs 1 record. A person we hold nothing for is a 404 and costs nothing. If you only want a deliverable work address, GET /v2/people/email/work with the same person_id returns one current-employer address or null. It costs 1 record per call, even when it finds nothing.

Step 4: Read the status before you send

The status says how far to trust the address. verified was tested. catch_all_valid means we confirmed the mailbox on a domain that accepts everything. catch_all means the domain accepts everything and the mailbox is unproven.

curl -s https://api.leadocean.io/v1/people/enrich \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"person_id": "PERSON_ID_FROM_STEP_2", "reveal_email": true}' \
  | jq -r '.data.contact_data
    | select(.email_status | IN("verified","catch_all_valid","catch_all"))
    | .contact_emails[0].email'

Empty output means the status failed the filter. LeadOcean gives no refund for bounced emails, so this check is your only protection. Treat catch_all as sendable at low volume, not as proof. Our catch-all explainer covers why.

Step 5: Fall back to a name pattern

When the data holds no address, build candidates from the person's name and the company domain. These four shapes are common. Pick the one you can confirm from a known address at the same company.

first="jane"; last="doe"; domain="acme.com"
printf '%s\n' "$first@$domain" "$first.$last@$domain" "${first:0:1}$last@$domain" "${first:0:1}.$last@$domain"

Research-heavy teams sometimes use a university or lab domain, so the company pattern may not apply. A domain that accepts all mail cannot confirm any single mailbox, so a guess there stays a guess.

Never send to a candidate you have not verified. Run each one through an email verifier you trust first.

Step 6: Verify and send in small batches

Verify before the first send, then start small. A flagged sending domain hurts every later send.

Send 20 to 50 messages first and watch the bounce count. If more than a few bounce, stop and re-check the status filter in Step 4. Name their stack or a problem they own. A generic template reads as a mass blast.

What you get

Step 1 is free. We ran it on 2026-10-21 for each sales region with leadocean_count_leads, title Data Scientist, no level filter. The counts are mailable data scientists (verified, catch_all_valid or catch_all, the tool default), not every data scientist we hold.

Worldwide the same filter counted 109,027 mailable people across 25,396 employers, out of 304,366 matches with any email status. The four regions add up to less, because some records carry a country but no sales region. The REST API stops its total at 100,000, so the worldwide figure comes from the MCP tool.

Mailable data scientists are about a third of all matches. North America holds almost half the mailable audience.

A revealed person comes back in the shape below. This is the response shape from the API reference, with placeholder values.

{
  "success": true,
  "data": {
    "profile_data": { "profile_full_name": "Jane Doe", "profile_headline": "Data Scientist at Acme" },
    "contact_data": {
      "has_email": true,
      "email_status": "verified",
      "email_type": "work",
      "contact_emails": [
        { "email": "jane.doe@acme.com", "type": "work", "status": "verified" }
      ]
    }
  }
}

Troubleshooting

FAQ