What Is a Job Function in B2B Data?

A job function is the department or area of work a person belongs to, such as Sales, Engineering or Finance. This page defines the field, shows how it is assigned, and shows how to filter on it in LeadOcean.

Key takeaways

• A job function is a fixed category for the department of someone's current role. A job title is free text.
• Function answers "which team". Seniority answers "how high". Use both to pick a buyer.
• A function filter is cleaner than a title keyword search, because one function covers hundreds of title spellings.
• LeadOcean has 22 job functions, set with the jobFunction filter on search and export.

What it is

A job function is a standardised label for the department of a person's current role, chosen from a closed list so that records can be grouped and filtered.

Titles are messy. "Head of Demand Gen", "Growth Marketer" and "Marketing Ops Lead" are three strings. They sit in one function: Advertising & Marketing.

The function is a property of the role, not of the company. A finance manager at a software company is in Finance & Accounting, not in Information Technology.

LeadOcean has 22 values. Examples are Sales & Business Development, Engineering, Human Resources, Legal, Operations and Customer/Client Service. The list is closed, so values are exact strings.

How it works

A data provider reads the title and profile text, then maps the role to one category from the list. The mapping runs once per record, so you filter on a label instead of guessing at keywords.

1. Collect the title. The provider reads the current job title from the person's profile or another source.
2. Normalise it. Abbreviations and word order are cleaned up. "VP, Rev Ops" becomes a title the mapper can read.
3. Map to a function. The title and profile text point to one value from the closed list.
4. Store it as a field. The label sits on the record next to seniority, company and contact fields.
5. Filter on it. Your query passes the label. Every record with that label matches, whatever its title says.

A worked example

Say you sell an ad analytics tool to a fictional company, Acme. You want the marketing leaders at companies like it.

A title search for "marketing director" misses "Head of Demand Generation" and "Growth Lead". A function filter does not. You set jobFunction to Advertising & Marketing and jobLevel to VP.

On 2026-10-01 that filter pair, with country US, matched 44,808 mailable people. Mailable here means email status verified, catch_all_valid or catch_all, the count default. Titles were not used.

Mapping is never perfect. Some titles span two teams, and a few land in Other. Treat the function as a strong filter, then sort the final list by title.

Job function vs seniority vs job title

These three fields describe one person from three angles. People swap them, and that breaks lists.

jobLevel has 6 values: C-Team, VP, Director, Manager, Staff and Other. seniority is finer, with 12 bands. For more, read what a seniority level is.

Use function and level together. Function narrows to a team, and level narrows to the people who sign. Title is the last pass.

When it matters

Targeting a buyer persona

Your buyer is a team, not a title. A function filter reaches everyone on that team, including odd titles. Add a level to cut it down to the people with budget.

Sizing a market before you spend

A function plus a level gives a count in seconds. You see whether a segment has 400 people or 40,000 before you pull a row. Count calls are free.

Splitting a list by team

One account has several buyers. A security tool goes to Information Technology. A payments tool goes to Finance & Accounting. Filter by function and write one message per team.

Reading outcomes by function

Job moves and email quality differ by function. The report on job change rates by function and the page on mailable share by job function show how those differ.

How LeadOcean handles it

LeadOcean stores the function as a filter field, jobFunction. It takes an array of exact strings from the 22-value list. Search, count and export all accept it.

The values are case and punctuation sensitive. "Sales & Business Development" works. "Sales" does not. Check the list with list_enum_values on the MCP server, or GET /v1/enums.

This call sizes a segment for free. It sends count=true as a query parameter with limit set to 1. The body uses a flat JSON object.

curl -X POST "https://api.leadocean.io/v1/people/search?count=true" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jobFunction": ["Advertising & Marketing"],
    "jobLevel": ["VP"],
    "country": ["US"],
    "limit": 1
  }'

The response has an empty data array and meta.countOnly set to true. meta.total is capped at 100,000. Remove count=true and raise limit to 100 to pull rows. Each person returned counts as one record.

To pull a big list, send the same filters to POST /v1/exports, up to 50,000 rows per request. Or use the Exports page in the app at app.leadocean.io, which has a filter builder and shows the record price before you start.

The database holds 693M people and 63M companies (as of 2026-09-23). The free plan gives 1,000 records, one-off, with no card. Pro is $499 a month, flat. See pricing.

FAQ