Handling Technical Skills On Resume

I’m an IT student completing my undergrad this semester. For the last week i’ve been updating my resume, portfolio, references, etc to prepare for job interviews in the coming months. I’m primarily seeking jobs as a software engineer and/or web developer. For the most part this is all going smoothly, however i’m having difficulty deciding how to manage technical skills in my resume.

Being a recent graduate (who is seeking a technical job) i’m assuming that recruiters are interested in the technical skills i’ve developed. My problem comes in finding an effective way to list/group my technical skills.

First question: should I include technical skills on my resume?
Second question: what is the best way to list, group, and rate (on experience or proficiency) this information.

My current method has two different lists.

Software:
name of software - proficiency*

Languages & Technologies:
name - proficiency**

*possibilities - Proficient, Familiar
** possibilities - Extensive Understanding, Moderate Understanding

Thanks for your input.

In my last resume (the one that got me my current job), I divided my experience into time ranges. For example, I have 10+ years’ experience with a, b, and c, 5 to 10 years’ experience with d, e, and f, a strong working knowledge of g, h, and i, etc.

If it’s an HTML resume, make every technical term or acronym a hyperlink to the definitive resource on that subject. It will show that you have at least researched the subject matter you’re claiming to know about.

Whatever you do, do not BS or stretch the truth at an interview. People see through that and you will end up on the slush pile.

[FONT=“Georgia”]Mine is similar.

Don’t worry about if there’s a ‘right’ way to display things. Do it whichever way is logical.

[/FONT]

I list skills that a) I’d feel comfortable enough working with daily, and b) I won’t hate myself for working with daily. If I don’t know something well enough it stays off my resume. If I do know it but don’t like it, it also stays off my resume. I personally wouldn’t call out proficiency level unless you’re really good at one particular language or skill.

Yeah I might not hit every point on some resume-scanning software but that’s OK with me.

I tend to rank information by order of relevance / importance. Firstly people want to know what skills you have (education and technologies / languages), then who you’ve worked for (most recent position at the top) and finally any additional skills you have (such as software usage). People want to know your right for the job so if you order it in this way they can check what you know, where you’ve been and the bells and whistles, it’s the order I’ve used for years and it works for me. :slight_smile: