18 ms·
Limecv – A LaTeX CV Document Class
- dhosek 9y agoI used to do my resume in LaTeX and it was gorgeous. I switched it to an uglier document in Word because most of the time my resume was getting put into some semi-automated flow and even a LaTeX-generated PDF file didn't do the job.
- pmiller2 9y agoI did the same, specifically because my 2-column layout gets mangled by most ATS import processes. limecv has the same issue.
- michaelhoffman 9y agoI started doing my CV in Pandoc Markdown for this reason. I usually produce a nice-looking CV PDF via LaTeX, but if I need Microsoft Word or plain text I can convert to that too. https://bitbucket.org/hoffman/cv https://bitbucket.org/hoffman/cv
- chrissnell 9y agoI've noticed far fewer requests for Word formats than I did in years past. I think that's largely because headhunter agencies have better tools for editing your resume and stripping out your contact info.
- B1narySunset 9y agoDo any interviewers notice resumes that are written in LaTeX compared to ones that aren't?
- pmiller2 9y agoI would, probably, depending on the level of customization.
- jedberg 9y agoI definitely do. I automatically give plus points in my head even though I know I shouldn't.
- tempay 9y agoShould you not? I'm sure having a LaTeX CV correlates well with other skills which you might deem desirable and, if so, it seems like a perfectly reasonable indicator to use. It shouldn't be used exclusively, but nothing should be.
- LVB 9y agoI 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 http://stevehanov.ca/blog/resume_comic.png
- deleted 9y ago[deleted]
- Xophmeister 9y agoYep; 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 :)
- sjy 9y agoHow can you tell that they used LaTeX if the CV is in PDF format, other than by guessing from the use of Computer Modern?
- blt 9y agoQuality of typesetting. Seriously.
- blt 9y agoSee e.g. the first example at http://www.zinktypografie.nl/latex.php?lang=en http://www.zinktypografie.nl/latex.php?lang=en
- saadat 9y agoLook at the PDF's "PDF Producer", "Creator", or "Application" metadata fields in a PDF reader application.
- zaarn 9y agoAfter a while you can just spot it, LaTeX has a much higher quality typesetting and layout engine than Word or other WYSIWYG on-the-fly editors. The easy way is usually to spot some of the no-no's of layouting; single words at the last line of a paragraph, sentences spanning over page breaks, spacing in block paragraphs, etc. It's easiest with letters or invoices with some text, where the spacing and word placing is most obvious but you can usually tell in CVs with less text too. Of course, sometimes Word gets lucky and does a proper layout, but I've found that it's rare that I get to see properly layouted word documents.
- pvdebbe 9y agoCrap. I like Computer Modern. :(
- Bromskloss 9y agoOf course. I mean, of course… https://xkcd.com/1301/ https://xkcd.com/1301/
- wyldfire 9y agoYes, it's definitely a shibboleth. IMO it's a full duplex signal. When I notice that an interviewer noticed, it can make me more interested in an offer from that place if I think I'll be working with that/those interviewer/s.
- chrissnell 9y agoI've been using this one for my resume and I love it: http://www.rpi.edu/dept/arc/training/latex/resumes/res.cls 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. This gives me a chance to learn about their interests and see their skills first-hand. Here's my LaTeX resume, built with res.cls and including a section about my OSS work: https://chrissnell.com/resume?latex https://chrissnell.com/resume?latex 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 on irrelevant characteristics until you've firmly established your appeal to the employer.
- swimfar 9y agoIn a number of European countries it's common/required to include a headshot on your CV. Birthdate is also often included. But I agree that, whenever possible, don't include this information.
- sh_123 9y agoYou wouldn't happen to have a repo of your LaTeX resume? It looks great and would love to use yours as a guide.
- Y_Y 9y agoStarting with your "Passions" felt really offputting and weird. I don't think that that list is stuff you are genuinely "passionate" about. That said I, I don't hire people, maybe it's effective.
- chrissnell 9y agoA hiring manager needs an easy way to see what you're all about. Many candidates put a word cloud of technologies and software here but I've found that people are often pretty weak on many things included here. Word clouds don't have any context, either. The hiring manager has know way of knowing if this person knows just a little bit of a technology or if they do it all day, every day. I call them "passions" because these are what I love to do at work. I'm confident about talking at length about any of them.
- mskalski 9y agoLooks nice. I also like https://github.com/posquit0/Awesome-CV https://github.com/posquit0/Awesome-CV
- michaelmior 9y agoThat does look cool, although arbitrarily making the first three letters of section headings a different colour is really weird to me.
- Wehrdo 9y agoThis 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 LaTeX, and after finding a decent-looking template, spent a lot of time fighting it to do simple things that weren't built in, like add my GPA to my school listing. In the Limecv template, what if I don't want the "stats" bars? Better go browse through a 2000-line template that I didn't write to figure out how to remove them. I ended up actually doing my resume in HTML/CSS, which provided me the flexibility to lay things out exactly how I wanted, which was quite nice. The main difficulty I had was getting a consistent PDF layout, as Chrome's PDF print is pretty much a black box that you have no control over.
- michaelmior 9y agoWhile some LaTeX templates are more unwieldy, in the case of Limecv, if you don't want the stats bars, just don't include the macro that adds them. It's not always so terrible.
- username223 9y agoSpeaking as someone with a LaTeX résumé, I agree with you. I use it because it's the typesetting tool with which I am most comfortable, not because it's the best tool for the job. I would never use HTML/CSS to create a résumé, but that's because I am bad at using them.
- benou 9y agoI "ported" moderncv LaTeX style in simple XHTML/CSS a while ago here: http://www.benou.fr/~ben/cv/cv.en.ganne.html http://www.benou.fr/~ben/cv/cv.en.ganne.html Feel free to clone it if you find it useful. I use both moderncv for PDF and this for web-based resume.
- IvanAnishchuk 9y ago
- tom_mellior 9y agoI find this looks to busy, but I guess that's partly because the example tries to show off as many features as possible. Personally, I use moderncv: https://ctan.org/tex-archive/macros/latex/contrib/moderncv/ https://ctan.org/tex-archive/macros/latex/contrib/moderncv/ It doesn't look very fancy, but it's actually simple and clean. (See the exaples directory.)
- technocrattobe 9y agoHello
- yzmtf2008 9y agoHere's my attempt at creating a Resume/CV with HTML/CSS: https://github.com/andyfangdz/resume https://github.com/andyfangdz/resume, or https://cv.andyfang.me https://cv.andyfang.me 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.
- vista980622 9y agoPretty cool!
- mburst 9y agoA few years ago I had the desire to have a version controlled CV. This is what I came up with after spending a few hours learning about LaTeX https://github.com/mburst/resume https://github.com/mburst/resume 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/ http://www.maxburstein.com/blog/creating-resume-using-latex/ I still use it to this day
- bdamm 9y agoLaTeX has lovely output (thanks Knuth!) but isn’t really achieving the dream of content fully separate from presentation. http://resume.dammfine.com http://resume.dammfine.com Source is an XML document that describes my various experience, a system of XSLT that targets three forms; an HTML landing page, an HTML form of the resume as a document, and a LaTeX output for PDF. Haven’t updated my resume in 10 years but when I do it’ll be pretty straightforward to keep going with the system I wrote 13 years ago. I should really post it to github, as others have done with theirs.
- taeric 9y agoTo be fair, that was never Knuth's goal. And, really, for most documents the presentation is no small part of the content. As much as we might wish otherwise.
- j7ake 9y agoAny recommendations for a plain academic CVtemplate ?
- Myrmornis 9y agoThe ideal is to separate content from presentation. A LaTeX resume template has done that for an extremely small proportion of all the people who have used a LaTeX resume template.
- taeric 9y agoWhat makes this the ideal? I'm not saying that I want my content completely mixed in with formatting options on every word, but by and large the presentation is a part of the content of anything you do. To that end, I want it to feel natural and to be somewhat easy to reason about. Not to be absent.
- Myrmornis 9y agoI mean, this is the basis of web design, and the programmers' long-standing criticism of WYSIWYG text editing. Perhaps I worded it wrongly: content should be tightly attached to semantics, but it should be possible to switch out the particular rendering used for those semantics. LaTeX resumes always fail in that regard: for example, in the template given in this thread, the semantics of "measures of experience in different languages" is inextricably bound to the rendering choice of stars. Or even more basically, the semantics of "a job or educational position held for a period of time with summary metadata", is with a LaTeX template tightly bound to a particular layout. Of course it is possible to design a TeX/LaTeX macro system that gives you separation, but, in reality, TeX is very wonderful, but learning the guts of the underlying macros is always going to be a niche audience.
- taeric 9y agoDon't get me wrong. It is a popular taking point. I just think it is wrong now. Specifically empirically. My "hard to manage" macros have maintained better than any of my friends resumes in other formats. With basically no effort, all told.