-
-
Notifications
You must be signed in to change notification settings - Fork 399
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
better experience parsing #14
Comments
@nickmedwards I totally agree with your point. The thing is I'm really struggling while segregating the different entities in experience "text". I am still not able to find a proper solution on this. Will update soon on this. Meanwhile, if you can get any solution you can open a PR too. Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I sent the attached file through your parser, the returned experience data is
The parser seems to get 5 different kinds of data, the company, the duration, the job title, the job location, and a job description. Could you make it so that these different kinds of experience data are better organized? On a related note, for the job description data, it only gets it one line at a time. Could you make that data one string?
Thanks for building this and hope you'll be able to find solutions to my questions!
resume_Meyer.pdf
The text was updated successfully, but these errors were encountered: