There’s also https://casual-effects.com/markdeep/ which extends markdown, has various templates including resume and there’s commands mentioned to get pdf version from command line.
I tried to use Firefox’s PDF facilities, but it couldn’t properly render links, which I have on the PDF version of my resume. So I’m stuck with chrome for the time being.
If you want to drop Chrome for this use case, I would give weasyprint a try. I was pleasantly surprised that it just worked, without any configuration.
It’s a good weekend project, nothing to be embarrassed about.
I remember having the same issue and selected Asciidoc as a format. The format gives better control over layout, such as placing the headshot on the top-right corner. And the Asciidoctor tooling outputs PDF by default. Unfortunately, the resume contains too much private information to be open-sourced right now.
This is generally a really bad idea. Companies are starting to care about implicit bias in their hiring process and if the first thing you see is a photo then that maximises the likelihood of implicit bias influencing shortlisting decisions. To avoid this, someone in HR will do a pass over the CV and strip out things like this. The hiring manager will see a mangled version of your CV.
If you want to avoid this, don’t put age, ethnicity, citizenship, or a photo anywhere on your CV. Companies may request this information (particularly for right-to-work checks) separately, but that goes through HR not to the person making the hiring decision. In some jurisdictions, taking any of this information into account in the hiring process is illegal. The simplest way of avoiding legal risk is to just throw away any CVs that include this information into the bin.
Do you know if they are also stripping the name from the CV?
With Asciidoc it’s quite easy to customize the CV with conditionals so it’s not necessarily a problem if they want the document with just the body of the content.
I’ve only rarely seen that done. There is research showing that it’s a good idea, but humans aren’t good at remembering candidate numbers, so going though a stack is quite tricky.
I just checked several large companies in my area (in Germany) and their application forms all have an explicit field for a photo. It wasn’t marked as required, though.
It’s a good weekend project, nothing to be embarrassed about.
For anyone wondering what this is about, it’s in response to my description on this post, which I guess should have been a comment: “I feel kind of embarrassed submitting this trivial weekend project but it was an itch of mine that nobody else had scratched and perhaps someone other that me will find it useful.”
The format gives better control over layout, such as placing the headshot on the top-right corner.
If you’re happy with the control of asciidoc then no worries, but just in case you were interested in dropping down to Markdown source: I was surprised by how easy it was to format the plain HTML output (no classes or ids) with CSS. E.g. in the example resume.md, the line of contact details below the name is a <ul> that I style with the h1 + ul CSS selector. Not having the ability to apply classes etc. to specific elements makes styling a particular instance a little fragile, and I wouldn’t play tricks like this across an entire website, but for a single page resume I think it’s fine.
So, for example, you could put the <img> immediately before (or after) the <h1> and then select it uniquely in CSS with h1 + img and shift it up to the corner with the usual tricks.
That said, I agree with the advice that you should not include a headshot in a resume in 2020! And I especially wouldn’t use Europass format, if that’s where you’re getting this idea from. (See, e.g. https://twitter.com/brkzkn/status/1283785183187988482).
There’s also https://casual-effects.com/markdeep/ which extends markdown, has various templates including resume and there’s commands mentioned to get pdf version from command line.
Thanks for sharing. WeasyPrint is a good find. I had been using chrome-headless-render-pdf for my own resume but was not super happy with it.
I always use Chrome Headless for my resume, made in HTML+CSS (source). I’ve been happy with it: here’s what it looks like as PDF.
I tried to use Firefox’s PDF facilities, but it couldn’t properly render links, which I have on the PDF version of my resume. So I’m stuck with chrome for the time being.
If you want to drop Chrome for this use case, I would give weasyprint a try. I was pleasantly surprised that it just worked, without any configuration.
It’s a good weekend project, nothing to be embarrassed about.
I remember having the same issue and selected Asciidoc as a format. The format gives better control over layout, such as placing the headshot on the top-right corner. And the Asciidoctor tooling outputs PDF by default. Unfortunately, the resume contains too much private information to be open-sourced right now.
I use LaTeX for mine. One word of warning:
This is generally a really bad idea. Companies are starting to care about implicit bias in their hiring process and if the first thing you see is a photo then that maximises the likelihood of implicit bias influencing shortlisting decisions. To avoid this, someone in HR will do a pass over the CV and strip out things like this. The hiring manager will see a mangled version of your CV.
If you want to avoid this, don’t put age, ethnicity, citizenship, or a photo anywhere on your CV. Companies may request this information (particularly for right-to-work checks) separately, but that goes through HR not to the person making the hiring decision. In some jurisdictions, taking any of this information into account in the hiring process is illegal. The simplest way of avoiding legal risk is to just throw away any CVs that include this information into the bin.
Do you know if they are also stripping the name from the CV?
With Asciidoc it’s quite easy to customize the CV with conditionals so it’s not necessarily a problem if they want the document with just the body of the content.
I’ve only rarely seen that done. There is research showing that it’s a good idea, but humans aren’t good at remembering candidate numbers, so going though a stack is quite tricky.
I wonder whether this is a US thing…
I just checked several large companies in my area (in Germany) and their application forms all have an explicit field for a photo. It wasn’t marked as required, though.
If it’s a separate field then it may only be used for identifying candidates when they come in for interview and not presented to the hiring manager.
For anyone wondering what this is about, it’s in response to my description on this post, which I guess should have been a comment: “I feel kind of embarrassed submitting this trivial weekend project but it was an itch of mine that nobody else had scratched and perhaps someone other that me will find it useful.”
If you’re happy with the control of asciidoc then no worries, but just in case you were interested in dropping down to Markdown source: I was surprised by how easy it was to format the plain HTML output (no classes or ids) with CSS. E.g. in the example resume.md, the line of contact details below the name is a
<ul>that I style with theh1 + ulCSS selector. Not having the ability to apply classes etc. to specific elements makes styling a particular instance a little fragile, and I wouldn’t play tricks like this across an entire website, but for a single page resume I think it’s fine.So, for example, you could put the
<img>immediately before (or after) the<h1>and then select it uniquely in CSS withh1 + imgand shift it up to the corner with the usual tricks.That said, I agree with the advice that you should not include a headshot in a resume in 2020! And I especially wouldn’t use Europass format, if that’s where you’re getting this idea from. (See, e.g. https://twitter.com/brkzkn/status/1283785183187988482).