CV/Resume's for Devs'

Pho3nix

Pho3nix

The Legend
Joined
Jul 31, 2009
Messages
32,827
Reaction score
3,033
Location
On the toilet
Hi guys,

Looking around for new employment and revising my Resume as a result. I know there are tons of threads about this but I wanted to ask about how Software houses "prefer" to see on a dev's CV/Resume. Should I mention the Clients and Projects I've worked on or just the skills I have?

Really confused as to how to go about it and should it rather be straight to the point (2pages ) or 5 pages. And reasonable number of references?

Thanks alot guys.
 
Pho3nix said:
Hi guys,

Looking around for new employment and revising my Resume as a result. I know there are tons of threads about this but I wanted to ask about how Software houses "prefer" to see on a dev's CV/Resume. Should I mention the Clients and Projects I've worked on or just the skills I have?

Really confused as to how to go about it and should it rather be straight to the point (2pages ) or 5 pages. And reasonable number of references?

Thanks alot guys.
Click to expand...

You using an agency or applying directly?
 
2-4 pages is perfectly fine!

1) personal details etc
2-3) schooling and past work experience.
3-4) specific technologies

You should also put the various projects into your work experience.
 
There's some pretty good advice on sites such as lifehacker to improve your CV/resume. If the site allows you to upload your own files, make sure that it is of a high standard. If potential employers are viewing it directly, they may not be too impressed by a poorly formatted or badly written one. Sometimes only recruiters are looking at those sites, in which case they may reformat it to their standards/template before sending to an employer.
 
I hear you..As to Projects I've worked on. Do I put everything I've worked on in the past two years or just the last 2-3 months?
 
Pho3nix said:
I hear you..As to Projects I've worked on. Do I put everything I've worked on in the past two years or just the last 2-3 months?
Click to expand...

Put things on that you are most proud of, if you've done them two years ago or 2 days ago.

If it is a great feat then add it. Also don't be shy adding your not so great projects. Everything you've done is great.

Software development is Great!
 
Toitjie said:
Put things on that you are most proud of, if you've done them two years ago or 2 days ago.

If it is a great feat then add it. Also don't be shy adding your not so great projects. Everything you've done is great.

Software development is Great!
Click to expand...

Agree with this. Also, a single sentence or so per project. Highlight what you thought was interesting about it. I've never looked in detail at CVs with millions of little details.
 
Pho3nix said:
Hi guys,

Looking around for new employment and revising my Resume as a result. I know there are tons of threads about this but I wanted to ask about how Software houses "prefer" to see on a dev's CV/Resume. Should I mention the Clients and Projects I've worked on or just the skills I have?

Really confused as to how to go about it and should it rather be straight to the point (2pages ) or 5 pages. And reasonable number of references?

Thanks alot guys.
Click to expand...

What type of dev work are you looking for? Web, enterprise?

I prefer a short cv. Personal details, education, work xp and skills matrix. And of course a "cover letter". The cv is only to get your foot in the door. It's the prac test you have to worry about.
 
Skills matrix is ok, but not that important imho.

As far as the practical test goes, companies that interview and only use this as a gauge of technical ability should revisit their interview strategy. Yes, it's an ok gauge, but problem solving ability with logical questions is more telling. Also, dev work is more and more about people interaction also. Gone are the days where you're locked up somewhere to produce code until it's done. ;)
 
kripstoe said:
Skills matrix is ok, but not that important imho.

As far as the practical test goes, companies that interview and only use this as a gauge of technical ability should revisit their interview strategy. Yes, it's an ok gauge, but problem solving ability with logical questions is more telling. Also, dev work is more and more about people interaction also. Gone are the days where you're locked up somewhere to produce code until it's done. ;)
Click to expand...

Those prac tests are there to test your problem solving ability. If your prac tests don't do that THEY should be revisited. But agreed, it can't be the only part in the interview process. It is a good gauge as to whether one should even bother getting to the actual "in person" interview.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X