# May 2026

## Experience and Education Update

{% updates format="full" %}
{% update date="2026-04-21" %}

## Overview

We are releasing an update to the Experience and Education categories in employee data. This release includes schema additions, data quality improvements, and a change to the ordering of active experiences. To apply all changes smoothly, the delivery for this update will be a full reload of both collections.

### Added new fields

#### Clean Employee Data

Adding new data fields to experience category.

| Data field                                   | Description                                   | Data type |
| -------------------------------------------- | --------------------------------------------- | --------- |
| `member_experience[].company_shorthand_name` | Shorthand / vanity identifier for the company | String    |
| `member_experience[].company_website`        | Company website URL                           | String    |

#### Multi-source Employee Data

Adding new fields to expand information about active experience.

| Data field                                 | Description                                                | Data type |
| ------------------------------------------ | ---------------------------------------------------------- | --------- |
| `active_experience_company_website`        | Website of the company in the employee's active experience | String    |
| `active_experience_company_shorthand_name` | Shorthand name of the company in the active experience     | String    |
| `active_experience_company_logo_url`       | Logo URL of the company in the active experience           | String    |

### Data improvements

#### 1. Data quality improvements <a href="#id-1.-data-quality-improvements" id="id-1.-data-quality-improvements"></a>

* **Stale deleted records removed**

Previous mapping logic could classify an experience as active (`deleted: 0`) even after the record stopped being updated. These records have now been identified and corrected. As a result, you may see a net reduction in `deleted: 0` experience counts. This change reflects cleaner, more accurate data, not data loss.

* **Improved fill rate on key fields**

The updated mapping logic improves coverage on two critical experience fields:

| Data field  | Improvement                            |
| ----------- | -------------------------------------- |
| `title`     | Higher fill rate and fewer null values |
| `date_from` | Higher fill rate and fewer null values |

#### 2. Change in `active_experience` ordering <a href="#id-2.-change-in-active_experience-ordering" id="id-2.-change-in-active_experience-ordering"></a>

The first entry in the `active_experience` array will now be ordered by greatest `date_from` (i.e. most recent active experience first).

Previously, ordering was based on `order_in_profile`, which could produce inconsistent results due to the legacy mapping logic. The new ordering is deterministic and reflects the employee's most recent active role.

{% hint style="info" %}

#### **Action required if you consume `active_experience[0]`**

Verify that your pipeline handles the new ordering correctly. The most recent experience will now always appear first.
{% endhint %}
{% endupdate %}
{% endupdates %}