Ideally there would be something on https://json-schema.org/ (as there are for industry job posting standards)
I have no idea why one wouldn't instantly go ahead and install this extension /s
Also, we do not scrape any data explicitly. At no point in time do we read data from the linkedin api nor html.
If it comes out any decent, lmk and we'll give you some credits for the paid service. The UX around tailoring resumes isnt as intuitive.
You can do some free tailoring on the home page as well, this ux is straight forward: cvgist.com
Not sure how to fix it. Thought you might like to know.
2. It's not clear how these tools grab this data without some direct integration with LinkedIn or Violation of their terms
3. We use AI to craft resume language, Kick Resume is a copy/Paste
4. We provide a word doc you can download and edit yourself.
So, the people installing this extension are the product then?
But turned out that shitty ATS software was throwing away my resume, even though it rendered and text-extracted fine, and with normal PDF fonts (not rasterized, like some DVI convertors would do).
Though, one time that the resume got me to an interview battery at a startup, it was a good conversation-starter with their designer, who could tell it was hand-crafted.
Now, I just have a relatively phoned-in two-pager, with lots of search keywords, that I do in LibreOffice. To hopefully get me found by the right serendipitous sourcer/recruiter/manager/founder, and hopefully not have the resume discarded if they pop it into some shitty corporate hiring pipeline system. Nor mangled too badly, if they parse it, and have some people in the process looking only at their shitty parser's output in a Web page.
I'd prefer making the most of one page, but sometimes idealism has to be flexible to the reality on the ground.
Don’t get me started about cute resumes that were written as code, etc. I hated them and hated myself for how much I hated them.
I've got various theories as to why, but in my experience most people with non-standard resumes have turned out to be weaker candidates than people who just type their stuff into a standard template with something approaching the STAR format.
Sorry no. It took me two days to fix a template I got from the internet to display all the writing systems I want. Plus I had a manually fix a hardcoded value in the bibliography template to use French while I had to use the bibliography in an English context so references don't get screwed with space inserted before colons. My dissertation is filed \foreignlanguage{xxx}{yyy} and \textit and I hate it.
> you should... / git gud
No. I have something to write, in addition to all the other things I do, and any time searching for commands or packages online to make things work is pure wasted. If Word had a better CVS and modular story I would have gladly stick with it.
I'd argue I spent more time trying to fit everything in two neat pages than actually writing down the resume.
At least it shows I know flexbox, or something. It's mostly a backend position anyway.
My process is update resume, git commit, git push, then update LinkedIn or whatever social site I want beyond that. The LaTeX files then become the single-source-of-truth.
(I hope that) I'm a far more interesting person than my resume would suggest. Unfortunately, no one hiring engineers would put that at the top of the list.
I've interviewed enough people to know what matters, so I highlight that. The fact that I once fell asleep underwater will have to come up at another time.
Can you share the github/sourcecode for the extension or unminify it? Code shouldn't be minified in V3 extensions anyway.
Google in fact allows minified code, not obfuscated.
Using LinkedIn is a highly desired feature in the resume builder business. Highly successful firms are using 3rd party services that scrape your profile (already have) without your consent.
So, no, you can parse the minified code all you like - the advantage we have with my implementation is competitors spend minutes scraping while we dont need to. - Which as you've inherently figured out, is not that insightful. - The extension codebase is small and doesnt communicate with any server
