What do you want to do?
If your CV is vague, it's likely to get rejected
I've been screening a lot of developer/architect CVs recently and I have to say that it's getting harder to actually determine which candidates I (and others) think are going to be above average. The two main reasons for this are that most developer CVs now look like the same vast array of buzzwords and also, so many CVs are just too vague.
While there are some great ways to make your CV stand-out from the crowd (this is a good example), there are a couple of really simple things you can do to make sure that anybody reviewing your CV has enough information to make an informed decision.
- State exactly what your role was on your previous projects : the purpose of and technologies used in the project *are* interesting, but I want to know exactly what your role and responsibilities were.
- State exactly what you want to do : saying that you're capable of everything from hands-on development through to strategic consulting is all very well, but if you don't tell me what you want to do, I won't be able to visualise the right role and career path for you.
If your CV is vague, it's likely to get rejected.
Re: What do you want to do?
Re: What do you want to do?
Its a dilemma. CVs are an extremely poor way of conveying what a person is really capable of.
Perhaps the best approach is to build a strong relationship with a preferred agency, and allow them to perform the screening process using a carefully prepared set of criterion. Of course, a few good peeps might slip through, but you might end up finding someone with a relatively poor looking CV, but that has an incisive mind, and communicates better through more verbose means than is acceptable with a CV.
Simon is a hands-on software architect who works within 