March 2026 Release Notes (v33.2)

Release NameDataset VersionPublish Date
March 2026v33.203/19/2026

Welcome to our March 2026 release notes!

This month’s release focuses on data quality, freshness, and richer company workforce insights. We’ve made significant improvements across our datasets to ensure the information you rely on is more accurate, more current, and easier to analyze at scale.

Here’s what’s new:

Dive into the full details below, or jump to what interests you using the table of contents below.


Table of Contents

📐 Schema Changes

🚀 Data Updates

🛠 Improvements and Bug Fixes


📐 Schema Changes

New Headcount Insights Fields (Company Data)

What’s New?

This month, we’re adding 7 new Headcount Insights Fields to our Company Dataset. These new fields are designed to support workforce analytics use cases with richer data on employee movement, tenure, and geographic growth trends.

New Headcount Insights Fields

FIELD NAME

FIELD TYPE

FIELD BUNDLE

FIELD DESCRIPTION

employee_turnover_rate

Object

Premium
Comprehensive

The percentage of employees who left the company compared to the company’s average workforce size over the most recent period. This field may report turnover rates for various periods.

annualized_employee_turnover_rate

Object

Comprehensive

The annualized percentage of employees who left the company compared to the company’s average workforce size over the most recent period. This field is identical to the employee_turnover_rate field, except that each period is annualized to enable direct comparison across different points in time.

median_employee_tenure

Float (>=0)

Premium
Comprehensive

The median number of years that employees have worked at the company.

median_tenure_by_level

Object

Premium
Comprehensive

The median number of years that employees have worked at the company, broken out by job title levels.

median_tenure_by_role

Object

Premium
Comprehensive

The median number of years that employees have worked at the company, broken out by job title role.

employee_growth_rate_12_month_by_country

Object

Premium
Comprehensive

The twelve month rate of change across each country. For each country, this field contains the current employee count, the employee count from one year ago, and the rate of growth or decline. See also: employee_count_by_country
Note: users accessing PDL's Tabular Schema instead receive this data as columns in the employee_count_by_country table.

affiliated_entities.employee_count

Integer (>= 0)

Premium
Comprehensive

The current employee count for the related company listed in the affiliated_entities object.

Examples
employee_turnover_rate
 "employee_turnover_rate": {
   "3_month": 0.0125,
   "6_month": 0.025,
   "12_month": 0.04,
   "24_month": 0.2
 },
annualized_employee_turnover_rate
  "annualized_employee_turnover_rate": {
    "3_month": 0.0250
    "6_month": 0.05,
    "12_month": 0.04,
    "24_month": 0.1
  },
median_employee_tenure
 "median_employee_tenure": 2.641
median_tenure_by_level
  "median_tenure_by_level": {
    "unpaid": 0.0,
    "cxo": 4.653,
    "partner": 0.0,
    "owner": 9.861,
    "director": 1.785,
    "vp": 2.617,
    "senior": 1.958,
    "manager": 1.813,
    "entry": 0.0,
    "training": 0.5
  }
