What Is a Seniority Level in B2B Data?

A seniority level is a fixed category that says how high a person sits in a company, such as VP, Director or Manager. This page defines it, shows how job levels and seniority in B2B data are assigned, and shows the filters that use it in LeadOcean.

Key takeaways

• Seniority is a normalised label for the rank of someone's current role. A job title is free text.
• LeadOcean carries two layers: 6 job levels (coarse) and 12 seniority bands (finer). Use jobLevel for broad cuts and seniority for precision.
• Seniority answers "how high". Job function answers "which team". Combine them to pick a buyer.
• Filter values are exact strings. jobLevel is capitalised (VP), seniority is lowercase (vp).

What it is

A seniority level is a standard label for the rank of a person's current role, assigned from their job title so that "SVP, Growth" and "Vice President of Sales" land in the same bucket.

Job titles are free text. Companies invent them, translate them and inflate them. A "Head of Revenue" at a 10-person startup and at a bank are not the same job. Both can still carry one level, so you can filter on it.

Data providers solve this by mapping each title to a small list of levels. The list is not a standard. Names and bucket edges vary by provider, so check the enum values before you reuse a filter from another tool.

How it works

Seniority is derived, not typed in. The steps below show the usual path from a raw title to a filterable field.

1. Read the title. The source record holds a string such as "VP of Sales, EMEA".
2. Match keywords and patterns. Words like "chief", "vice president", "director" and "manager" map to a rank. Words like "assistant" or "intern" map lower.
3. Assign a band. The record gets one seniority value from a fixed list, for example vp.
4. Roll it up. Several bands collapse into a coarser job level. In LeadOcean, vp rolls up to the VP job level.
5. Store it on the record. You then filter on the field instead of searching title text.

Worked example. You want heads of sales in Canada. Searching the title "VP Sales" misses "Vice President, Revenue" and "SVP Commercial". Filtering jobLevel VP with jobFunction Sales & Business Development catches all three spellings. The title filter can then narrow further.

Two caveats apply before you trust the label. First, the level describes the current role only, not the person's career. Second, it says nothing about authority. A Director at a bank can hold more sign-off power than a VP at a startup.

Seniority has limits. A title that says nothing about rank, such as "Consultant" or "Partner Success", can land in unknown or Other. The label also lags a promotion until the record is refreshed. LeadOcean refreshes the dataset monthly, and each record carries its own fetched_at date.

Job level vs seniority

Job level and seniority are two views of the same idea at different resolution. LeadOcean has 6 job levels and 12 seniority bands, and the finer field lets you split groups the coarse one merges.

Counts show how the two relate. On 2026-10-01, a count with jobLevel C-Team and country US returned both c_suite and owner in its seniority breakdown. A count with jobLevel Staff and country LU returned entry and senior. So the coarse level can hide a real difference between an owner and a hired chief officer.

Seniority is also not job function. A VP of Engineering and a VP of Sales share a level and differ in function. Read what a job function is for the other half.

When it matters

Level changes who answers, who signs and how you write the message. Four situations come up most often.

Targeting a budget owner

If your product costs real money, aim at VP, Director or C-Team and skip Staff. Budget sits at the top of a team. A user-level contact can champion a tool but rarely approves it.

Writing to a small company

In a company of 1-10 people, the owner and founder is often the buyer and the VP level barely exists. For small accounts, filter seniority on owner, founder and c_suite. Pair it with employeeRange to keep the size honest.

Splitting a list into outreach tracks

Different levels want different messages. A CFO wants risk and cost. A Manager wants workload and tooling. Pull each level as its own list so the copy can differ.

Choosing between jobLevel and seniority

Start with jobLevel, because six values are easy to reason about. Move to seniority when a group is too mixed. C-Team, for example, covers both hired chief officers and owners. If you sell to founders, seniority lets you pull founder and owner and leave c_suite out.

How LeadOcean handles it

LeadOcean exposes seniority as two filters on search and export: jobLevel (6 values) and seniority (12 values). Both take arrays of exact strings, and you can pass them together with jobFunction, country and the rest of the 50 people filters.

Sizing is free. On 2026-10-01 these counts returned mailable people in the United States. Mailable means a verified, catch_all_valid or catch_all email:

Both filters work the same way on the API, covered in what a B2B data API is. Look up exact values first with the free list_enum_values MCP tool, or GET /v1/enums. Then send a count request. The count=true flag goes in the query string, not the JSON body.

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 '{
    "jobLevel": ["VP"],
    "jobFunction": ["Sales & Business Development"],
    "country": ["CA"],
    "limit": 1
  }'

The response has an empty data array and meta.countOnly set to true. meta.total is capped at 100,000. Drop count=true and raise limit to 100 to read rows, where 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. The Exports page in the app at app.leadocean.io has a filter builder and shows the record price before you start.

The database holds 693M people (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. If you are comparing sources by how well they filter, start with the best B2B databases or, for UK coverage, B2B data providers in the UK.

FAQ