In a nutshell I want to cite open-source and/or side project work on my resume (either in chronological or functional format), as I currently work as an engineer that performs primarily maintenance and support on applications built with legacy technologies and want to really highlight my "peripheral" experience with more current frameworks (.NET 3.5, etc.). Has anyone done this and if so, what has been your approach?
I appreciate any relevant feedback....thanks all.
Regards,
Todd.
I rank open source projects lower than professional experience, but higher than hobby projects. Each has their own section, all in roughly the same format.
As someone that reads resumes from time-to-time I would say include the projects very prominently with a link and a description of the main areas of the project you worked on. When hiring programmers there's nothing better than being able to check out a bit of code (so don't include the project if it's bad code). Also include a link to the page where your name is mentioned or in the credits so that whomever is looking over it can easily verify you were actually involved.
1/ Mention about this in the summary - which you typically put on top of the resume.
2/ Put this right after your professional experience
3/ Add the technologies that you learned in these side projects to your "skill-set-box"
It's already obvious that the benefit of this will greatly depend on the reader of the resume. For example, I don't weight hobby projects lower than professional experience simply because they show a passion for the job that goes beyond money. On the other hand, you may simply be a maverick and not beholden to the job or want to work on your hobbies on company time. It's not clear-cut.
That said, you want to expose them, so do so. I would suggest that you have a section similar to your education history for your open-source projects, and that you include URLs and your userid wherever possible. This makes it possible for the interviewer to verify your code skills before getting to the interview. It shows a level of confidence that can be refreshing. Not arrogance, just confidence. Arrogance is confidence without ability, but you're providing evidence and proof.
Open Source and Hobby Projects
As for where, well, are these better than your professional experience? If so, put them at the top (most likely, you're a recent grad, so your education is up there, too). If not, put them after your professional experience (most likely, you're not a recent grad, so your education is after the experience section, too).
Just my two cents.
Be sure to clarify what you actually did.
Looking at an open source project is one thing. Dabbling is not very interesting.
Using an open source tool or component is a basic skill. "Manage Apache" or "Configure MySQL" or whatever.
Using an open source component to build something is an interesting thing. What's interesting is you built something. Using open source (or commercial products) is of secondary importance -- what's important is what you built and how well you can build something else.
Contributing to an open source project is also interesting. What's interesting here is that you built something. What's important is what you built and how well you can build something else.
The issue of Open Source contributions vs. commercial software is one of overall quality. When someone's paying you, there's a kind of independent audit of your quality. If they don't like it, they stop paying you. The supporting details are available when the prospective employer checks your references.
For open source, the independent audit is the number of downloads. The supporting details are the number of downloads.
In my opinion a private project may be even more important than "professional experience". If you do maintenance with legacy technologies (like me coding something in old .NET 1.1) it is probably worth nothing.
On the other hand, if you've played with, for example .NET 3.5, MVC and maybe have a working site online it is much more valuable.
It is highy likely than in your "professional experience" you've only seen a small part of the big picture. In a private project you've done through the whole lifecycle on your own which is commendable.
So put your side projects (the ones you're proud about) prominently on your resume.