We are having a major issue with resumes parsing. The candidate applies, loads resume, it parses incorrectly, the candidate fixes the data and applies. That same candidate wants to apply for a second job and Avionte will trigger it to send them a code to their email. They enter the code and the system requires them to load their resume again. It parses AGAIN and removes all of the information that the candidate fixed the first time. Candidates are very frustrated. Does anyone have this same issue? The parsing is not working well and we have asked for it to be turned off and have not received an answer. Any advice is appreciated.
1
Comments
Please sign in to leave a comment.
Our issue isn't so much with the parsing itself, but that when an applicant reapplies, it replaces all of the work history and work history notes, that the candidate and/or the recruiter may have spent quite a bit of time on. Work history should be appended and not replaced. This is a ticket I've had in forever.
I think our candidates may upload their resumes differently than yours are... Our only issue with parsing is when we're extracting resume data to work history. Our candidates never have to go in and fix the information on their resume.
We have the same complaint/issue as Tamara. It causes a lot of frustration with our recruiters. I'm sure it's very irritating to the candidates as well. Laurie, the reapply part of your problem is one we all share, unfortunately. We've not had a problem with resumes consistently parsing incorrectly, but we do find that there is still additional data the candidate needs to complete to apply - each time they are interested in a job post.
Hi Shelly & Tamara,
Thank you for your feedback. After I posted yesterday, support created a ticket for me I explained the situation. It really does come down to the candidates who apply more than once. The parsing is ok for the most part but the candidates usually make changes and then when reapply, it changes what the candidate changed the first time. Support worked on this yesterday and researched what I was describing. They came to the conclusion that the parsing is not the issue (I think I described it incorrectly yesterday) and support does agree that the issue is when the candidate reapplies. They are aware of it and said that there will be a change to the application process in a future version but they would not say when the future version will be rolled out. So, there should be a fix sometime in the future. I hope it is soon. Thanks for your feedback! I really appreciate it!
Thank you for letting us know, Laurie! I too, hope it is soon!