Skills on a resume?

wrykyn

Definitely skills2 "To his dog, every man is Napoleon"

eggie5

I think seeing the 5 stars on C and C++ is really impressive. /\ |_ E X E GG

Andy Brummer

I like the layout as long as you have enough room on your resume. First, for each skill list the number of years you have worked with it, since that is what people want to know. It's easier then translating from the start date. Second don't give yourself the highest ranking for any of your skill levels. It looks bad, and it is one of those common "trick" interview quiestions. If you give yourself 10 out of 10 or 5 out of 5, then people expect you to have written the book on the subject.

If you don't kill me you will only make me stronger That and a cup of coffee will get you 2 cups of coffee

Jeremy Kimball

Generally, I like #1 better - it's similar to what I use. Two things: 1. Not sure about the stars - I used a novice/medium/expert scale. 2. Add in a "last used" column. For example, on mine, I've got a column like so:

Skill aptitude years of exp last used

DSP Assembly Prog. medium 4 2001

Jeremy Kimball Catapultam habeo. Nisi pecuniam omnem mihi dabis, ad caput tuum saxum immane mittam. (I have a catapult. Give me all the money, or I will fling an enormous rock at your head)

ColinDavies

Actually I like the stars, it makes it easier for the reader to follow. Mind you nothing beats a good handshake Regardz Colin J Davies

*** WARNING *
This could be addictive
**The minion's version of "Catch :bob: "

It's a real shame that people as stupid as you can work out how to use a computer. said by Christian Graus in the Soapbox

Andrew Bleakley

That's about what I always use, and have found it the clearest way to indicate your capabilities to a prospective employer without boring them to the tears.

Tim Smith

Being someone who hires people, I would use #2. #1 provides too much information that nobody cares about. It also looks really geeky. #2 provides just the proper amount of information without requiring me to dig into the data. Tim Smith I'm going to patent thought. I have yet to see any prior art.

Vadim Tabakman

I completely agree. After going through several interviews about 4-6 months ago, I found that the interviews only want to know what knowledge you have. Not specifics, more general like C/C++, MFC, .NET, and the number of years you've been coding. Any more specific than that, and they bother reading it. It comes down to if the interview reads your resume and your general skills match his criteria, then they'll get you for an interview and then ask you specifics. I think with resumés you have to keep it short and sweet, but still sell yourself. :)

Navin

I noticed that on both, you mention "Visual Basic". Be aware, that may end up being a liability. :-D :-D (p.s., I like format 2. While I'm not "The Boss", I'm sometimes one of those technical guys who winds up interviewing people and sifting through resumes.) "Fish and guests stink in three days." - Benjamin Franlkin

Jason Henderson

I doubt if they would look at your self-ratings without skepticism. I would leave those out and let your references heap praise upon you.

"Live long and prosper." - Spock

Jason Henderson
blog

Rocky Moore

Yeah, I wanted to show them that I can endure pain and suffering if required ;) Rocky <>< www.HintsAndTips.com www.GotTheAnswerToSpam.com

Rocky Moore

Jason Henderson wrote: I would leave those out and let your references heap praise upon you. But that would mean I would have to pay the references more, right :) Rocky <>< www.HintsAndTips.com www.GotTheAnswerToSpam.com

MS le Roux

Perhaps you should use 2, but group the information to improve readability. And perhaps list the more relevant skills first, e.g. ASP .NET before ASP. For example Expert Knowledge Skills - ADO.NET, MS SQL Server 7, 2000 - Stored Procedures / Triggers - C, C++, C#, MFC - ASP.NET, ASP, HTML - WinAPI, WinForms