I'm talking from the other side of the fence, as someone who reads CVs.
When I get a CV, I look at:
- The # of pages (1-2 is ideal, 3 could be ok), if it's much longer, I may only skim it.
- Answers to the main questions: What did you do? What do you know? What did you study?
- Then I look for all the fluff, the less the better. I hate CVs which claim to know everything, like a programmer taking 4 pages to say he knows: Basic, Cobol, Pascal, Modula-2, Scheme, C, C#, C++, Java, Delphi, Php, Python, Perl, Objective-C, ..., TCP/IP, Netware, Windows NT3.5/NT4/2000/2003/2008 Server, Windows 3.0/3.1/95/98/ME/2000Pro/XP/Vista/7, Cisco CCNA, MCSE, Linux, Ubuntu, Redhat, ..., ASP.net, Visual Basic 6, VB.net, Ajax, XML, Hardware maintenance, ..., ...
Believe me, the more you put in your CV, the more obscure questions I would ask you, if you put in Linux because you played with it for a few days, I'd ask about your favorite distribution and why, your favorite shell, what does NIS do?, what is NFS? I find most people would not know the answers.
I also had people claiming they did some things, and in the interview I find out, they were a small part of a big team, and all they did was "bring the donuts".
If you don't know it well, don't put it on your CV.
The perfect CV:
- Has 2 pages max, with the most important info (to the person you're sending this to) on the first page.
- Contains things you know from A-Z, if you haven't really used it yourself in a real project, don't include it.
- Contains where you worked, and for how long, as well as your accomplishments there.
- Contains information about your education and certifications (yawn)
A CV's objective is to get past the first filter, and to get to an interview (most likely a phone interview first).