Slashdot Mirror
How To List FOSS Experience On Your Resume
maximus1 writes "If you're selling skills gained in an open source project, you have additional opportunities to shine, say experts in this ITWorld article. But what is the best way to explain your FOSS experience? 'Someone stands out because of how they talk about the project, says Zack Grossbart, author of The One Minute Commute. His advice is to describe the project and discuss your contributions in detail: 'If you were a committer, what did you do to earn that status? What features did you work on? Did you design new areas, or just implement predefined functions? Did you lead meetings? Define new architecture? Set the project direction?' If the FOSS experience is part of your background but not a shining beacon or job equivalent, it's common to list it under 'other experience.' Andy Lester, author of Land The Tech Job You Love, says: 'Think of each project as a freelance job that you've worked on. Just as different freelance gigs have varying sizes and scopes, so too does each project to which you contribute. The key is to not lump all your projects under one "open source work" heading.' Good examples are worth a thousand words. Grossbart offers up his resume as a sound but not perfect example (PDF) that includes open source experience. (His article on how to format your resume might also be of interest.)"
> Did you lead meetings?
What are these "meetings" you speak of?
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
Big problem is that the resume is filtered by data mining software and HR types. Anything outside of standard keywords and job description might not make the cut to an interview. At interview is where you show them what you have done unless they have a specific style of Q&A.
Aside for the formatting of skill lists and stuff, its pretty good, which means one thing, in my opinion: he is another victim of the "YOUR RESUME MUST BE ONE PAGE REGARDLESS OF YOUR EXPERIENCE!!!!!111!" school of thought.
The one page resume rule: hurting professionals everywhere since....well, ever.
I hope you never accidentally open a book, you might go blind.
Make a portfolio of open source work you've done. Go in and extract code that you've written. Annotate it explaining what problem you were solving and why you chose the design you did, etc. Keep each section fairly short (a few hundred lines of code) and write an overall document linking up the various code excerpts, creating a narrative for them to follow. If you have planning/design documentation, etc feel free to show excerpts of that too. Even emails from mailing lists where you defused a potentially difficult situation is good. Finally, provide links to all the original projects that you've contributed to so they can see your contribution first hand.
After you have organized all that, put it up on a web page somewhere and put a link on your resume. Burn a few business card sized CDs and hand them out at interviews. Make sure to bring a few to each interview. I've found they are popular.
This has gotten me more than one job. I used to maintain my portfolio continuously on my web page, but I'm teaching now and have let it lapse. However, it's sometimes useful even outside the job searching venue.
1. only list relevant experience, if your applying for a DBA position i don't want to waste time reading about how you enjoy cake decorating.
2. put the good stuff first, i need to skim 100's of these resumes so having to read till page 10 isn't helping your chances that'll see your skills.
3. keep the format clean and easy to read, don't make my eye's bleed because your going in the bin after page one with pink curly fonts.
If you mod me down, I will become more powerful than you can imagine....