feedback

Is there any way to make the resume parsing on import better? More often than not (I’d say at least 75% of the time), it’s totally incorrect. It’s most often incorrect in the Job Title and Company fields. Sometimes one of those fields will be correct, and the other will be either blank or just show a grouping of other words in the resume. Other times both will be just blank. Other fields that the parser has common issues with that I’ve seen: phone number, email, location. I know that no parser is 100% foolproof, but I’ve used multiple CRM systems, ATS’s, other systems, and data scrapers that are worlds beyond where this one is. Is it possible to put some focus on this?

Is there any way to make the resume parsing on import better? More often than not (I’d say at least 75% of the time), it’s totally incorrect. It’s most often incorrect in the Job Title and Company fields. Sometimes one of those fields will be correct, and the other will be either blank or just show a grouping of other words in the resume. Other times both will be just blank. Other fields that the parser has common issues with that I’ve seen: phone number, email, location. I know that no parser is 100% foolproof, but I’ve used multiple CRM systems, ATS’s, other systems, and data scrapers...

In Review

aguzman

Is there any way to make the resume parsing on import better? More often than not (I’d say at least 75% of the time), it’s totally incorrect. It’s most often incorrect in the Job Title and Company fields. Sometimes one of those fields will be correct, and the other will be either blank or just show a grouping of other words in the resume. Other times both will be just blank.

Other fields that the parser has common issues with that I’ve seen: phone number, email, location.

I know that no parser is 100% foolproof, but I’ve used multiple CRM systems, ATS’s, other systems, and data scrapers that are worlds beyond where this one is. Is it possible to put some focus on this?



Resume Parsing

Subscribe to post

Post Information