One of my clients is currently looking to hire a full time systems administrator (More details here), and we’re finding it incredibly difficult to find the right person. Whilst we do get a lot of CVs, I’m finding it incredibly frustrating getting solid candidates that I even want to interview. On the whole the CVs we get are very poor.
So, I thought, partly as a way to vent in a hopefully humorous and - perhaps - useful way, as well as an exercise in double-negation, I’d explain how you can guarantee that you will NOT be getting an interview when I’m looking at your CV, simply by following these easy steps:
- Use an agency that massacres careful formatting in your CV, and applies some of the rules below in a destructive and unhelpful way.
- Ensure that your CV does not contain your name. Really, it helps that we don’t know who you are. Maybe an arbitrary reference number that means nothing to me instead?
- Even if you do include your name, state the blindingly obvious by declaring as the first thing I read that the CV I am in fact looking at is, indeed, demonstrably a Curriculum Vitae
- If you do use it, please make sure you misspell Curriculum Vitae.
- Come up with an opening gambit that is grammatically incorrect, so I know that you spend lots of time on a computer and never read anything other than slashdot or digg.
- Misspell much of your carefully considered opening gambit. I mean, I don’t expect you to actually know how to use a word processor you list as a skill.
- Make no use whatsoever of the word-processors “advanced” features such as styles or formatting. Agencies can help here by copy and pasting with abandon and disregard.
- Ensure you tell me that you have a full driving license for that desk job in central London.
- Ensure you have lots and lots of keywords for products and technologies you don’t really know that well.
- Put everything down you can think of, no matter how brief your involvement, so we can have one of those really awkward interview moments where you realise you’ve wasted not only your time, but mine too.
- If you can’t think of some buzzwords, put “etc” in quite liberally. It’s really helpful because it shows you know the specifics so well, and it helps me fill out the all important details.
- Misappropriate some concepts, or demonstrate that you don’t really mean what you’ve written. Just to be helpful.
- Education. Please list everything you’ve ever done. Get that swimming certificate in there, as well as that Metalwork GCSE ‘F’ grade you’re so proud of. Because it makes all the difference when I’m comparing your CV to the person who just stated his highest level of achievement I interviewed the other day.
- Experience. Please list every contract you’ve ever done, every last one of them. Even that two month part-time contract you took for a short period whilst you were travelling in Australia just after you graduated.
- Don’t ever list a contract you did that was extended by your employer because you were quite good at what you did. Let me do the guessing.
- In fact, don’t even distinguish what’s a contract and what was actually a permanent position you hated.
- As to those permanent roles, inflate your involvement to the maximum degree possible, so when I ask you to describe your involvement in the project in that interview you’re soooo going to get, it matches what’s on your CV
- Use those lists of skills, education and experience to the max. Lots of long lists making the worst possible use of space, so it spreads over six pages without saying very much. Short, concise well-formatted CVs are for losers.
- As far as outside interests are concerned, do yourself proud and list all the things you think any self-respecting geek would do, like play with computers and socialise. Constructive, strange or interesting things with your free time just don’t cut the mustard.
- You know that really awful perl script you wrote that mangled so many concepts it resembled a 3-year old’s attempt at technical lego construction? Put that on the internet as an example of your code. Because I won’t really download it and look at it. Much less actually consider it as representative of what you’ve done.
But seriously, I find it quite shocking how many CVs that cross my inbox are simply:
- Badly spelt, with poor grammar. Nobody is perfect, but some mistakes really are unforgivable.
- Badly formatted. Long lists of skills you don’t really know any more, or are ‘learning’ are not appropriate. Keep it short, concise and - if possible - intriguing. Make me want to interview you to find out more.
- Badly considered for what is the first, and perhaps most important part, of getting a job. Take a look at it, and ask yourself what impression it gives.
A little bit of time and effort makes all the difference, as well as keeping it up to date every now and then (even if you’re not looking for a job). Show you know what you’re talking about, that you have as much pride in your CV as in the natty suit you’ve picked up for the purpose, and that you’re not putting untruths or inappropriate content in your CV.
A lot of the blame certainly rests on the shoulders of the agencies that don’t filter or check the CVs and just forward all the CVs that contain keywords (What value do they actually add?). Of course that is even before they even mangle them horribly to suit their template, but so much of it rests on the candidates shoulders.
At the risk of setting myself up for a tremendous fall, here’s my CV. Perhaps I’ll even rework the above into something a little less cynical when I’ve a bit more time….


January 15th, 2007 at 2:01 pm
I can’t agree more. Particularly on the point of agencies - wouldn’t it be great one day to deal with an agent who actually knows something about the industry and could recommend people with appropriate skills, rather than sending webmonkeys for sysadmin jobs?
Anyway, as you know Rich, there are only two important questions to ask any candidate:
i) do you have a clue?
ii) what’s the biggest fuck up you’ve been responsible for in a production environment?
January 17th, 2007 at 3:35 pm
Try this agency - OPUS2 Recruitment
02089716000.
http://www.connectuk.org/connect_public/default.asp?id=101
Connect - the union for professionals in communications
You will be surprised.
February 24th, 2007 at 8:45 pm
From ‘How (not) to write a CV’
‘Use an agency that massacre’s your CV’s careful formatting and applies some of the rules below in a destructive and unhelpful way.’
and…..
‘But seriously, I find it quite shocking how many CV’s that cross my inbox are simply:
Ooooops!
massacre’s, CV’s?
If I were you, I would edit my own work more carefully (or get someone else to point out your misuse of apostrophes before publishing)
February 25th, 2007 at 5:55 pm
Thanks for your comment David, and I’ve corrected the items you pointed out.
I confess that I got a little defensive after initially reading your comment - I didn’t initially feel like publishing it - as I felt you were missing the main point of my post. I certainly don’t think there’s much point in my striving - with a grade C in English GCSE some years in the past - to trying to be a beacon of grammatical excellence. I’ll leave that to Lynne Truss.
However, I realise that in complaining about grammar, and then going on to make simple mistakes, I could well be seen as setting myself up for a bit of a fall (Indeed, I point that out in my post). So I’m happy to take on board your comments, have fixed them, and continue to keep an eye out for what is perhaps my most frequent grammatical error when I write.
But the really big difference between my slips, and the main point I am making, is that a weblog such as this is an informal place for me, and my readers, to say pretty much what they want. I enjoy simply putting down my thoughts and opinions in words that are, to me, interesting, and hopefully of interest to others, and I don’t always go over them in fine detail prior to publishing, simply because it’s more akin to me speaking, than to a formal paper or article.
In comparison, a CV is very much a formal document, submitted by candidates, seeking a new job to advance - I imagine - their career, get more money, or improve their quality of life in some way. It really should be carefully put together, checked by others (agencies in particular), and strive to paint a good picture of a candidate. Atrocious grammar in such contexts is not a good start.
So, yes, bad me. But it’s really - I’d argue - not in the same league as repeated grammatical mistakes in CVs that I have had the misfortune to receive over the last year or so. My post was a light-hearted rant to try and draw attention to that, and I think by and large it succeeds in that aim.
August 14th, 2007 at 12:06 pm
Hi Rich,
I was looking for articles about CV’s and read your ‘rant’. How true! It is well-written and I would definitely like to pass on some of the comments to the students who would benefit from your - Not-To-Do-List!
Thanks again
Anita