Looks nice. To nit pick, I am a believer that, unless you are a recent college grad, your work experience should come first, before your education. Unless you are applying for a teaching job, or you otherwise want to purposefully highlight your educational achievements, I feel that a few years after graduation, what you did in school is mostly irrelevant.
I agree with you wrt software jobs, but overall it varies by field. The linked example is someone who is a Phd student, so I'd say it's pretty relevant to be at the top.
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.
I might as well take this opportunity to plug resume.rb (https://github.com/mwylde/resume.rb) which allows you to define your resume using a simple Ruby DSL and then render it to various outputs (currently supported are plain-text and PDF via LaTeX). Here's  an example ruby file which generates this  PDF.
The support for plain text is important. When I applied for my current position, I sent a TeX generated PDF of my resume. When I arrived for my interview, what they had in hand was as if someone had OCRd it, done a "strings" on the result and then pulled it into Word - barely comprehensible and ugly as puke. Of course, I had brought lots of paper copies with me.
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 used to keep my resume in TeX. I don't anymore. I just use a simple format in Word. PDF is fair, but most of the IT job market infrastructure is based around dealing with word docs & electronic copies so frankly the appearance isn't that important (other than basic legibility). I found it much easier to get work once I bit the bullet and move my resume into a word doc.
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 used to spend hours working on my resume in LaTeX, under the belief that it would buy me geek cred from employers who could recognize the typesetting. Not one person ever noticed it and the hassle from recruiters that wanted a Word doc finally motivated me to switch to Word. Sad but that's the way it goes.
As a counterpoint, I've recently had two interviewers recognize (and comment) on me using TeX because they recognized Computer Modern. One commented that I should have typed '\latex' instead of just 'latex' (I agreed of course, but mentioned that I didn't want to be too flashy). I got offers from both.
I don't use recruiters, preferring to rely on personal connections, but would they really balk that much at a PDF resume?
I think that discovering which recruiters will hassle you for Word files is a feature, not a bug.
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.
I'd be happy to get into that first category and then prove you wrong on the flag in an interview, unless step three is the trash...
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.
Are you sure you have enough data to make 1) a fact ?
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.
I meant `sensible' purely in the technical sense. Postscript is superior to pdf. pdf is basically a stripped down postscript in binary format as a premature size optimization. ps.gz is usually smaller than the equivalent pdf.
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 would say my comment was purely about the "user-friendly" point of view, which overlaps technical and social. The right answer, speaking from a technical worldview, is always at least related to what is user-friendly. Technically superior is the same as technically worthless if nobody can use it.
I used ps (in favour of pdf) whenever I can get away with it. Especially if I am the consumer of the data and can decide which format somebody else prepares for me. E.g. when downloading scientific paper there's often a .ps version.
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.
We've switched over to LinkedIn's job application feature which just PDFs up your LinkedIn profile and sends it to us when they click on apply on our website. I don't believe there is even a place to attach a normal résumé anymore.
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.
Seems too cumbersome. Plus, mixing the resume information with the formatting looks like a maintenance nightmare.
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.
Perhaps it's just the font, but this and most other Latex resumes scream "I was made with Latex!" For some jobs, that might buy some geek cred, but I wanted to make mine less Latexy. What do you think? (Disclaimer: content is crappy and outdated)
I really do not like the italic text. Immediately thought of cheap newspaper classifieds. Maybe just not make that italic? It is already lighter than the main headlines so it might be different enough.
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."
once done with your resume/cv, do us a favor and try it with our resume analyzer - it'll tell you a lot of things about the quality/content of your resume (and other things you might have missed). it's free, and automated.