# March 2026 ## Multi-source Company Data {% updates format="full" %} {% update date="2026-03-02" %} ## Adding new fields The update introduces new workforce metrics, identifiers, and parent company mapping fields. | Data field | Description | Data type | | ------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------- | | `departures_count` | Count of employees who left the company in the current month. Set to `0` when there are no departures | Integer | | `departures_count_by_month` | Historical monthly departures count with corresponding dates | Array of structs | | `departures_count_by_month.departures_count` | Number of employee departures | Long | | `departures_count_by_month.date` | Date for departure count | String | | `employee_attrition_rate` | Current month attrition rate calculated as (`departures_count` / `employees_count_inferred`) \* 100. Value is `null` when `employees_count_inferred` is `0` or `null` | Double | | `employee_attrition_rate_by_month` | Historical monthly attrition rates with corresponding dates | Array of structs | | `employee_attrition_rate_by_month.attrition_rate` | Attrition rate | Double | | `employee_attrition_rate_by_month.date` | Date for attrition rate | String | | `professional_network_shorthand_name` | Professional network URL shorthand name | String | | `canonical_professional_network_shorthand_name` | The most recent version of `professional_network_shorthand_name` | String | | `parent_company_information.parent_company_id` | Matched parent company ID | String | | {% endupdate %} | | | | {% endupdates %} | | | ## Multi-source Employee Data {% updates format="full" %} {% update date="2026-03-02" %} ## Adding a new field `profile_score` is a model-derived quality score for our multi-source employee dataset, calculated from Professional network profiles. Using our profile dataset collection and integrated change-tracking data, we trained a model that performs score analysis across various profile features to produce a single numeric quality indicator per profile. | Data field | Description | Data type | | --------------- | ----------------------------------------------------------------------------------------------------------------------- | --------- | | `profile_score` | Model-derived employee profile quality score based on profile completeness and activity signals. Score range: `0` – `1` | `Double` | *** #### How does it work? The model evaluates profile features and assigns each an importance weight across three tiers: **1. Key drivers** – carry the most weight; reflect core professional completeness. * **Connections, experience, and education** – count and dates are the strongest signals of profile engagement, capturing depth of professional history and academic background. * **Activity count** – posting, liking, and commenting activity serves as a key indicator of genuine platform engagement vs. automated or inactive accounts. * **Image authenticity** – whether the profile photo is identified as real or not. **2. Profile completeness** – add meaningful but smaller increments; capture profile richness and behavioral signals. * Profile richness: headline length, summary presence, skills, websites, languages, and groups. * Change signals: photo updates, activity changes, experience edits, and follower count changes. * Naming patterns: casing, formatting, and dash usage in titles. * Related data: similar profiles count, school/company URLs, job title and description presence. **3. Minor / negligible factors** – minimal individual impact but contribute to the final score. * Certifications, awards, volunteering, recommendations, publications, patents, courses, projects, and various other metadata fields. *** #### Key takeaways Use the score ranges below as a practical guide for evaluating profile reliability: | Score range | Interpretation | | ---------------- | ------------------------------------------------------------------------------ | | `0.0` – `0.20` | Low quality. Profiles to approach with caution or exclude. | | `0.21` – `0.40` | Moderate quality. More likely to be real users than bots or inactive accounts. | | `0.40` – `1.0` | Good to high quality. Growing signal of a genuine, active user. | | {% endupdate %} | | | {% endupdates %} | | ## Base Employee Data {% updates format="full" %} {% update date="2026-03-04" %} ## Added a new field The `inferred_skills` contains skills derived from structured and contextual profile information. | Data field | Description | Data type | | ----------------- | ------------------------------------------------------------------ | ---------------- | | `inferred_skills` | Lists employees' skills based on the descriptions from the profile | Array of strings | | {% endupdate %} | | | {% update date="2026-04-01" %} ## Scheduled removal: `hidden_details` The `hidden_details` category will be removed from the Base Employee schema starting with the April 2026 dump. Updates to the data aggregation pipeline now ensure that all necessary information is properly populated in the standard schema fields. As a result, the separate `hidden_details` identifier has become redundant. ### **Removed fields** | Data field | Data type | | ---------------------------------- | ---------------- | | `hidden_details` | Array of objects | | `hidden_details.hidden_collection` | String | | {% endupdate %} | | | {% endupdates %} | | ## Employee Posts Data {% updates format="full" %} {% update date="2026-03-02" %} ## Adding new fields The `created_at` field introduces a clear temporal reference point: when the employee post record was scraped and recorded. The `reshared_post.company_id` field links posts to a specific company by its ID. | `created_at` | The date and time when the employee post record was scraped and recorded in `ISO 8601` format | String (date) | | -------------------------- | --------------------------------------------------------------------------------------------- | ------------- | | `reshared_post.company_id` | The `company_id` of the reshared post in case the post belongs to a company | Integer | | {% endupdate %} | | | | {% endupdates %} | | | ## Clean Company Data {% updates format="full" %} {% update date="2026-02-25" %} ## \[Reminder] Adding and fixing fields #### Added fields We are adding new company HQ location fields. | Data field | Description | Data type | | ----------------------------------- | ------------------------------------------------- | --------- | | `company_location_hq_country_iso_2` | ISO 2-letter country code for company HQ location | String | | `company_location_hq_country_iso_3` | ISO 3-letter country code for company HQ location | String | | `company_location_hq_state` | Company HQ state | String | | `company_location_hq_city` | Company HQ city | String | #### Fixed fields We are fixing inaccuracies in Clean Company schema, specifically `company_locations_full` nested fields, that were referenced in the December 2025 schema update but were not fully launched. The issue has now been resolved, and the previously missing fields are available in the Clean Company schema.
Data fieldDescriptionData type
company_locations_full.countryFixed country name fieldString
company_locations_full.country_iso_2Fixed ISO 2-letter country fieldString
company_locations_full.country_iso_3 Fixed ISO 3-letter country code fieldString
company_locations_full.regions Fixed regions array fieldArray of structs
company_locations_full.state Fixed state fieldString
company_locations_full.cityFixed city fieldString
{% endupdate %} {% endupdates %} ## Multi-source Company API {% updates format="full" %} {% update date="2026-03-12" %} ## Adding new fields The update introduces new workforce metrics, identifiers, and parent company mapping fields. | Data field | Description | Data type | | ------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------- | | `departures_count` | Count of employees who left the company in the current month. Set to `0` when there are no departures | Integer | | `departures_count_by_month` | Historical monthly departures count with corresponding dates | Array of structs | | `departures_count_by_month.departures_count` | Number of employee departures | Long | | `departures_count_by_month.date` | Date for departure count | String | | `employee_attrition_rate` | Current month attrition rate calculated as (`departures_count` / `employees_count_inferred`) \* 100. Value is `null` when `employees_count_inferred` is `0` or `null` | Double | | `employee_attrition_rate_by_month` | Historical monthly attrition rates with corresponding dates | Array of structs | | `employee_attrition_rate_by_month.attrition_rate` | Attrition rate | Double | | `employee_attrition_rate_by_month.date` | Date for attrition rate | String | | `professional_network_shorthand_name` | Professional network URL shorthand name | String | | `canonical_professional_network_shorthand_name` | The most recent version of `professional_network_shorthand_name` | String | | `parent_company_information.parent_company_id` | Matched parent company ID | String | | {% endupdate %} | | | {% update date="2026-03-12" %} ## Elasticsearch DSL schema update Adding `domain_only` data field type for `website_alias`. Sample of the schema below: ```json "website_alias": { "type": "text", "fields": { "domain_only": { "type": "text" } } }, ``` {% endupdate %} {% endupdates %} ## Multi-source Employee API {% updates format="full" %} {% update date="2026-03-12" %} ## Adding a new field `profile_score` is a model-derived quality score for our multi-source employee dataset, calculated from Professional network profiles. Using our profile dataset collection and integrated change-tracking data, we trained a model that performs score analysis across various profile features to produce a single numeric quality indicator per profile. | Data field | Description | Data type | | --------------- | ----------------------------------------------------------------------------------------------------------------------- | --------- | | `profile_score` | Model-derived employee profile quality score based on profile completeness and activity signals. Score range: `0` – `1` | `Double` | Detailed description is given in the Multi-source Employee Data [changelog](#multi-source-employee-data). {% endupdate %} {% update date="2026-03-25" %} ## New sorting option Introducing `profile_score` as a sorting field when querying Multi-source Employee results. This allows you to order employee records by their computed profile completeness score, enabling more meaningful ranking of results. {% endupdate %} {% endupdates %} ## Base Employee API {% updates format="full" %} {% update date="2026-03-25" %} ## Added a new field The `inferred_skills` contains skills derived from structured and contextual profile information. | Data field | Description | Data type | | ----------------- | ------------------------------------------------------------------ | ---------------- | | `inferred_skills` | Lists employees' skills based on the descriptions from the profile | Array of strings | | {% endupdate %} | | | | {% endupdates %} | | | ## Logic changes {% updates format="full" %} {% update date="2026-03-23" %} ## Job title classification updates ### Changes We are improving our job title classification system with refined department and management level categories. ### Impacted fields | Dataset | Data fields | | ------------------- | -------------------------------------------------------------------------------- | | Clean Employee data | | #### C-Level migration: `department` → `management_level` * The `"C-Suite"` department has been eliminated (previously 2.3M records). * C-Level executives are now classified by their functional department (e.g., CFO → `Finance & Accounting`, CTO → `Engineering and Technical`), with `"C-Level"` assigned as their management level. #### Reduced "Other" classifications * The "Other" department has dropped from 8.9M to 2.1M records (76% reduction) as significantly more job titles are now accurately categorized into specific departments. #### New category: "General Management" * A new "General Management" department has been added to capture leadership roles that span multiple functions (4.5M records). *** ### Supported values #### Departments `Administrative` · `Consulting` · `Customer Service` · `Design` · `Education` · `Engineering and Technical` · `Finance & Accounting` · `General Management` · `Human Resources` · `Legal` · `Marketing` · `Medical` · `Operations` · `Other` · `Product` · `Project Management` · `Real Estate` · `Research` · `Sales` · `Trades` #### Management levels `C-Level` · `Director` · `Founder` · `Head` · `Intern` · `Manager` · `Owner` · `Partner` · `President/Vice President` · `Senior` · `Specialist` *** ### Classification examples | Title | Department | Management level | | ------------------------ | ------------------------- | ------------------------ | | CEO | General Management | C-Level | | CFO | Finance & Accounting | C-Level | | CTO | Engineering and Technical | C-Level | | Director of Engineering | Engineering and Technical | Director | | VP of Sales | Sales | President/Vice President | | Marketing Manager | Marketing | Manager | | Senior Software Engineer | Engineering and Technical | Senior | | Software Engineer | Engineering and Technical | Specialist | | {% endupdate %} | | | | {% endupdates %} | | | ## Clean Company API {% updates format="full" %} {% update date="2026-03-25" %} ## Adding new fields We are adding new company HQ location fields. | Data field | Description | Data type | | --------------------------- | ------------------------------------------------- | --------- | | `location_hq_country_iso_2` | ISO 2-letter country code for company HQ location | String | | `location_hq_country_iso_3` | ISO 3-letter country code for company HQ location | String | | `location_hq_state` | Company HQ state | String | | `location_hq_city` | Company HQ city | String | | {% endupdate %} | | | | {% endupdates %} | | |