median_tenure_by_role
"median_tenure_by_role": {
  "advisory": 2.083,
  "trade": 0.0,
  "manufacturing": 0.0,
  "hospitality": 0.0,
  "public_service": 0.0,
  "support": 1.546,
  "research": 2.625,
  "product": 1.993,
  "education": 0.0,
  "human_resources": 2.013,
  "legal": 0.0,
  "operations": 3.619,
  "fulfillment": 1.771,
  "professional_service": 0.0,
  "creative": 1.833,
  "marketing": 1.689,
  "partnerships": 1.56,
  "sales_engineering": 2.051,
  "sales": 1.964,
  "health": 0.0,
  "analyst": 1.683,
  "finance": 4.563,
  "engineering": 2.993
}
employee_growth_rate_12_month_by_country
  "employee_growth_rate_12_month_by_country": {
    "other_uncategorized": {
      "current_headcount": 1,
      "12_month_headcount": 0,
      "12_month_growth_rate": null
    },
    "united kingdom": {
      "current_headcount": 10,
      "12_month_headcount": 2,
      "12_month_growth_rate": 5
    },
    "india": {
      "current_headcount": 1,
      "12_month_headcount": 1,
      "12_month_growth_rate": 0
    },
    "colombia": {
      "current_headcount": 1,
      "12_month_headcount": 1,
      "12_month_growth_rate": 0
    },    
    "canada": {
      "current_headcount": 74,
      "12_month_headcount": 52,
      "12_month_growth_rate": 0.4231
    },
    "philippines": {
      "current_headcount": 4,
      "12_month_headcount": 3,
      "12_month_growth_rate": 0.3333
    },
    "spain": {
      "current_headcount": 0,
      "12_month_headcount": 4,      
      "12_month_growth_rate": -1
    },
    "portugal": {
      "current_headcount": 2,
      "12_month_headcount": 1,      
      "12_month_growth_rate": 1
    },
    "united states": {
      "current_headcount": 168,
      "12_month_headcount": 172,
      "12_month_growth_rate": -0.0232
    }
  }
