Keep Experience ID's Persistent
H
Haley Bryan
Merged in a post:
Job IDs
B
Ben Eisenberg
Have an ID tied to a person's job experience object. When a customer gets a data file, they know which experiences to update/edit/delete upon ingestion. If a title changes or a company name changes we would want to indicate that on the same job.
Jenelle Kemp @ PDL
From Josh Harris at Solel on 01/22/2026:
In the person data, the experience fields aren’t nested so they can’t do a nested search of specific company data parameters. He has to search across the entire field object. It would improve search efficiency and ease to search within those objects. It would also be helpful for them if there was an experience object ID in addition to person ID.