Bugs

I've noticed the human_resources roles that are more senior often have misclassified job title roles or sub roles. This is especially present in areas like investment banking, but also other areas.

Searching on a po box address that exists in your data is not returning in the search api. See attached side by side of person enrichment vs person search.

Around 90k profiles are being tagged to University School when they should be tagged to East Tennessee State University.

The parquet data exports of company data contain embedded nulls, which complicates parsing this data with some standard version of arrow.

The company domains are stale. ( useloom.com changed to loom.com , getsentry.com -> sentry.io etc) Other examples: {' useloom.com ': ' http://www.loom.com/ '}, {' getsentry.com ': ' http://sentry.io/welcome/ '}, {' standardcognition.com ': ' http://standard.ai/ '}, {' proposify.biz ': ' http://www.proposify.com/ '}

Employees of https://www.linkedin.com/company/mgxai are incorrectly mapped to linkedin.com/company/mgxdigital (id: zjALg7FSxb7FGywj3e6CVAA713HR)

We canonicalize people who work at a stealth startup to company ID: y4crItXCDcfiKkDkCneCgwJU1Gg3 (and potentially other IDs). This really shouldn't be a canonical company and we should figure out how we handle people who work at stealth startups. In addition, when they update their experience to indicate the name of the company / come "out" of stealth this creates duplicate / messy experience.

When using Retrieve API for person A, we noticed that an incorrect primary email address is returned. This email address actually belongs to someone else. We found out about this after that person contacted us that they are not person A.

There is a spam/inappropriate profile in the database