In today's dynamic job market, maintaining an up-to-date and organized resume is crucial. However, it can be a challenging task without the right t...
For further actions, you may consider blocking this person and/or reporting abuse
Just a couple comments.... Great idea using git for your resume. Maintaining a resume with git also works well with LaTeX (I do that with my CV).
My other comments concern your resume in your GitHub repository....
First, I recommend removing your birthdate. Nobody needs that. If someone hires you they will probably need it then as part of employment documentation, but until then they don't need it. You definitely don't want it in a public repository. It is risking identity theft. I strongly recommend removing it entirely from your git history. You should also remove gender from your resume. It is irrelevant to the hiring process. Here in the U.S. asking a candidate for a position about age or gender (and some other things) are actually off-limits during interviews. Neither are relevant to your qualifications.
Second, you might actually consider keeping this in a private repository. For example, do you really want the world to have access to your contact info, such as phone, etc? If you want potential employers to have access to a public version, then maybe have 2 versions, 1 private with complete contact info that you send when you apply for jobs, and 1 public with more limited contact info.
Thank you so much for your feedback 😄 I've made some updates to my resume based on your recommendations.
Great comment. Thanks so much for pointing that out. It did come to mind but you mentioned stuffs I did not even consider specially about having one in a public repo and one as private repo.
Not every country runs by the US laws...so def. not off limits outside of that island
I have done something similar with jsonresume.org/ .
If you just want to have a pdf markdown gets the job done. But I also wanted to have my resume as a website ;-).
So... yes and no. :-)
While this might be apparent to some readers, it bears mentioning that the local Git repo is just another copy/copies of your document. If something happens to your computer or the SSD, you'll then lose all copies.
But seeing that GitHub has private repos, that would be a great place to have a repo, because the extra copy of your repo stored offsite would then serve as a backup.
Very good subject.