Slashdot Mirror


Open Source Helps New IT Grads Get Foot in the Door

Yes, some US IT jobs are disappearing, but Linux.com (which shares a corporate overlord with Slashdot) has a recent story emphasizing the job advantage that involvement in open source projects can give young programmers who aren't planning to ditch their dreams of making a living in the field. The article focuses on one programmer's experience with Google's Summer of Code, which led directly to her job working on the Drupal content-management system. But the underlying message (that involvement in open source projects provides a background of experience otherwise difficult to obtain because of the chicken-and-egg problem of "experience required" job opportunities) is generalizable to many other forms of open-source involvement. Do you have a job that you landed because of your unpaid open-source programming?

41 of 128 comments (clear)

  1. But how does it help non programmers and PHB who s by Joe+The+Dragon · · Score: 3, Interesting

    But how does it help non programmers and PHB who say they want job experience in a office not side / school work?

  2. Sounds like... by Shados · · Score: 5, Interesting

    Sounds like its not so much open source involvement, but generally ANY involvement with your field, helps. And thats true for any job, any field, anything. In IT, you could simply do unpaid internships and get similar results. Its just a bit easier to get involved in open source, because you can jump in a project just by writing patches and open they get accepted, and go from there...

    But really, any field. Doing some volunteer work has always helped landing a job, its nothing new.

    1. Re:Sounds like... by Narpak · · Score: 4, Interesting

      I guess the sum of the matter is that some of the open source principles makes it easier for students to access and participate in ongoing projects. Thus they can develop skills hard to come by otherwise. Only natural that this would give them an advantage when looking for steady work later on.

    2. Re:Sounds like... by justhatched · · Score: 2, Informative

      I have not only employed developers based on their involvement in FOSS projects, but actually use it to cull the list of prospects - ie no visibilty in a FOSS project, application goes in the bin. The ease of getting involved has no bearing on what it takes to deliver valuable code. There are a few others doing this in Australia, and although it may be limited I believe it is a growing trend. The reason is not the demonstration of touchy-feely tree-hugging volunteering by the applicants, but that the best developers do not switch off at 5PM, and they are always looking for new ways to excercise their skills and increase their knowledge. The fruits of their journeys are also visible for like minded or simply pragmatic business people to leverage against competitors. Competitors that do not get that employing average gets you average results.

  3. Newsflash! by consonant · · Score: 5, Funny
    Prior related experience works in your favour when applying for jobs in a particular stream!

    Details at 11!

    1. Re:Newsflash! by moteyalpha · · Score: 4, Funny

      I agree, I have been telling the women who want to be prostitutes in Vegas for a long time that I operate an open source prostitution business and they need to get experience if they want to be successful. I think that work in open source is an end in itself. I find that people who work in open source tend to be talented in many areas of technology. The open source is just a way to apply the knowledge in the broadest possible way.

  4. Doesn't work for me by 4D6963 · · Score: 4, Insightful

    I've been working on my open source project for three years and that doesn't help me a bit when looking for a job in Dublin (Ireland, not Ohio). Basically there's a very few jobs out there in which you can program in C or anything vaguely signal processing-related and they all want you to have at least three years of commercial experience, don't care if you've got the snazziest open source project out there.

    And I've been looking for a job for over 5 months now, and mainly in tech support and system administration because really, no one wants to hire me for a coding job.

    --
    You just got troll'd!
    1. Re:Doesn't work for me by angusthefuzz · · Score: 5, Funny

      Maybe you should get off your ARSS and try working for a different open source project?

    2. Re:Doesn't work for me by epiphani · · Score: 5, Insightful

      I've been working on my open source project for about ten years now, and it has played a major role in every single job that I've held.

      I got my present job through someone I worked on the project with. I've been there 4.5 years.

      I also got involved in a local unix users group by way of hearing about it from some friends of the open source project. The connections I made at that users group have gotten me the job I will be starting in one month.

      My open source project, however idle it has been for the last several years, has contributed significantly and directly to my career.

      And I've been looking for a job for over 5 months now, and mainly in tech support and system administration because really, no one wants to hire me for a coding job.

      Get used to it. Unless you want to crank out business rules written in Java, systems administration/engineering/architecture is the place to be, IMHO. In those teams you can actually do work in C, mess around inside the kernel, and actually make use of all your skills. "Programmers" these days actually seem pretty boring unless you're working for a tech company that has an exceptional software engineering department doing something interesting.

      --
      .
    3. Re:Doesn't work for me by 4D6963 · · Score: 2, Funny

      Maybe you should get off your ARSS and try working for a different open source project?

      *pa-da-pshhh!* ;-)

      --
      You just got troll'd!
    4. Re:Doesn't work for me by Lumpy · · Score: 4, Insightful

      Because you are doing it wrong, marketing yourself wrong.

      I trot out my OSS projects not as "I work on this free thing on the side" but as "I invented and designed product X, I am a volunteer lead developer for Project Y, and I saved project Z and single handed brought it from a failure to a viable product.

      You need to take marketing classes, you gotta market yourself and network hard with people in the field. Hell get an article published in Dr Dobbs or another programming rag and your value goes up even farther.

      You market yourself as a one trick pony. you gotta have a list of tricks to dazzle them.

      --
      Do not look at laser with remaining good eye.
    5. Re:Doesn't work for me by Splab · · Score: 2, Insightful

      So you have been working for 3 years on the project, but hasn't managed to get it into a first version yet? No wonder you can't get a job if you can't show ability to get stuff out the door.

      Also, ARSS? In the beginning you called it ARSE - Yes that might be tong in cheek and kind of fun, but for a company hiring it doesn't exactly signal maturity.

      Remember you are pointing them to this project saying "this is what I can do!" and when they go there you show them that you are a lazy guy who doesn't get his things done. It might not be who you are, but those are the signals, and they are what count.

    6. Re:Doesn't work for me by DrgnDancer · · Score: 4, Insightful

      I hate to say it, but that's a pretty arcane bit of coding you've done there. Having taken a sound processing class at university, I'd probably hire you on the spot if the damn thing works like you say it does. Purely on the "If he can figure out how to do this on his own, he'll probably figure out whatever I set him" theory. On the other hand, a lot of people are going to look at this like it's an impractical exercise outside of a few very specific applications.

      You might try volunteering some time on a larger project with a more understandable goal. This gives you a) practical experience working with a team (usually pretty important in development work), b) something that an average manager will understand when you show them what you did, and c) a potential reference from someone else in the team who is already in industry and thus has standing to recommend you.

      Your personal project has two thing working against it as useful "experience". First, few people are going to really understand what you did, or how difficult it was. Second, you're not actually getting what they would consider useful professional experience. "Real" projects are developed by teams, with schedules, check-ins and outs, a team leader that everyone else reports to, and some sort of hierarchical development plan. This is often more than half of what companies want to see when they ask for "experience". They assume people learned how to pound code into an IDE in in university, they want to see that you can fit into a dev team and do your part.

      --
      I don't need a million points of light, just two points of multi-mode fiber and a 10 Gig-E router.
    7. Re:Doesn't work for me by Shados · · Score: 3, Interesting

      Lumpy is correct, and that goes for everything, every job, open source, close source, non-software job, everything. All job market experts and professional resume writers will confirm it, too.

      When you write your resume (or talk during an interview), you don't say "I worked on XYZ". No one gives a flying duck about what you worked on, because there's at least 10000 people who worked on the same thing, no matter how niche. What people care (and not only dumb ass PHBs and HR), is your achievements. The net gain you provided, the "out of the ordinary" stuff that pushes you ahead of others.

      So that line : "and I saved project Z and single handed brought it from a failure to a viable product" is the most important one of the bunch, and thats a sure fire job lander.

    8. Re:Doesn't work for me by Brandybuck · · Score: 2, Insightful

      There is no ticket to a free job. If you can't sell yourself, it doesn't matter how great your experience is. But even if you're the greatest self-promoter in the world, you still have to bust your ass for that job. That's life.

      --
      Don't blame me, I didn't vote for either of them!
    9. Re:Doesn't work for me by Glonoinha · · Score: 2, Insightful

      You have the answer right there in black and white - and it's not the answer you thought it was ...

      I got my present job through someone ...
      The connections I made at that users group have gotten me the job ...

      Sitting at home haxoring F/OSS in your underware isn't going to help anyone's long term career.
      Interacting with other people, contributing to a common goal in a collaborative fashion where you establish yourself in the minds of influential people as someone that delivers quality work - THIS is what opens up long term career options and opportunities.

      As much as it has been forever - it's not what you know. It's who you know. So get out there and meet some people.

      --
      Glonoinha the MebiByte Slayer
    10. Re:Doesn't work for me by Splab · · Score: 2, Insightful

      Then don't use the acronym, name it! If the name is too long, then rename it to something shorter and easier to remember.

      And just because someone else hasn't released "full" version doesn't make it right. You are the one searching for a job, what count is peoples view of your project(s).

      And don't get jumpy about it, I work for an IT company and we do hire C/C++ programmers, and I am one of those sitting across the table. I checked out your site and my response is the same as if you would have applied where I work - granted you wouldn't have been told, but would just have ended up in the bottom of the pile.

      Also, you are getting criticism, it sucks, but you need to suck it in and learn from peoples input - a Google search would now turn up this thread (somewhere) when searching for your project; how you handle yourself here will also impact your future applications.

    11. Re:Doesn't work for me by 4D6963 · · Score: 2, Interesting

      Well thank you for your insight, I appreciate. I'm glad to know that there are people out there in charge of recruiting me who would dismiss my work based on the fact that its version number starts with a 0, like it's more important than what it actually does?

      No offense but I think I'll keep it like this, sounds like a good way to weed out people who need a clue ;-)

      --
      You just got troll'd!
  5. Worked for me by goofy183 · · Score: 4, Insightful

    I was working for my university as a student in the IT department and implementing an open-source portal. Ended up getting a job offer with a company that provided consulting for said project. Now that I'm four years into working with the project and on my second employer (voluntary change) having open-source project experience while in college and after opens a lot of doors. Beyond just the development experience if you become heavily involved in a project it can also speak volumes about your interpersonal and team skills.

  6. Unsure in Seattle by OpenSourced · · Score: 4, Funny

    Do you have a job that you landed because of you unpaid open-source programming?

    I lost my last job for using the dead compile times for working on my pet open source project. Then I found another job, so you can say I landed there because of my unpaid open-source programming. Does that count?

    --
    Rome taught me patience and assiduous application to detail. Virtues which temper the boldness of great, general views.
  7. My IT experience by skyggen · · Score: 4, Interesting

    I never went to school for computer science. I went to college for Philosophy. I had always been around computers since I was six. I started programming basic on the TI-99a at 7. Granted it following step by step out of books, but still the knack and want was there. It wasn't until 1998 when I was introduced to open source and linux that my career path really shifted. Within 2 years of working with Linux and open source software I had become quite sick administrating linux and as a by product decent enough to be trained on solaris. At which point I was hired by a contractor for our local school district as a helper monkey for systems administration. Since 2000 I have made incredible leaps and bounds, improving my skill sets to include networking, virtualization, clustering, and so much more. All the experience I gained was by reading man pages, how-tos, wikis and using the software in a dev environment. Now I manage all IT at a 20 million dollar a year company.

    1. Re:My IT experience by Raconteur · · Score: 2, Interesting

      IMO, the best developers I've met have been non-traditionally trained. I have degrees in English and Political Science, and none in IT-related fields. That was pre-law, and when all of my friends started turning into lawyers I got terrified and bailed out of law school in a big hurry. As you already know, those who have an affinity for this field experience an epiphany when they discover the joys of code development, and that doesn't always happen with those who choose the career path of IT for reasons other than, well, the love of the art form. That happened to me over twenty years ago and now I have a very comfortable life. I have held numerous fascinating jobs and after all this time, I still like what I do for a living, even though I don't have to do it any more.

  8. A little... by 19061969 · · Score: 2, Informative

    I got some small-level consultancy stuff through volunteer open source programming but nothing serious. Employers value non-volunteer experience far more than just about anything else (unless they are deliberately aiming to pick up new graduates). The consultancy helps a little in terms of experience, but except for the payment, none of it was particularly useful.

    --
    bang goes my karma... again...
  9. Working with Linux helped me get my first job by Jim+Hall · · Score: 4, Interesting

    I got my degree in Physics, but my career path after that was in IT. My first job (January, 1995) was working as a UNIX systems administrator at a small geographics company. What helped me land the job despite having a different educational background was first-hand "experience" with Linux (SLS and Slackware.) I was the first at my university to try Linux (1993) so I became a sort of go-to guy for Linux questions when the CompSci students started to install it, and the university IT staff put it up on a few systems to try it out. "Something break? Happened to me too once, let me help you fix it."

    When I graduated, and it was time to look for a job, a friend recommended me for the UNIX sysadmin job at her company. The fact that I'd had two years experience working with Linux, helping others to install it and get it working for them, really gave me a boost during the interview. I got the job.

    Yes, this could have turned out the same if I'd just been helping at the computer labs (which I didn't, but others might have.) I think what gave me the extra edge was spending so much time with it at home, so when the technical interview questions came up, I was able to answer them very well. Nothing beats spending that extra time on your own desktop system, when you'll eventually mess something up and have to learn stuff on your own to get it working again and know how not break it a second time. That kind of "experience" says a lot to a hiring manager.

  10. Worked for me by cduffy · · Score: 4, Interesting

    First "real" tech job I interviewed for had a job description focused around porting and packaging software -- two things I'd already been doing for fun (building RPMs for whatever the current Red Hat was at the time, and porting software to my university's Solaris and IRIX boxes); the CTO (well, it was less than a 20-person shop at the time) was floored by my level of relevant experience.

    I landed the interview in the first place through some folks I met helping out at the university LUG. So yes -- of course -- open source experience helps. That employer was an embedded Linux shop, and learning from some of the other folks they had on staff (a bunch of kernel developers, including two of Linus's lieutenants, a gdb maintainer, and a bunch of other really bright folks) is what I credit for getting my career off in the right direction; every job I've held since then has included some level of interaction with the open source community, and I've had a great deal of fun.

  11. Its all about networking and communication by mjhuot · · Score: 2, Insightful

    I work on the OpenNMS project and we have been participating in the GSoC. I have not been directly involved but I have seen some of the work done by our participants. It is interesting to watch them learn about how to interact and contribute to the project. Some of them had to learn some of the basics of the "work" environment like meetings, status reports, and meaningful commit messages, as well as how best to present their ideas. I watched one presentation by a student and it was better than most I have seen in my professional life. If this student was to ask me for a recommendation I would have no problem giving it based on the coding and communications skills he has demonstrated. I think that is where the real value.
    Going and starting your own open source project is one thing, but you need to show how you work with others. I think there is more value in working on an existing project, showing how well you can work with others within a team. Plus you have an opportunity of networking with other developers.
    For non-programmers, there are other ways to contribute to open source projects, through documentation, IRC, mailing lists, forum participation, and testing. Again you get a chance to interact and network with people. You never know when one of the people that you wrote documentation for or helped out on a mailing list might be your next boss or co-worker.

  12. I created a business with my open source work by mckyj57 · · Score: 4, Interesting

    I built a business with unpaid open source programming. I say unpaid, because even though I was working as a consultant, the paid hours were very few and far between. I worked thousand upon thousands of hours over a period of years building a software package that sustains me to this day, almost thirteen years later.

    At the time I did it though, there was a dearth of open source software. The space I chose, the electronic shopping cart, was wide open, and people were crying for anything that worked and was supported.

    That is the key -- support. Decent programming and software is a must, but it doesn't need to be knock-your-socks-off great. If you can demonstrate you will be reliably there, month after month, year after year, I believe you be able to do what I did.

    However, I don't think it has much to do with "50,000 IT jobs lost". What I described takes hard work and initiative, as does any substantive contribution to an open source software package. The people demonstrating that type of ability are not the ones who are marginalized.

  13. Re:But how does it help non programmers and PHB wh by Lumpy · · Score: 4, Insightful

    only if the office PHB is not a moron.

    If the PHB discounts your OSS work, you REALLY DO NOT want to work there.

    Consider it a "has a clue" flag in the database. If they dont like the OSS work, the OSS flag is not set and you should exclude that place from your dataset.

    --
    Do not look at laser with remaining good eye.
  14. That's besides the point by HalAtWork · · Score: 2, Insightful

    The point here is that it's easier in a field where open source software is used, because the barrier of entry for actual hands on experience is lowered significantly. You can just download it and submit patches and participate in the actual development from your own home, and nobody has to know anything about you, so there are even no prejudices working against you which you may often encounter in a job environment, even if it's just people scrutinizing your age or what you wear.

  15. What about Linus? by hemp · · Score: 3, Interesting

    Open Source didn't really help him land a job for what 9 years?

    --
    Skip ------ See the latest from http://www.anArchyFortWorth.com
  16. Experience by Brandybuck · · Score: 2, Insightful

    Some of you younglings may think experience is overrated, that your degree from a party university should give you a free entry into an immediately high paying job. But this is the real world. Degrees are a dime a dozen and most resumes are padded. You need to prove to us old fogeys not just that you can code, but that you can code well, know how to design, now how to work in teams, won't go on a three month drinking binge the first time you get a bug logged against your software.

    We want experience!

    That's what internships are for. But getting an internship is almost as difficult as getting a regular position. Open Source Software lets you create your own internship. It lets you put down real experience on your resume. Even if you have real world experience, a lot of your code won't be public. But your Open Source Software will be, and interviewers can see your actual code.

    --
    Don't blame me, I didn't vote for either of them!
  17. Re:But how does it help non programmers and PHB wh by kz45 · · Score: 3, Interesting

    "only if the office PHB is not a moron."

    Not really. I see lots of open source contribution as more likely to leak commercial code into open source projects.

    Also, with the FSF going after all of these companies in court over GPL violations, why would I want to take a risk on a programmer that might "accidentally" add GPLd code in our codebase and risk the entire company's IP.

  18. Why I'm skeptical about the career value by walterbyrd · · Score: 3, Interesting

    I happen to be a F/OSS advocate. But, I'm a little skeptical about the career value of volunteering your time for F/OSS projects. The problems, as I see it, are:

    1) Most employers want five years of recent, verifiable, full-time, professional experience. That would be an awful lot of time to volunteer.

    2) Offshore, and guest workers are still much cheaper. Maybe it's best for Americans to give up on software development, and let the offshore workers have it.

    3) Even if an American can manage to get a development job, salaries are going down the toilet, as the market becomes glutted.

    Both presidential candidates, and almost all of congress, are pushing for more guest workers. Bill Gates is petitioning for unlimited guest workers. Once the election is over, I think guest worker caps will be raised substantially, if not eliminated entirely.

    1. Re:Why I'm skeptical about the career value by webchickenator · · Score: 2, Interesting

      (Disclaimer: I'm the person in the interview who blabbed on and on about how awesome open source is as a career move. ;))

      This actually is far more an argument *for* working in an open source project than against.

      When people think about the idea of using open source as a career launching pad, they generally think of two things:

      1. It's volunteer, which means you're not being paid. Ha! Sucker.
      2. It's IT, which is a dead-end in the U.S. due to shifts in the larger global markets. DANGER DANGER! SWITCH MAJORS NOW!

      But that ignores entirely one of the biggest advantages of getting involved in an open source project with a large, thriving community such as Drupal: there are nearly limitless networking opportunities, and those can (and do) lead directly to careers.

      Most of my first paid gigs as an independent consultant were from people I helped in the forums who needed some more "hands-on" assistance with their websites. The more people I helped, the more my reputation grew, and the more "human" connections I made. These connections, and the work I was doing out in the larger open source community, led directly to full-time employment with a Drupal shop. And this all happened within a matter of a couple months, mind you, not years.

      Open source economies seem to exist independently of the larger global trends, from what I've experienced. It might very well be that if I tried to apply down the street at a local IT place, I'd be turned away. But within the Drupal community, at least, it certainly seems like we can't find people to fill positions fast enough. And with more and more companies depending on technologies like Linux, Subversion, Python, and Drupal, experience working directly on those tools with the very people who built them can only help your employment potential even at the local IT place, no?

  19. Comment removed by account_deleted · · Score: 3, Interesting

    Comment removed based on user account deletion

  20. Re:But how does it help non programmers and PHB wh by dvice_null · · Score: 2, Funny

    PHP: - Sorry, OSS work does not count, besides I have never heard of that project. Have you done any real work in your life?
    Linus: - ...

  21. Re:But how does it help non programmers and PHB wh by mikael_j · · Score: 2, Interesting

    Anyway, any place that looks at those certifications is likely to eat up anything you tell them anyway, because they usually don't know any better. A place where they ask you technical questions usually won't care where you learned the stuff, as long as you know your shit. I prefer the later type of setting myself.

    Well, it's not that these courses are useless, it's just that most of the stuff in them is stuff I knew how to do back in the late 90's (and which are apparently considered advanced UNIX skills these days, like building apache+mysql+php on your own instead of running Synaptic and clicking on Apache, MySQL and PHP followed by the "install selected packages" button). So I'm basically taking these courses so that potential employers will know I'm not lying about my skills.

    /Mikael

    --
    Greylisting is to SMTP as NAT is to IPv4
  22. Re:But how does it help non programmers and PHB wh by poolmeister · · Score: 3, Informative

    I'm a senior HP-UX & Linux sysadmin now purely thanks to free software such as GNU/Linux, BSD, HTTPD & MySQL which enabled me to start learning the concepts of Unix style OSs, databases and their benefits without having to shell out for expensive software packages and courses.
    These skills then easily transferable to the other Unix OSs such as HP-UX, AIX, Solaris etc. which you're unlikely to ever touch unless you're paid to do so.

    --
    CN=poolmeister.OU=lurkers.CN=slashdot
  23. If you use or develop open source... by zogger · · Score: 2, Insightful

    ..you are never "unpaid". Never. The immediate and primary currency -your pay- you receive at all times and in as large of amounts as you wish is other peoples code they freely share. You can take this huge amount that is out there and use it for any purpose you want, including engaging in this thing called "business" where you can get paid in another form of currency if you desire. If you want to know where computers and code are used so you can "get paid" in central bankers currency while working "a job", here is a handy reference to start your search from. The vast majority of the hundreds of thousands of listings in this reference manual all use computers and code in some fashion now-a-days, and most of them all will pay you in central bankers currency if you work a job with them. So you not only get paid, you get paid twice if you use open source. Kinda nifty.

  24. Open Source Projects by xquiky · · Score: 2, Insightful

    I know that the open source community has given a lot to me. I have been able to tackle some difficult coding tasks by being able to reference works already done by some different open source iniatives. I think the chicken-and-egg issue about the developers not having experience but needing it to get a job, is definitely something that if the developer could show they contributed meaningfully to an open source project would help there case trying to get a job. It looks good on the resume. I decided to try and give back to the open source community, and released one of my products as open source now. I am looking for anyone that wants to work on it, or just enjoy using it. http://sourceforge.net/projects/pop3wizardnet/ I hope it helps someone save a few hours of headaches, considering it has weeks of work in it.

  25. Re:What about PHB in HR as well the other HR peopl by MBGMorden · · Score: 2, Insightful

    Agreed. For my last promotion HR didn't consider me "qualified enough" even though my boss assured them that I was more than capable of taking on the increased responsibilities. In the end the job posting had to be retracted, and the job description/requirements rewritten in order to fit my paper credentials more closely.

    Now, this was for an existing employee (me) that was already known to the people who would do the final hiring. If you were some unknown applicant out of college however, you'd get tossed in the circular file and nobody would ever know any different.

    As to the "you don't want to work there" part stated by the GP - be real. The economy is on the way to tanking. People have bills to pay. If it's the difference between living on the street and a roof over my head I'd be willing to dig shit all day - programming for clueless people is one heck of a step up from that.

    --
    "People who think they know everything are very annoying to those of us who do."-Mark Twain