Why isn't there an XML or JSON format widely used for CVs? It would make sifting through CVs so much easier, plus it would make CVEO (CV engine optimization) a thing.
Does anyone still enjoy writing, rewriting and designing their own CV by hand, for example using Latex? Shouldn't it be a signature, a testament to your sense of individualism and craftsmanship?
I did. I had a nice TeX or LaTeX hand-tuned one-pager. Yes, "C++" was a macro, to subdue those ridiculous huge '+' characters, there was no Computer Modern Roman, and I made countless other tweaks.
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.
I stopped caring about that when companies started using Applicant Tracking Systems (ATS) to evaluate resumes based on keywords and other silly criteria without ever having a person actually review it.
I was the founding site lead of a Polish office of U.S. tech company, with an initial target of a hundred developers. After looking at… many resumes I realized I strongly disliked custom resumes. As much as I wanted to appreciate uniqueness and creativity, it got in the way. What I really wanted was something as standard and easy to read as possible. Ideally a LinkedIn profile.
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.
Unfortunately, I've found a negative correlation between CV creativity and candidate quality.
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 did mine by hand using plain HTML+CSS (using A4.css, then rendered to a 2-page PDF) and my employer remarked that it was a sign of attention to detail and care that many other candidates won't even bother with.
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.
I do! Using LaTeX is how I track changes to my resume, look at historic resumes, and keep it all in commits within git, tagging "releases" I send out.
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.
This is one of the things I enjoy the most these days, but I also had quite a lot of fun with it back in the day... I just looks for designs online and then I reproduce as much as I can using other tooling... I enjoy doing this for anything print, like magazines and corporate image documents too...
Nope. It's a list of shit that I've done, organized in the most effective way to get someone to hire me.
(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.
hmm weird, do you mind sharing your profile? Or try refreshing that page it could be a cloudflare issue... we have to protect against the endpoint to avoid financial ddos.
i’ve been quietly on the job market the last month or so, and i’ve been kind of surprised at the number of recruiters who insist they need an “actual resume” instead of linkedin profile, which honestly has been my resume for about 15 years now. i finally dropped a PDF of my profile into claude and got a resume condensed, but i have a hard time seeing the advantage in this day and age.
No one is concerned this sends your LinkedIn ID and PDF to their own server to "generate" the PDF? Surely that data is being stored (and probably sold).
Can you share the github/sourcecode for the extension or unminify it? Code shouldn't be minified in V3 extensions anyway.
I'm not sure how to mitigate the data selling concern or what to show you there. But we're trying to upsell a paid service via nice free utility. We send your data to use AI to generate the resume, that is part of the deal. So if you wouldn't give your data to ChatGPT, don't give it to us (delete it from linkedin also - because your principles sound weak while you let it reside there). We store the data so that paid users can reference their linkedin profiles. Feel free to request a delete and we'll do so with adequate proof: support at cvgist dot com.
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
hahamaster|1 year ago
prodtorok|1 year ago
Ideally there would be something on https://json-schema.org/ (as there are for industry job posting standards)
pratio|1 year ago
elliotec|1 year ago
prodtorok|1 year ago
nramos3|1 year ago
phoronixrly|1 year ago
I have no idea why one wouldn't instantly go ahead and install this extension /s
monsieurgaufre|1 year ago
prodtorok|1 year ago
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
nramos3|1 year ago
TripleChecker|1 year ago
prodtorok|1 year ago
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.
MateGreat|1 year ago
smartmic|1 year ago
neilv|1 year ago
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.
redeux|1 year ago
szopa|1 year ago
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.
drc500free|1 year ago
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.
alexott|1 year ago
tokinonagare|1 year ago
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.
Vampiero|1 year ago
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.
csswizardry|1 year ago
urda|1 year ago
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.
pelagicAustral|1 year ago
Conscat|1 year ago
bagels|1 year ago
ramon156|1 year ago
HeyLaughingBoy|1 year ago
(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.
j1mmie|1 year ago
xtracto|1 year ago
prodtorok|1 year ago
karmajunkie|1 year ago
gdevenyi|1 year ago
bitbasher|1 year ago
Can you share the github/sourcecode for the extension or unminify it? Code shouldn't be minified in V3 extensions anyway.
prodtorok|1 year ago
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
TrillgoreClout|1 year ago
prodtorok|1 year ago
hacker002|1 year ago
zishaniqbal1|1 year ago