Word documents? Get a real job
For a couple of years now when job hunting, in lieu of emailing around my CV as horrible Microsoft word documents, or that most frightening of modern digital afflictions being cast upon unsuspecting web users - the PDF - I’ve used a plain old HTML document. It works because unlike Word or a PDF viewer, everyone has a browser and after all, we are supposed to be web people, no?
The regular rules of CV writing apply
I don’t have to go over the rules of CV writing. You know the drill already:
- keep it simple - no insane graphics or colours. Just because we’re using HTML doesn’t mean that it’s a website!
- be concise
- summarise your most recent work/projects
- customise the contents of your CV for each position
- discard fluff.
There are a boogzillion of sites out there to help you. Google it.
Some employers may not understand
Not all geeks are hired by geeks. Some people won’t be able to comprehend why in the cahoots you’re sending them a webpage. “Hmm, is it safe for work? Will it contain a virus?” These seem stupid questions to us, but to someone used to seeing 100s of CVs every day for the past 20 years, well, that would be enough to send anyone batty.
So to prevent confusion, write a short explanation at the footer of your email such as: “I attach my CV in HTML format for you consideration. You can open it in any web browser (Internet Explorer, FireFox or Safari for example)”.
It’s probably not a good idea add JavaScript or link to external dependencies such as images or css files as you shouldn’t rely on there being an Internet connection. And we all know how IE throws a wobbly when it encounters local “active” content. Excuse me while I vomit.
However in such cases it might be justified to include graphics or even JavaScript, for instance if you’re going for a design or developer position. In these cases, if you can’t link to site, make sure you inform the recruiter just what they can or should expect when they open your CV or examples.
Most of all, don’t give them too much to think about. Requiring a non-technical person to install Flash player does not make a good first impression and they might just give up and hire the guy who sent an ASCII picture of his pony.
Ok, let me see!
Here’s my example: example-cv.html
The file itself uses XHTML strict with styles in the body, including print styles (yes, people still print CVs and they may even want to bring one in to the interview!) with a teeny conditional hack for IE. I make use of position:fixed to add navigation but have disabled it for IE6 since it doesn’t support it.
I’ve tried to use standard markup along with microformats for the address area, but I don’t doubt that it could be improved.
Feel free to use it, trash, reskin it or whatever - just don’t blame me if you don’t get the position. If you do decide to do something with it, I’d appreciate a looksy!
Oh yes, good luck by the way! 
January 30th, 2008 at 4:24 pm
I often use HTML in place of word documents, especially for web documentation. Frankly a good HTML document is much easier to create than a good word doc! Dreamweaver handles headings really well, Word fucks them up regularly.
IE’s local content/script freakouts actually prevented us putting an HTML-indstead-of-word document into general circulation back at Griffith. We encoded the logo and embedded it in Javascript, worked a treat except in bloody IE! It was a self-contained document complete with corporate branding.
January 31st, 2008 at 3:48 am
Yeah, it makes so much sense to place web documentation in HTML. Particularly for code examples where what you see in the docs is what you’ll get in a browser. No screenshots, no word, perfect! Even linking to the live css/images from the docs so that changes are reflected in real time. Use SVN and you’ve nearly got a decent system.
And besides, any standard is better than none.