affiliated_entities.employee_count
"affiliated_entities": [
  {
    "affiliated_id": "Bz8mYR0sZFCrWvdkco07nwi7tGTt",
    "display_name": "ExampleCo",
    "relationship": "ultimate_parent",
    "employee_count": 77118
  },  
  {
    "affiliated_id": "CzJNyjIICYIBrhIOyxG5iQfQvzLt",
    "display_name": "SubsidiaryCo",
    "relationship": "direct_subsidiary",
    "employee_count": 9
  },

Why It Matters

These new fields expand our Company Dataset records with widely used workforce metrics and more ready-to-use indicators of company headcount trends. Together, these fields make it easier to analyze hiring, retention, and geographic expansion without additional calculations.

Key benefits include:

  • Turnover fields: Provide standardized turnover metrics that make it easier to benchmark employee retention and workforce stability across companies and time periods
  • Median tenure fields: Adds more robust metrics for understanding employee tenure that complement our existing average tenure fields
  • Growth rate by country field: Simplifies analysis of a company’s geographic presence and makes it easier to identify locations with growing or shrinking footprints
  • Affiliated profile employee count field: Enables easier aggregation of employee counts across parent companies, subsidiaries, and related entities.

Availability
These fields will be automatically added to the Company Premium and Company Comprehensive field bundles.

Customers receiving either of the Premium or Comprehensive field bundles will automatically receive the new fields (unless they have opted out of such updates previously).

📘

For the employee_turnover_rate field specifically:

  • the 12-month turnover rate will be available in the Premium bundle
  • the 3-, 6-, 12-, and 24-month turnover rates will be available in the Comprehensive bundle

We’d Love Your Feedback!
Your input helps shape what we build next. Share your thoughts on these fields or suggest new ones via our Roadmap Feature Request Board!


🚀 Data Updates

Freshness

The number of jobs and locations verified in our datasets (based on the job_last_verified and location_last_updated fields).

Monthly (v33.1 → v33.2)
Freshness updates over the past month.

DatasetGeographyFieldRecords Updated
ResumeGlobalexperience69,340,086
ResumeGloballocation71,319,387
ResumeUnited Statesexperience25,602,692
ResumeUnited Stateslocation24,952,269

Job Changes

The number of person records where the primary job experience changed in our Person Dataset (based on the job_last_changed field).

Monthly (v33.1 → v33.2)
Freshness updates over the past month.

DatasetGeographyRecords Updated
ResumeGlobal17,095,459
ResumeUnited States3,428,411

Coverage (Full Stats: Person, Company, Job Posting, IP)

Monthly (v33.1 → v33.2)

Resume Dataset

LinkageCoverage in v33.1Coverage in v33.2Increase (%)
Total Records798,883,485809,413,6141.32%
languages.proficiency24,017,58556,004,088133.18%
work_email64,587,83568,063,5625.38%
job_company_total_funding_raised65,789,90560,602,359-7.89%

API Dataset

LinkageCoverage in v33.1Coverage in v33.2Increase (%)
Total Records2,452,057,3382,450,764,460-0.05%

Email Dataset

LinkageCoverage in v33.1Coverage in v33.2Increase (%)
Total Records587,067,804586,672,510-0.07%

Mobile Phone Dataset

LinkageCoverage in v33.1Coverage in v33.2Increase (%)
Total Records479,764,367479,651,097-0.02%

Company Dataset

LinkageCoverage in v33.1Coverage in v33.2Increase (%)
Total Records74,679,88774,685,7930.008%

Job Posting Dataset

LinkageCoverage in v33.1Coverage in v33.2Increase (%)
Total Records24,056,41125,931,6747.80%
Total Unique Companies48,05952,2368.69%
Total Active Postings2,792,3943,178,61313.83%

Commentary

  • Person
    • We saw a 133% increase in coverage for language proficiencies in our Resume Dataset as a result of some improvements we made this month.
    • Work email coverage increased by 5% this month, as part of our ongoing efforts to improve the quality and deliverability of our top-level email addresses
    • We saw a 7% drop in coverage for our coverage of job_company_total_funding_raised as a result of a logic improvement we made to ensure more accurate funding information.
  • Job Posting Data
    • This month we saw a 8% increase in the number of unique companies tracked in our Job Posting Dataset.

🛠 Improvements and Bug Fixes

Improvements

  • Sourcing Diversification
    • We expanded our data sourcing resulting in a significant increase in profile updates and job change detections.
  • Additional Language Proficiencies
    • We identified gaps in how language proficiency levels were being detected and resolved issues that caused some entries to be missed or misread. As a result, proficiency coverage has increased by 133%.
  • Total Funding Set to null when Unknown
    • We updated the total_funding_raised field in our Company records to return null when all associated funding_details.funding_raised values are null. Previously, this field returned 0 in these cases. This change more accurately represents situations where funding information is unavailable rather than indicating that no funding was raised.

Bug Fixes

  • Incorrect End Dates on Current Roles
    • We resolved an issue where some profiles incorrectly contained an end_date (often 2026) on their current role due to a source data error. In affected records, this caused active positions to be interpreted as ended.
    • This fix restores the correct representation of current roles and resolves several downstream impacts introduced in the previous release, including:
      • Primary job detection: Some profiles temporarily lost their active primary role because the incorrect end_date caused the role to appear inactive.
      • Headcount and workforce metrics: Company headcount trends and derived insights fields (e.g. employee headcount and role transition fields) may have shown artificial declines due to the misclassification of active employees.
      • Experience-based calculations: Metrics derived from current job tenure (such as years at current company) may have been temporarily understated.
    • Not impacted: job_last_changed
      • Our job_last_changed metrics reported this month and last month were not affected by this bug and are accurate representations of the job changes detected in our dataset.
    • With this fix, current roles are again correctly identified as active, restoring accurate job status and downstream metrics.
  • Removed Certifications from Names
    • We expanded our name cleaning logic to ensure certain certifications do not appear in name fields (i.e. CDPSE, NRCSS)
  • Volunteering Experience as Active Job
    • We fixed an issue where volunteer experience was being added into the experience fields and in some cases being selected as an active job.
  • Location Names as Experience Summaries
    • We fixed an issue where the experience.summary field for some records was being incorrectly populated with raw experience location information (e.g. New York, New York, US). This fix removes summaries that directly match location data, improving the quality and uniqueness of professional summary results.
  • Education Raw School Values
    • We fixed an issue with a data source where raw school values (e.g. university of oregon) were being incorrectly mapped to the education.raw field instead of the education.school.raw field.