31–40 of 79 posts
Do any interviewers notice resumes that are written in LaTeX compared to ones that aren't?
Yep; it’s obviously not a deal breaker/winner, but we definitely notice. I once joked that we ought to mark up candidates with LaTeX CVs, but knock them slightly down if they stuck with Computer Modern :)
I've been using this one for my resume and I love it: http://www.rpi.edu/dept/arc/training/latex/resumes/res.cls As a hiring manager, I much prefer simpler resumes that are easy to scan. I don't really like the "five stars" self-rating stuff, however. It feels a little strange to distill one's language knowledge down to a number. One thing I do love is when people include some of their notable open source projects. T…
> Also: never, ever put a photograph of yourself in your resume. You're just asking for someone to judge you based on your looks, gender, age, or ethnicity. Likewise, don't put your age. If you've been around for a while, trim everything but the last 5-10 years of positions off your resume to avoid the unfortunate but oh-so-common ageism. Even old hiring managers can be ageist! Don't give anyone a chance to judge you…
Not really.
The more educated people are about this topic (e.g. have read "The Google Resume" by Gayle McDowell, which I highly recommend), or have had startup experience, the less common it is.
We all should stop doing it, everybody will benefit.
Do any interviewers notice resumes that are written in LaTeX compared to ones that aren't?
I must say, I was happy to come across this after putting in the not insignificant effort of converting my resume into a nice looking LaTeX document: http://stevehanov.ca/blog/resume_comic.png
Do any interviewers notice resumes that are written in LaTeX compared to ones that aren't?
Earlier quoted context omitted.
Yep; it’s obviously not a deal breaker/winner, but we definitely notice. I once joked that we ought to mark up candidates with LaTeX CVs, but knock them slightly down if they stuck with Computer Modern :)
How can you tell that they used LaTeX if the CV is in PDF format, other than by guessing from the use of Computer Modern?
This may be an unpopular opinion, but I feel like LaTeX is not an efficient way to create a resume, unless you are very skilled with LaTeX macros and can essentially create your own "template", or modify someone else's. If you don't have those skills, you end up with a very bland, "stock LaTeX document"-looking resume, of which half the LaTeX resumes I see people share look like. I once tried to redo my resume in LaT…
However it has become more and more painful to edit it.
I have moved to a simple Google Document 3 years ago.
Reasons :
- I dont really need all these advanced Latex features, I am not writing a maths book.
- Docs has everything I need in order to make a resume (tbh I have considered doing it in Photoshop to have more graphical flair but never spent the time to do so)
- I can get feedback directly in the docs.
I am not going to spend the time to do it in Latex again
A few properties:
* There's no separate CV and Resume. A resume is just the highlighted elements in a CV.
* The "PDF" version is created by print-to-pdf in Chrome.
* `cv` and `resume` pages are statically pre-rendered (google-friendly), with a switch (visible on desktop browsers) to toggle between them.
* Elements are represented in JSON objects, so the entire CV's data can be exported to one JSON string. I also only need to edit the JSON files for changing stuff in my resume.
* Each commit to Github triggers a build in Travis CI, which 1) updates the JS bundles, 2) renders the static pages and 3) updates the rendered PDFs.
Story:
Couple years ago I was doing a re-design on my resume. I started with LaTeX, but in the end did not continue: I wanted my resume to look good on both the Web and on paper, and I couldn't find a LaTeX -> HTML renderer that can be properly indexed by Google.
Then I realized, perhaps I've been doing this backwards: instead of rendering HTML from LaTeX, why don't I just use Chrome's print-to-pdf function to create a PDF from HTML directly? I also wanted to learn React.js, so that was my chance.
Now, if I want to change something in my resume/CV, I can just edit the JSON files, and Travis CI takes care of all the updates, instead of me manually updating multiple versions. I use nightmare.js to capture the PDFs and pre-rendered static HTMLs, and the workflow has been greatly simplified.
Want to hide something in the resume and only show it on the CV? Easy, just change `featured` property to `false`. The "Publication" section even recognizes my frequent co-authors, and render their names as links to their homepages. The possibilities are endless. I have been satisfied ever since.
I put out a tutorial about how to make you're own if anyone is curious http://www.maxburstein.com/blog/creating-resume-using-latex/ I still use it to this day
This may be an unpopular opinion, but I feel like LaTeX is not an efficient way to create a resume, unless you are very skilled with LaTeX macros and can essentially create your own "template", or modify someone else's. If you don't have those skills, you end up with a very bland, "stock LaTeX document"-looking resume, of which half the LaTeX resumes I see people share look like. I once tried to redo my resume in LaT…
LaTeX is not an efficient way to create anything . But, to be fair, it's not supposed to be efficient - it's supposed to be consistent . But I really wish it was less painful to use.