Industry filtering
The filters behind the word "industry" — the person's own industry, their employers' industries current or past, and the company side — and how to pick values that never silently match nothing.
"Industry" means two different things in people data: the industry on the person's own profile, and the industry of the companies they work for. Most searches actually want the second one. This page separates the filters, shows which expresses each, and covers how to pick valid industry values, including which values are worth showing your users.
Which filter is which
| Filter | What it matches | Where |
|---|---|---|
industryV2 | The industry on the person's own profile, in Fiber's standard categories | People search |
experienceIndustry | The industries of the companies someone has worked at, current or past | People search |
linkedinIndustries | The employer's industry, in current LinkedIn industry names | Company search, combined search (companyParams) |
industriesV2 | The employer's industry, in Fiber's broader standard categories | Company search, combined search (companyParams) |
industry | Deprecated person-level filter — use industryV2 | People search |
Providers in this space mostly derive industry from the employer. If your audience is "people who work in industry X" (what most industry targeting means), that's an employer-industry search.
The person's own industry
The industryV2 filter on people search matches the industry carried on the
person's profile, using the same standard categories as company search —
Healthcare, Finance, Software, and so on.
Use it when the question is about the person: "people whose profile says healthcare", regardless of where they work.
industry (the person filter's older form) is deprecated. It uses a
separate person-only value list that doesn't alias with industryV2, and
profiles without a value are excluded by any industry filter, so it
under-counts. Switch to industryV2 and re-pick values from the standard
categories.
The employer's industry
For people at companies in an industry, use combined search and put the industry filter on the company side:
{
"companyParams": {
"linkedinIndustries": { "anyOf": ["Banking"] }
},
"profileParams": {
"country3LetterCode": { "anyOf": ["FRA"] },
"jobTitleV3": { "anyOf": [{ "type": "functional", "seniority": ["manager", "director"] }] }
}
}The employer-side filter answers a different question than the person-level one, and it combines with your other company conditions (size, location, funding) in the same query.
Choose between the two employer-side filters:
linkedinIndustriesis precise. Current LinkedIn industry names, hundreds of them. One broad concept often spans several names: retail includes Retail, Retail Groceries, Online and Mail Order Retail, Retail Apparel and Fashion and more. Send all that apply.industriesV2is broader. Fiber's standardized categories group those names, so one value covers the whole concept. Start here, narrow withlinkedinIndustriesif you need precision.
The industries of someone's employers
When the question is "has worked in this industry" (not "works there
now"), people search has a direct filter for it. experienceIndustry
matches the industries of a person's employers, scoped by jobStatus: the
current employer, past employers, or either. Same standard categories as
industriesV2:
{
"experienceIndustry": { "anyOf": ["Software"] },
"jobStatus": { "status": "previously-employed" }
}That finds people who used to work at software companies: a
software-company alumni search in one people query, no company-side filter
needed. More on the work-experience filters and how jobStatus scopes them
in advanced work experience search.
Picking valid values
Get industry names from the industries list
(GET /v1/enums/industries, free). It returns every valid name for all
three lists, plus companyCounts, the number of companies behind each
value.
A linkedinIndustries value must match exactly. A misspelled or retired
name (for example the older "Computer Software" instead of "Software
Development") returns zero results with no error or warning. Build
your lists from the industries list, never from memory.
Check companyCounts before you expose a value in your own filter UI.
The enum list is complete, but some values have only a handful of companies
behind them; a filter option with eleven matching companies is a no-op for
your users and generates support tickets. Hide values whose count is too
small to matter for your audience, and show the count alongside each option
so users can see what they're selecting.
Which one when
| You want | Use |
|---|---|
| People at companies in an industry (the common case) | Combined search, industriesV2 or linkedinIndustries on companyParams |
| Companies in an industry | Company search, same filters |
| People by the industry on their own profile | People search, industryV2 |
| People who have worked in an industry, current or past | People search, experienceIndustry with jobStatus |
| A broad category, fast | industriesV2 (or industryV2 / experienceIndustry on people search) |
| Exact industry names | linkedinIndustries, values from the industries list |
| Official industry codes | naicsCodes on company search |
Filtering by NAICS code
If your systems use NAICS codes, filter companies with naicsCodes instead of
mapping codes to industry names. Matching is by prefix: "5415" matches
every company whose code starts with 5415 (such as 541511 and 541512), so you
can filter at any level of the hierarchy. It takes anyOf, allOf, and
noneOf:
{
"searchParams": {
"naicsCodes": { "anyOf": ["5415", "5182"], "noneOf": ["518210"] }
}
}The full list of 2022 NAICS codes is free:
| Operation | What it does | Reference |
|---|---|---|
| NAICS codes | Every 2022 NAICS code with its title (free) | getNaicsCodes |
Excluding an industry
linkedinIndustries takes noneOf as well as anyOf, so you can keep an
industry out of an otherwise broad search, for example "software companies,
but not staffing and recruiting":
{
"searchParams": {
"linkedinIndustries": {
"anyOf": ["Software Development"],
"noneOf": ["Staffing and Recruiting"]
}
}
}Related
- Advanced work experience search —
experienceIndustry,jobCategories, and the other per-role filters - Getting accurate results from search — filter semantics and worked examples
- Typeaheads — resolve names to exact values
- Search counts — exact vs estimated numbers
- Search — filters, ordering, pagination
Search counts
Count matching companies and people before you pull a single result — what's exact, what's estimated, and the two caveats that matter when a count feeds a report or a benchmark.
Migrating from another data provider
Translation tables for the filter vocabularies that differ between providers (departments, seniority levels, job-title matching), so a search means the same thing here as it did there.