I'm interested in hearing counter arguments.
First, the education section takes up relatively little space, and a good school will quickly get the reader's interest.
Secondly, by the end of your work experience section, the reader has probably formed an opinion of you, and a good school won't do much to recover from a mediocre list of jobs.
Of course, none of this actually affects your qualifications for the job. However, HR people usually see things a bit differently than an engineer would...
On the other hand, if you're a developer and still have your degree at the top of the page after 7-10 years, my gut-check-needle drops into danger zone and while I will read the work experience part, I do it with the knowledge that you think you've wasted all that valuable learning time. This is extra true for people from prestigious schools.
To answer why I do the opposite, I am (still!) working in France, and unfortunately academic achievement and diplomas are more rated than experience, when you are under 30 (which is my case).
When I do a resume that targets the USA, I usually remove the picture and invert those parts.
EDIT: Embarrassingly, I seem to have lost my bullets. Have to dig back in and find them.
Thanks a lot :)
This is the .tex file I started with: http://matthewm.boedicker.org/doc/resume/resume.pdf
then I took my Word resume (that had the shading, and some other things) and converted it into this:
I made it because I loved my Word resume and I didn't like any of the LaTeX resumes out there on the Web. I also hated Word and loved using LaTeX.
It made it into CTAN as a .sty file thanks to the efforts of George Louthan:
Example using tucv package: http://mirror.its.dal.ca/ctan/macros/latex/contrib/tucv/tucv...
Personally, I hate using .sty or .cls for a resume. I think using a .tex file as it allows full customization/tweaking of the entire file, easily. A resume isn't something that can be easily generalized to a .sty or .cls IMO.
I just print to PDF from there, and attach the result.
For HTML5, you could include HTML5 features like microdata or use some of the HTML5 tags. The design though is great - very clean!
I personally author my resume in XML and transform it into various formats using XSLT.
This is also great if you are just getting into LaTeX:
I was only half-way serious when suggesting postscript. Postscript is a nice format that you can write by hand. And it does meet your "need [for] more print-specific control."
Since you are sensible you don't want to write postscript by hand, but I don't know of any tools that help you produce better postscript than pdf.
(For technical reasons postscript is the superior format though. PDF is a prematurely optimized postscript. pdf-files usually have a smaller file size than ps files, but .ps.gz easily beats pdf, and you can change it with your favorite editor if you want.)
I think basically all latex users have been passing around variants of the same GPL resume template for ten or fifteen years now. :)
I don't use recruiters, preferring to rely on personal connections, but would they really balk that much at a PDF resume?
There is no good reason for them to require Word that doesn't, ultimately, come down to them either a) being too lazy to cut and paste into a database, or b) wanting to "improve" your CV before passing it on.
1) I can usually tell that you wrote your resume in TeX
2) I then classify you immediately in the "advanced geeks" category, with a "probably hard to work with because is picky" flag...
I personally think it is more about using the right tool for the job than picky-ness. I like the way TeX looks and there are some things that you can do very easily (and maintainably) compared to OO/Word.
I doubt that anyone but very, very few, writes resumes in TeX. LaTeX, yes some. TeX ? Nah.
Someone in command of LaTeX, can make a CV look essentially like whatever they want, so 1) is perhaps not as "usually" as you think.
Regarding 2), what, if anything, do you conclude about an applicant's level of geekiness if you believe you have identified their resume as having been written in Word ?
If you really use this strategy and you are a hiring manager in an area related to technology or computing/programming, someone should seriously consider if it is to their advantage having you involved in the hiring process.
Being picky about your tools and what you produce should be a positive sign. It shows that you care. It doesn't say anything about how flexible the person is.
I wouldn't send out postscript files to people I don't know, since you can't assume that people are able to read them.
I assume your comment was purely about the social point of view? Or are there technical reasons for foregoing postscript documents you may want to print? (Especially reasons that didn't exist 30 years ago.) Thanks!
I wouldn't want to force other people (especially non-geeks) to learn about data formats they don't care about. And after all a pdf is still better than MS Word.
Sadly no one cared; recruiters wanted MS Word or RTF and employers valued beauty in phrasing over beauty of typesetting and so I hired a CV writer and stuck to Open Office / Google Docs.
Hope it works out for you though!
Generally not a good idea for a simple, b/w, serious layout.
If I remember correctly, even horizontal rules weren't that common back in the days. German/Swiss typography called them "English lines", so I assume they were more common in the UK.
There is not in existence a page with a rule on it
that cannot be instantly and obviously improved
by taking the rule out.
Having software set up properly is IMO a good case for a web app; with scribtex, all you need is a text editor to produce good pdfs.
I highly recommend it.
(Please keep it in business.)
i like typesetting, so naturally did my best. it uses the pagella font that is often used for books (with 'low case numbers' -- i love those). except the h-lines and some bullets everything is made of text. uses hyper-refs where applicable, in dark blue so 'print safe'. everything is open source, how to compile this on ubuntu is in the header comment of the tex file.
it is originally based on a file found on toofishes' blog:
please let me know what you think!
That's why I store my resume as XML (model) and transform it into HTML (view) using XSLT (controller). The XML file includes my complete resume, and I use XSLT to generate different resumes that each display a subset of that information. It's as simple as myname.com/resume/dev or myname.com/resume/dba. The resulting HTML also copy and pastes well into Notepad or textarea form fields. I can also take this same XML data and convert it to PDF using a server-side PDF library.
If I ever get around to updating the code behind it, I'll convert it to HTML5/canvas.
(the content is still from college days when I had no real experience, so please don't judge the content)
Yours looks nice, and has less of the LaTex feel to it:)
You can see a sample TeX file at http://polibyte.com/files/resume-20110908.tex and the PDF output at http://polibyte.com/files/resume-20110908.pdf
I like the modernCV format a lot, I'll likely try to crib some features from there.
This plus the links in the comments are a great starting up point for someone looking to do this for the first time, something I wish I had years ago when I started.
Will share the .tex if people want it.
I hadn't thought to add example output.
Monospace for "internet things" is geeky, looked weird.
Lose the "(primary)" at the cell number unless you add another number.
Bullet points maybe?
"company." as single word in a line is sub-optimal.
"development teams of 2-5." -> "development teams of 2-5 people."
"Email" -> "E-Mail", I am not sure about this.
You silly Amer. wi. al. your abbr. in addr. :)
And yet, all the TeX resume/CV examples I ever see are fairly boring.
Here you can download my archive: http://uploading.com/files/3c95c534/resumes.tar.gz
It contains pdf and tex versions of the resumes of following people; elizabrock, mikepark, pavpanchekha, rlipman, rpetti, stuhood
I hope that this archive may help you guys.