Slashdot Mirror


How To Get Hired As An Open Source Developer

An anonymous reader writes "Todd Cranston-Cuebas, tech recruiter for Ticketmaster, offers insider tips and tricks for landing an open-source job -- or for recruiting new talent to your IT staff." Make yourself googleable.

129 of 351 comments (clear)

  1. Its rather simple. by Anonymous Coward · · Score: 5, Funny

    Just put it "willing to work for free" in your resume!

    1. Re:Its rather simple. by Anonymous Coward · · Score: 5, Funny

      I'll work for free.. I just won't do what you want me to do. But that's okay, if you offer me some cash then we can talk.

    2. Re:Its rather simple. by gallir · · Score: 2

      Free as beer or free as freedom? They just look for people who will work "free as beer", so be nice.

      --
      sgis ddo ekil t'nod i
    3. Re:Its rather simple. by jsse · · Score: 2

      My nephew really did put 'expected salary: $0' in his resume. He was serious, in view of the high unemployment rate here and he doesn't want to stay home for nothing.

      The interviewer really asked him: "Would you consider getting more for this job?" - you dream to hear that in the interview do you? XD

    4. Re:Its rather simple. by Monkelectric · · Score: 2
      I've been offered jobs for no money. tomshardware.com offered me a "job" reviewing hardware for no pay.

      Me: What does the job pay?
      Them: Well we're small, so ... ... nothing.
      Me: Can I keep some of the hardware I review?
      Them: No, we want it.
      Me: Well I guess it would be still cool to see my name on the site, can you guys fedex me the hardware?
      Them: No, you have to pick it up.
      Me: Thats 150 miles each way, it was nice meetin ya! :D

      --

      Religion is a gateway psychosis. -- Dave Foley

  2. does this happen? by mschoolbus · · Score: 3, Interesting

    I thought the point of a company hiring you is so that they may make money off of you (i.e. What can you do for the company?).

    I understand there are some companies that can somehow make money off of you creating open source software for them, but does it really make sense to look for a job in which you create open-source software? I mean, isn't working about bringing in money at the end...?

    1. Re:does this happen? by blonde+rser · · Score: 2

      Remember the whole point of computers and software is a means to an end. The only reason there are companies that produce and sell software is other companies then use this software to generate wealth. The software itself is not wealth. (This may vary depending on your definition of wealth, which - despite the efforts of many - does not have a single definition.)

      The company that uses the software doesn't really care about who owns it cause it's not there business. Their business is generating wealth (or assisting others in generating wealth) so that they can skim their share.

      So then existence value comes into play. There are companies who, for a variety of reasons, will pay others not to do certain things to their land (ie not knocking down trees by a certain stretch of river). The paying company doesn't now own the land... nor do they want to. There is no value to them owning the land. All they own is the decision not to knock down those trees because those trees have an "existence value" to them. Well this can be extended to software as well. Since the company is not in the business of own or selling software they can get a way better deal in buying the decision that somebody develops it instead of buying the software.

    2. Re:does this happen? by civilizedINTENSITY · · Score: 3, Insightful

      "Remember the whole point of computers and software is a means to an end. The only reason there are companies that produce and sell software is other companies then use this software to generate wealth."

      Yeah but by far most corporate software produced is not for sell. It is for use. So for most cases the only reason companies produce software is because they percieve a need for that software to do something for them. Thus, in the majority of cases, GPLed software is a free jumpstart. Since distribution in a non-issue, there is no problem with the GPL.

    3. Re:does this happen? by sql*kitten · · Score: 3, Insightful

      Yeah but by far most corporate software produced is not for sell. It is for use. So for most cases the only reason companies produce software is because they percieve a need for that software to do something for them. Thus, in the majority of cases, GPLed software is a free jumpstart.

      Why would any company want to give a "free jumpstart" to its competitors?

      There might be a philosophical argument for Open Source, but I have yet (in almost 6 years of reading /.) to see a convincing economic argument.

    4. Re:does this happen? by civilizedINTENSITY · · Score: 2

      I assumed you were trolling and ignored your reply, but you've been modded up, so... at the expense of feeding a troll I respond: Yes, why would a company give a free jumpstart to its competitors? Strange that you would ask. Since most software is produced for internal use, how the hell would non-distributed software help a competitor who never sees it? So obviously you are building a "strawman" arguement to attack. Or you really don't understand. Developing from GPL-ed software for internal use would give their developers a jumpstart, and it would give their competitors as much of a jumpstart as the sourcecode for MS Windows has given its competitors. Both would be as visible.

  3. Hiring with or without a degree... my thoughts. by dagg · · Score: 5, Insightful
    "Companies looking for open source skill sets are very focused on the proven abilities of the engineer in the work environment. In other words, if you can do it, you are the right candidate. With proprietary systems, like Microsoft technologies, there's a tendency to look at things like certifications as a prerequisite for hires. In the open source world, there are very few certifications that matter."

    My experience is this:

    • People without degrees will willingly hire people without degrees.
    • People with degrees usually hire only people with degrees.
    --
    Sex - Find It
    1. Re:Hiring with or without a degree... my thoughts. by MattW · · Score: 5, Insightful

      That hasn't been my experience. My experience is that good managers who are knowledgable about the workforce will hire people without degrees. People who are poor managers and in over their heads are too afraid to hire non-degreed personnel because they feel it will reflect poorly on them. It's the HR equivalent of "no one ever got fired for buying Microsoft".

    2. Re:Hiring with or without a degree... my thoughts. by Telastyn · · Score: 3, Interesting

      In part this is because (in the US anyways) people are raised believing that you're sent to school to get the degree so you can get a good job so you can get the pretty and vapid girl so...

      And it's just a farce. People that have succeeded, or seen someone else succeed without the degree will realise (generally) before people that've gone through the schooling and the job, and have the pretty and vapid girl, and are oblivious.

    3. Re:Hiring with or without a degree... my thoughts. by El · · Score: 2
      People without degrees will willingly hire people without degrees.


      I've found just the opposite to be true. Oracle, headed by Larry Ellison, who never graduated, is obsessive about only hiring master's degrees from schools like MIT and Stanford. I beleive that Microsoft, headed by Mr. Bill who also never graduated, prefers degreed people as well. Of course, some of the brightest developers I've ever met never graduated.

      --

      "Freedom means freedom for everybody" -- Dick Cheney

    4. Re:Hiring with or without a degree... my thoughts. by arkanes · · Score: 3, Insightful

      I'm well educated, well trained, and competent. I also have no degree. I also have a good job. I must be that 1 on a hundred :/

    5. Re:Hiring with or without a degree... my thoughts. by Monkelectric · · Score: 4, Interesting
      You are the exception my friend. I'm not saying I like it this way, but the US has a *HORRIBLE* case of credentialism. You can't disprove social trends :)

      This was the best thing I could find on short notice, but heres a link showing median income by education in farfax county virginia.

      I'm not saying you can't prosper without a degree -- first rule of science is you can't prove a negative. However, your chances are *much* greater with a college degree. In US Society right now a degree is what you need just to be let on the playing field.

      --

      Religion is a gateway psychosis. -- Dave Foley

    6. Re:Hiring with or without a degree... my thoughts. by tshak · · Score: 2

      We run an 80% Microsoft tech department and not one of us has a certification. Although certifications are a legitimate way of showing that you have a certain set of knowledge, it does not show the intelligence of a person. The same goes for CS types. It takes an intelligent person to truely take advantage of a college degree or certification.

      Anyway, my point is that just because we run "proprietary systems" doesn't mean that we look for certifications of those systems.

      --

      There is no longer anything that can be done with computers that is nontrivial and clearly legal. -- Paul Phillips
    7. Re:Hiring with or without a degree... my thoughts. by tshak · · Score: 2

      The only time I've seen a good manager virtually require a degree (except for rare exception) is when the job requires a lot of math and CS theory (eg: biometric security in embedded systems with relatively slow hardware). This makes sense as this is more of a research position, and research is a very academic decipline, which IMHO requires a certain academic background. Although, we all know what kind of an academic background Einstien had.

      --

      There is no longer anything that can be done with computers that is nontrivial and clearly legal. -- Paul Phillips
    8. Re:Hiring with or without a degree... my thoughts. by outsider007 · · Score: 2

      Yes so you should just put a degree on your resume even if you don't have one because:

      * People without degrees won't check because they're too slack to care
      * People with degrees won't check because doubting you would require 'thinking outside the box'

      --
      If you mod me down the terrorists will have won
  4. Same as getting any job by BigGar' · · Score: 5, Insightful

    Have skills applicable to the job and a few others that might come in handy.

    Be flexabile on salary, understand that pay has come down in a lot of markets.

    Interview well when it gets to that point.

    Get lucky.

    How is any of this different than getting any job?

    --


    Shop smart, Shop S-Mart.
    1. Re:Same as getting any job by klevin · · Score: 2

      Well, there were the points about participating in relevent mailing-lists/forums in a meaningful way and on making your resume show up in search engines such as Google.

      I personally found the suggestions on search engines helpful.

  5. Lucky me :-) by Wizard+of+OS · · Score: 4, Informative

    I know, I know, I have been extremely lucky :). Exactly one year ago, I was asked to join the internet team of a public broadcaster in the Netherlands. Their sites are based on the Open Source CMS mmbase. Of course, my work doesn't consist of 100% open-source programming, a lot of projects are more based around implementing the CMS for sites then on extending it. Nevertheless, I have been able to write significant bugfixes / applications that have been or will be released under an Open Source license.

    Please don't hurt me now :)

    --

    --
    If code was hard to write, it should be hard to read
  6. No way by IamTheRealMike · · Score: 5, Interesting
    Wow, slashdot is really proving itself interesting tonight. I should get a subscription but student, no cash, blah de blah.

    This is almost psychic though. I was just talking to my flatmate (we both work for former ministry of defence research) whether it'd be possible to get a project code for my open source project and try and get a grant from the LinuxFund, the idea being that I could "bill" the Fund for my time working on the project. Often the fund gives out money and the projects don't really know what to do with it, I think the best use I can think of is to let me work on it fulltime.

    Of course, as Dan rightly pointed out, there are all sorts of ugly issues with that plan, noteably the overhead my company would charge, and the fact that they have a tendancy to eat IP for breakfast. Even though the project doesn't do anything that hasn't been done before, they might try to "own" the code, which wouldn't do any good at all.

    Still, I think I might talk to my boss about it tomorrow. I get paid jack all basically so I'd be able to make $1000 go a long way.....

  7. ResumeRank(tm)? by szquirrel · · Score: 5, Interesting

    From the article:

    We create an index of all incoming resumes and search on keywords. That's why it's important for job-seekers to repeat the major skills multiple times in their resume.

    WTF is this? It's bad enough having to compete for a job with people who flat-out lie. Now am I going to lose out just because some dickhead spammed more buzzwords around his resume?

    --
    Never approach a vast undertaking with a half-vast plan.
    1. Re:ResumeRank(tm)? by stefanlasiewski · · Score: 3, Interesting

      Agreed... I just finished what I thought was a kick-ass resume, where I explictly removed multiple occurances of the same word.

      Why? Because it looks bad to the human eye "Apache this" and "Apache that" and "Apache thisotherthat" "Java this" "Java that" "Java something else", when you could say "This that thisotherthat Apache" and "Java this and that".

      Now I need to go back and put those keywords back in multiple times... arg!

      --
      "Can of worms? The can is open... the worms are everywhere."
    2. Re:ResumeRank(tm)? by greechneb · · Score: 2
      could be worse, you could be competing with Bernard Shifman

      - He once sent our company mascot an email with his resume. Apparently he thought a mouse was in charge of human resources. Guess he thought we were disney.

    3. Re:ResumeRank(tm)? by Telastyn · · Score: 2

      Though this also might be a benefit (especially in better markets). If the company doesn't hire on decent people they're not going to succeed. They're not going to get good people keyword searching. And you don't *really* want to get hired on just so you can go job hunting again in a few months do you?

    4. Re:ResumeRank(tm)? by zephc · · Score: 3, Funny

      avoid resumes such as:

      Programming Experience:
      - 68020, 030 Assembler (37 years)
      - Java development (15 years)

      Internet:
      - Website development (20 years)

      MCSE Certified

      --
      "I would say that 99 per cent of what my father has written about his own life is false." - L. Ron Hubbard Jr.
    5. Re:ResumeRank(tm)? by stefanlasiewski · · Score: 3, Insightful

      There is already too much bullshit in the resume world... and his strategy is simply asking for more bullshit.

      While it may seem like the screening process is simplified with these screening tools, in reality he's passing up many qualified candidates for people who plugin repeat certain keywords over and over again, with bullshit acting as the glue to connect words together.

      --
      "Can of worms? The can is open... the worms are everywhere."
    6. Re:ResumeRank(tm)? by pclminion · · Score: 2
      WTF is this? It's bad enough having to compete for a job with people who flat-out lie. Now am I going to lose out just because some dickhead spammed more buzzwords around his resume?

      Dude, seriously... Don't sweat it. Why would you ever want to work at a company where recruitment and hiring is performed by a computer?

      In other words, if some stupid company hires Joe Blow because his resume contains six more occurrences of "PHP" than yours, do you really want to work there? Imagine what your new boss would be like...

    7. Re:ResumeRank(tm)? by szquirrel · · Score: 2, Interesting

      Trying to get the pool down to a manageable level, that sort of thing.

      Then let him filter on a spelling/grammar check. That ought to prune out at least 50% of the chaff.

      Or maybe he should hire more HR staff if he really wants to find the right fits for such high profile positions.

      --
      Never approach a vast undertaking with a half-vast plan.
    8. Re:ResumeRank(tm)? by Amazing+Quantum+Man · · Score: 2

      Why? You could then get in good with those people who want "5 years experience in {Office,Windows} XP"!

      --
      Fascism starts when the efficiency of the government becomes more important than the rights of the people.
    9. Re:ResumeRank(tm)? by shoppa · · Score: 2
      While it may seem like the screening process is simplified with these screening tools, in reality he's passing up many qualified candidates for people who plugin repeat certain keywords over and over again

      Actually, "PC support" implies repeating the same things (retry Windows, reboot Windows, reinstall Windows) over and over again. So maybe repetition in the resume is a good thing!

  8. Ticketbastard by timothy_m_smith · · Score: 5, Insightful

    I find it almost funny to hear Ticketmaster being associated with free software since they provide a service that adds almost no value and charges a boatload. Good thing they are saving so much money on software systems.

    1. Re:Ticketbastard by MrEd · · Score: 2
      Right on. The best part is that they charge you a 'convenience fee' for ordering online... while saving money on operators!


      What a deal, eh?

      --

      Wah!

    2. Re:Ticketbastard by RazzleFrog · · Score: 3, Insightful

      Please mod this up. Can people be so blind as to not see the value of his post? This is not about a company supporting the open source revolution. It is about a money grubbing, evil empire (that has made buying event tickets an absolute expensive nightmare) using freely available open source applications to save money and then hiring a full time open source employee so that they don't have to pay support fees to any of the companies/organizations creating the applications.

    3. Re:Ticketbastard by Saige · · Score: 2

      Even worse is that they can't even keep their services working well. I've lost 8th row tickets because of their "you must check out in 5 minutes" rule when their website wouldn't work well enough to let me purchase the tickets in that allotted 5 minutes. Or even worse, getting on for a presale right when it starts, and being told "there are no more tickets available" while talking to other people who were purchasing tickets throughout the time it wouldn't find any for me.

      In other words, why take the advice of this person? What reason is there to believe they're not trying to find another way to make money off of doing nothing, and doing it badly?

      --
      "You know your god is man-made when he hates all the same people you do."
    4. Re:Ticketbastard by chris_mahan · · Score: 2

      Which is why I don't go to concerts and therefore don't buy tickets.

      If people voted with their wallets instead of spewing filth upon the head of the filthy rich on geeky forums and then spending their hard-earned cash on tickets and convenience fees, they'd change their tune.

      Anyway: It's like saying the soup is salty and asking for seconds: mixed messages get you nowhere.

      --

      "Piter, too, is dead."

    5. Re:Ticketbastard by Soko · · Score: 5, Insightful

      Creators of apps like Microsoft?

      Welcome to capitalism, and (for good or ill) one of the roles of OSS. How many times have you heard "RedHat is cheaper than Windows, so businesses should use it!!!", or worse, said that yourself? Don't like it when the other edge of the OSS sword swings around and hits you, eh?

      Since when does the GPL say "No money grubbing, evil monopolists allowed to install and use this software to further thier cause."? Oh, that's right, it doesn't - only rules about re-distribution. Hopefully 2.0 of the GPL will stomp out all monopolies, hunh?

      Grow up.

      Like it or not, we get the good with the bad. As "evil" as TicketMonster is, they _are_ forwarding our cause in a way that businesses understand - namley that OSS makes good business sense. I'll take that over a tin-foil hat any day, bud.

      Hell, maybe our way "of goodness and light" will rub off on them by association, making for a kinder and gentler monopolist. You just never know...

      Soko

      --
      "Depression is merely anger without enthusiasm." - Anonymous
    6. Re:Ticketbastard by hacker · · Score: 2
      Welcome to capitalism, and (for good or ill) one of the roles of OSS. How many times have you heard "RedHat is cheaper than Windows, so businesses should use it!!!", or worse, said that yourself? Don't like it when the other edge of the OSS sword swings around and hits you, eh?

      I think you, like the rest of the media and masses who don't know enough about this environment, clearly missed the point..

      The point is NOT that it's free (as well as Free), or that they save money by using it... Go ahead, use it, save billions, that's the reason it exists, to improve the technology.

      The real point here is that they violate the SPIRIT of the license and community by NOT GIVING BACK to the community that helped them.

      Where are the fixes to the code they use?

      Where are the bug reports?

      What about patches?

      New features?

      Where's the "Thanks for saving us millions!" letters?

      Nothing. That's the point. We save thousands of companies billions of dollars a year, and we see less than 1/10th of a percent of fixes/bugs/patches back, and maybe one in 5,000 people actually care to say "Thanks". Now go back and re-read this book from the beginning, and stop skipping to the last page, you've clearly missed a lot.

  9. Google? by xchino · · Score: 3, Interesting

    What's the difference between sorting out 3,000 resumes and 3,000 irrelevant google links? Secondly, if someone is not actively seeking employment, then they are probably employed. Why not give the job to one of the thousands of highly qualified unemployed Open Source professionals? Seriously, it's like a geek can't get a break in this business ;)

    --
    Everyone is entitled to their own opinion. It's just that yours is stupid.
  10. Arg! You just 404'd my resume! by stefanlasiewski · · Score: 5, Funny

    Gee, thanks! I just submitted my resume for a job at one of the ticketmaster subsidiaries...

    My resume is now lost in a huge, even bigger then usual pile of resumes.

    404 - Career Not Found!

    --
    "Can of worms? The can is open... the worms are everywhere."
  11. Re:lol.. .. open source is hireable..? by foistboinder · · Score: 2

    I just spent 4 months working on CFD software that will be freely available

  12. pssst... by jki · · Score: 4, Insightful
    offers insider tips and tricks for landing an open-source job -- or for recruiting new talent to your IT staff

    Here's a free insider tip, here's another.. do something to get noticed. A CV with something concrete in it looks much better than one without.

  13. Ticketmaster, huh? by X_Caffeine · · Score: 5, Funny

    Does he have any tips on running the sort of monopoly that a company like Microsoft could actually take notes from?

    --
    // I will show you fear in a handful of jellybeans.
    1. Re:Ticketmaster, huh? by Jonny+Ringo · · Score: 3, Funny

      I know. But the title of this is not called "How To Get Hired As An Open Source Developer and Still Keep Your Ethics". :-)

  14. Sigh - #include by 4of12 · · Score: 5, Funny

    I guess it's probably just a reflex action against spam-like resume submission (he cites 3000 applicants for a PC support tech), but I have to cringe that resumes get pre-processed by machine.

    Soon applicants will achieve homogeneity in resumes, devoid of any real persona...

    • PHP, 5 years experience
    • MySQL 6 years experience, senior project lead, architect
    • Apache 3.0pre9, principal developer, 9 years experience
    • .NET original architectural team, 15 years experience
    • Java2EE, 23 years experience
    • Linux kernel developer, 497 years experience
    • MCSE since 1954
    • SANS certified since 213 B.C.
    • CCNE since Cheops finished the pyramid
    --
    "Provided by the management for your protection."
    1. Re:Sigh - #include by richieb · · Score: 2

      Yeah, but that's in dog years...

      --
      ...richie - It is a good day to code.
  15. As the job turns by satsuke · · Score: 2

    Imagine the deluge of resumes this recruiter is going to see .. solicited or not.

    My take on working full time in an open source role is ..

    Keep your skills current and relevent for the job market and interview as best you are able ..

    The fact that there might be a chance for open source evangelism or code contributions is secondary unless you are either independently wealthy or found some group that is.

    In this case, it's like my career. I was a Unix admin before the boom .. during and after. The tools change and improve but the basic requirements don't change.

    That is why you find people brought up on Dos or Linux having no particular problem getting around Windows .. no more so than going from Solaris to Red Hat Linux to Debian Linux .. the particulars are different but the skills required to understand what needs to be done do not vary very much.

    Which looks better on a resume

    Unix Administrator - 5 Years - Linux (several) Solaris, HPUX, AIX and others

    or

    Red Hat Linux Administrator - 5 years

  16. Get a headhunter by stratjakt · · Score: 2, Insightful

    They'll do all the work for you, and (usually) get paid by the hiring company for finding you.

    This article is good advise if you want to work as a support tech at ticketmaster, but in my experience, a good headhunter is the only way to go.

    --
    I don't need no instructions to know how to rock!!!!
    1. Re:Get a headhunter by geekoid · · Score: 2

      The "Employer pays" model of head hunting is something the boom created. Prior to that, the employee paid head-hunters.
      Expect the old model to return.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  17. My new resume by Waffle+Iron · · Score: 5, Funny
    This article has excellent advice for writing a resume in this age of Internet search engines. I've already rewritten mine. Here it is:

    Resume Resume Resume Resume Resume

    Java C Windows Windows Motivated C++ C SQL Teamwork C++ Perl C GDI C++ Perl Teamwork Windows Perl SQL SQL Motivated Windows GDI C++ Windows Self-Starter Perl C++ C C++ C++ GDI Motivated Self-Starter Python C++ Java Java C++ Python C++

    Motivated Teamwork Python Motivated C++ Perl Motivated Perl C Java Self-Starter Windows GDI Self-Starter Java GDI Motivated C++ Windows Windows Windows Teamwork Self-Starter GDI Self-Starter C C Windows SQL Windows Python Python GDI Motivated GDI Perl Teamwork SQL Perl Self-Starter Java Python GDI Teamwork Teamwork Motivated Java SQL Windows Perl Teamwork SQL C++

    Self-Starter C++ GDI Java Python Windows Perl C++ GDI Windows Teamwork C GDI Python Perl C++ Perl C C++ Self-Starter Teamwork Motivated Python Java Teamwork Java Motivated Motivated Teamwork Motivated Python Self-Starter Java Python C++ SQL Python Teamwork Python Self-Starter Java Teamwork Teamwork C++ C++ Self-Starter Motivated GDI Motivated Windows Motivated GDI C++ GDI Windows Python Perl C Python Teamwork Python Self-Starter Windows Motivated SQL C++ GDI GDI SQL SQL C Self-Starter C++ Java GDI SQL GDI Self-Starter C Teamwork Motivated Motivated SQL SQL Self-Starter

    Self-Starter Motivated C Teamwork Motivated Teamwork SQL Windows Java Windows C Windows SQL C++ Teamwork Python GDI Java C++ Python GDI

    1. Re:My new resume by RealAlaskan · · Score: 2
      Resume Resume Resume Resume Resume

      Java C Windows Windows Motivated C++ C SQL Teamwork C++ Perl C GDI C++ Perl Teamwork Windows Perl SQL SQL Motivated Windows GDI C++ Windows Self-Starter Perl C++ C C++ C++ GDI Motivated Self-Starter Python C++ Java Java C++ Python C++ ...

      You SWINE!! You copied my resume! You may expect to hear from my liars!
    2. Re:My new resume by Havokmon · · Score: 2
      Now the trick is to get this version to HR, but a real resume to the hiring manager. Some kind of magic ink that changes after HR reads it? Now where did I put my "McGivor's Guide to Resume Writing" book?

      Try a VERY SMALL white font. :P

      --
      "I can't give you a brain, so I'll give you a diploma" - The Great Oz (blatently stolen sig)
  18. Just the other way around by Wee · · Score: 2
    People without degrees will willingly hire people without degrees.

    This has not been my experience. I've worked in a tech field for 4 employers in two states since 1994. I have no advanced degree (I was 12 units away from a BS in Geosciences when I recruited away from school to California, FWIW) yet I've worked continuously for the last 8 1/2 years. I was only hired once based solely on my resume. All other times, I had some working relationship and/or professional reputation with those who hired me (ie, they knew -- or knew someone who could vouch for -- what I could do). The one time I was hired based on my resume was by a person without a technical degree.

    It comes down to knowing people or being in the right place at the right time, in my experience. You have to know people and they have to know what you can do. Your working life should be thought of as one long probationary period from which future employers can draw by taking a peer's word that you are a good employee. You should also be able to find out a lot about an employer through similar methods. Either that, or you have to look really good on paper and somehow stand out from the crowd.

    The best employment experiences I've had were ones where I knew them and they knew me (at least second-hand).

    -B

    --

    Ash and Hickory, straight-grained and true, make excellent bludgeons, dandy for the cudgeling of vegetarians.

  19. Insider tips and tricks, condensed version by kwertii · · Score: 3, Funny
    • List buzzwords often in your resume.
    • Put your resume online.
    • Already know someone who is hiring.
    • If this is not possible, already know someone who can refer you to someone who is hiring.
    1. Re:Insider tips and tricks, condensed version by /dev/trash · · Score: 2
      # Already know someone who is hiring.
      # If this is not possible, already know someone who can refer you to someone who is hiring.

      Any picks for the 2003 Super Bowl?

  20. Move towards becoming self-employed and contract by NZheretic · · Score: 4, Interesting
    If your planning on spending most of your time actually developing or deploying rather than administrating open source systems, then do yourself and open source in general a favor and consider becoming a self-employed contractor.

    As a contractor, it is easier to avoid getting locked into internal (and infernal) NDAs development agreements, the bane of my current position.

    The concept of open source and development is finally gaining ground and it's a lot easier these days to sell your development services, based on open sourced and free licensed software, to other interested parties.

    Individual jobs come and go, but GPL and LGPL licensed source is forever.

  21. Open Source a Fantastic "Interview" by Adam+Fisk · · Score: 4, Insightful

    We see this issue from a slightly different angle -- open source coders for LimeWire offer us an extended "interview" period where we can truly judge the value of their code. This lets us make hiring decisions easily. There's no interview that can substitute for months of open source code. Interestingly, we've seen that one of the primary attributes of people who write good code is also one of the primary attributes that involves them in open source to begin with -- passion for the project. The best coders often don't have the most impressive degrees. Rather, the best coders are the ones who care enough about the project to write good code for it. Experience and training help, but it's passion for the project that makes average code good, or good code great.

    --

    Adam Fisk

    1. Re:Open Source a Fantastic "Interview" by geekoid · · Score: 2

      I hope you have checked with your State to see what qualifies as an employee, or you may find yourself on the loosing end of a lawsuit.

      Actual, check with the IRS. They list 20 thing that indicate someone is an employee, regardless of anything the sign. That applie to courts as well.

      Rul of thumb, if the person doing the work could answer yes to 7 out of the 20 question, there an employee.

      Again, the courts and the IRS don't care about what the person has signed when determining status. this will get you into a lot of trouble if you using 1099.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    2. Re:Open Source a Fantastic "Interview" by shoppa · · Score: 2
      There can be some difficulty in determining, in a multi-person open source project, who the author/designer really is. And who did the coding (good and bad).

      This isn't unique to open-source code, of course. For every big succesful commercial project there are plenty of people willing to take credit for the whole thing, too.

    3. Re:Open Source a Fantastic "Interview" by Adam+Fisk · · Score: 2

      That's an interesting point regarding liability in general, and about the IRS. In terms of suite regarding any copyright issues in particular, however, it's unlikely that employees of companies would be held personally liable in any way. The assets of company officers could potentially be fair game in a suit, but even that is unlikely and not really what the plaintiffs would be after (except perhaps as a scare tactic). Given that open source coders could never be considered officers, there's really no legal threat in terms of personal assets.

      As far as the IRS goes, any open source programmers that get paid are required to file their earnings, just as any freelance employee would be. If they're not getting paid, it's off course not an issue.

      --

      Adam Fisk

    4. Re:Open Source a Fantastic "Interview" by Adam+Fisk · · Score: 2

      In any project that is centrally controlled, where a set of individuals keeps close track of any new code (and where limited numbers of people are able to add code directly without submitting patches), it's quite easy to know precisely who did what. This is the case with LimeWire just as it's the case with Linux (our job is orders of magnitude smaller and easier, of course).

      That issue aside, however, even if you only know that a specific person wrote a specific piece of code that you liked (whether or not you know exactly who wrote every line in the program), that person has a much better chance of getting hired if and when a position opens up.

      --

      Adam Fisk

  22. Re:Business Plan by EccentricAnomaly · · Score: 3, Funny

    And be sure to link /. as a favorite technical website on you resume:

    Another thing is to include your favorite technical Web site list in your online resume or personal Web site. I'll look for people who specialize in a certain area -- if they also have a list of favorite Web sites that show their interest in the top Web sites in a certain area, I'll notice that.

    But then again, telling a potential employer that you read a lot of slashdot might not be a good thing :)

    --
    There are 10 types of people in this world, those who can count in binary and those who can't.
  23. FOR GREAT GLORY~!!!! by EnderWiggnz · · Score: 3, Funny

    all your base belong to a beowulf cluster of natalie portman's with hotgrits down their pants

    3) PROFIT!!!

    --
    ... hi bingo ...
  24. How I got my last job by Binarybrain · · Score: 3, Funny

    Sometime during the last few days at my last job I happened to ask my employer why he hired me. The reason was rather caught me by suprise.

    Because I hated Microsoft. Im not kidding. He figured that if I was smart enough to dislike Microsoft that I probably knew what I was talking about.

    1. Re:How I got my last job by The+Bungi · · Score: 3, Funny

      What did you do? Mop the floors?

    2. Re:How I got my last job by Binarybrain · · Score: 2, Informative

      I developed a content management system.

    3. Re:How I got my last job by sql*kitten · · Score: 2, Funny

      I developed a content management system.

      Emptied the bins, then?

  25. Crappy hiring techniques by Anonymous Coward · · Score: 2, Interesting

    Another reason is that some recruiters use applicant tracking programs that do automatic skills assessment based on keywords found in the resume, and will rank resumes based on that assessment.

    Having seen my fair share of resumes padded with every acronym under the sun, I have to say this is a pretty crappy way to do recruiting.

    There's a reason why people get hired based on "who they know"... it can be an effective filter.

    Looking for a job? Get to know people!

  26. DONT CLICK ON LINK IN ABOVE POST!!!! by kingkade · · Score: 2

    a word of warning, for anyone who thought this ass-clown might have something funny to say: he doesn't he's just another angry loner with not one original thought in his tiny brain. just a sheep, your bus is leaving, you fuckstick.

    1. Re:DONT CLICK ON LINK IN ABOVE POST!!!! by kingkade · · Score: 2

      Actually I didn't click on the link Anonymous Coward.

      See dimwit, I have something called a memory, which is a feature of something called a mind which in turn is a manefestation of an organ called a brain. This unique device actually helps me recall experiences I've had before and learn from them.

      Am I going too fast for you, little troll?

      As for your poorly-formed inquiry: here you go, fuckstick. Also, you're one of these as well.

      Oh and read a book, fuckwit.

  27. Now hiring OS Developers! by NineNine · · Score: 4, Funny

    Payment:

    I'll buy beer for you and won't tell your parents.

    You get to look at my personal collection of nudie magazines.

    You can code at my office, and tell your parents that you're at a sleepover. I'm an adult. They'll believe me.

    I can pick you up from school, posing as your parents.

    I have a PS2 and Grand Theft Auto: Vice City!

    You can have all of the soda and candy you want.

    Please send resume and/or high score list.

  28. It's not that simple by dcavanaugh · · Score: 4, Insightful

    As a manager with no degree, I am in a position to comment.

    I give careful consideration to all applicants, but I take a sceptical view of those people whose only claim to fame is a degree or certification. I want experience, or concrete evidence that the candidate is prepared to do the job with minimal babysitting. Another thing I want is some longevity. If I'm hiring for a full-time position, I view it as a purchase as opposed to a rental. You would be amazed to see how many people have years of experience, but never more than 12 months at any one place. What assurances do I have that such people are not simply hopping from one contract to the next, leaving behind a trail of destruction?

    My hires have ranged from a high school dropout [long story omitted], to an MSCS. I'm quite proud of my people; all except one have worked out well. I don't actively seek to avoid hiring people with degrees, I'm just not convinced that the credential means much. This means I'm tough on recent grads, but who isn't? For the record, I hired a recent grad after he spent some time in my department as a temp -- another success story.

    I believe that managers will repeat any behavior that works, and abandon that which does not work. After you get burned on a few bad hires, you will seek to avoid whatever led you down that path.

    1. Re:It's not that simple by Matthew+Weigel · · Score: 2

      dcavanaugh wrote:

      Another thing I want is some longevity. If I'm hiring for a full-time position, I view it as a purchase as opposed to a rental.

      Hmmm. I assume longevity, then, is something you as a manager can offer your employees, too? Can they feel confident that there won't be layoffs, that the company won't collapse, that there won't be huge accounting scandals that ruin their retirement?

      What assurances do I have that such people are not simply hopping from one contract to the next, leaving behind a trail of destruction?

      I dunno. Why not ask the applicant? Maybe former employers too. Maybe you can find out whether they did well in those jobs.

      Maybe he's hopping from contract to contract, leaving a trail of happy employers- maybe he's worked for a lot of high-risk companies that went under or had to lay him off, and he's looking for something now that's a bit more stable (if you purport to offer it).

      I don't think your metric has much value, but I'll be honest- with a big stack of resumes, some winnowing technique must be used. It's hard to argue with one that's worked, and isn't outright unethical.

      --
      --Matthew
    2. Re:It's not that simple by susano_otter · · Score: 2
      You would be amazed to see how many people have years of experience, but never more than 12 months at any one place. What assurances do I have that such people are not simply hopping from one contract to the next, leaving behind a trail of destruction?

      No, I wouldn't be amazed at all. It's a bit naive to think that sort of work history has been anything but typical in some sectors--for years, now. If you want assurances, interview them hard, and check their references. Meanwhile, how about giving us some assurances that you're committed to long-term loyalty to your employees, and won't lay us off next Christmas to appease your new CEO, who's making arbitrary budget cuts to line his own pockets.

      --

      Any sufficiently well-organized community is indistinguishable from Government.

    3. Re:It's not that simple by hendridm · · Score: 2

      > I take a sceptical view of those people whose only claim to fame is a degree or certification.

      So I guess the rest of us who graduated from college and can't get experience because nobody will hire us are fucked then.

      If I wasn't supposed to go to college, what do you suggest I SHOULD have done after high school? College certainly hasn't paid off.

    4. Re:It's not that simple by dcavanaugh · · Score: 3

      "I beleive claming to fame 'a dregree' is better than 'I have no degree, but it's not that usefull and I am good'"

      It depends on how many examples you have that support the "I am good" assertion, especially if those examples are logically presented with proper spelling and grammar.

    5. Re:It's not that simple by SuiteSisterMary · · Score: 2
      If I wasn't supposed to go to college, what do you suggest I SHOULD have done after high school? College certainly hasn't paid off.

      You were supposed to go to college, but in a field that isn't so drastically oversaturated as tech is now a days. That way, you wouldn't be competing for entry level positions against people who already have 10+ years of experience.

      Sad, but true.

      --
      Vintage computer games and RPG books available. Email me if you're interested.
    6. Re:It's not that simple by Matthew+Weigel · · Score: 2

      mindstrm wrote:

      You seem to be saying that as employers don't offer you a guaranteed job, you don't offer them guaranteed service.

      Only partially.

      Absolutely.. however.. will you work for an employer who has a record of laying off his workers every 12 months or so?

      No. But I think the parallel between "laid off workers" and "stopped working there" is a bad one. After all, he didn't say "quit their job every 12 months". What about a company that's extremely upwardly mobile, with people not holding the same positions for long? (that's quite a bit different from annual layoffs) What about an employee who went from contractor to employee for a vendor to employee for a customer?

      If the work is obvious contract work, that's not what he is talking about

      Excuse me if I take his words at face value, and ignore your attempts to interpret it. He made a pretty clear statement that didn't provide for "if it was contract work."

      he's talking about people (and I'm sure we all know people like this) who work for a job for around a year, and then look for the bigger, better deal.

      No, he's not, because that can't be measured with the metric he mentioned. Maybe that's what he's trying to winnow out, but that's not all he's cutting out.

      Why did you leave your last job? You will be asked this in an interview. If your main reasons seem to be "more money" then it's obvious that as soon as someone comes along offering a bit more cash, you will flee.

      Not necessarily. As an example, I left my last job because as much as I loved it, they weren't prepared to offer me enough to support both me and my fiance moving into town. When I get a kid, I probably won't be comfortable working where I am now, much as I love it. Then, and in the future, I will be leaving for "more money," but I'm not a fly-by-night programmer looking for my next buck. In fact, I pick jobs (and work environments) well enough that I expect my main reason for leaving, over time, will be either "they went under" (won't happen at Carnegie Mellon), or "I needed more money."

      My point being, it's a complicated issue that requires consideration of a number of factors and information coming from a number of sources (former employers, the prospective employee, references...). However, a recruiter sees enough applications that they can't give all this information due consideration for every applicant- they have to have simple, moderately effective, metrics for throwing out 90% of the resumes with very little thought.

      So while I'm arguing that this fella's metric isn't perfect, I'd probably do something similar.

      --
      --Matthew
    7. Re:It's not that simple by dcavanaugh · · Score: 2

      "Meanwhile, how about giving us some assurances that you're committed to long-term loyalty to your employees"

      I believe it's the classic risk/reward equation. During the Dot-Com era, the highest salaries went to those who abandoned their relatively stable jobs to go off and join startups. The companies that "went public" spewed forth plenty of money for salaries, bonuses, and stock options. Those that failed to go public are pretty much gone by now. Hell, they're ALL pretty much gone by now!

      I work for a company that has nothing to do with IT, but we use IT to help provide services. Do I make as much as I could have with a dot-com? No. Do I make as much as I should, based on salary surveys and other data? Nope. Do I pay my staff as much as they are worth? No; I'm very lucky to have them On the other hand, we survived the Dot-Bomb era, no problem. The company has been around for almost 60 years, so they won't be disappearing anytime soon. Even when some divisions had problems and layoffs, corporate IT was unscathed. I believe it worked this way because I kept the department small when I could easily justify 2X as many positions as I have. This means a substantial backlog of projects, but it also means the knife of corporate austerity does its damage elsewhere.

      Nobody is going to get rich working in my department, but I think I do a world-class job of defending my people. What I fail to understand is how so many people thought it was possible to earn big money without big risk.

    8. Re:It's not that simple by dcavanaugh · · Score: 5, Interesting

      I was in college back in the early 80s. At the time, new grads were having a hell of a time landing jobs. I was really worried about graduating and finding nothing to do. By the mid 80's, things warmed up just a little. I was looking for a part-time job that would provide meaningful experience, because it looked like experience was the only way to get a "real" job later.

      I applied for what I thought was a temporary, part-time, third shift operations job in a data center that ran a bunch of DEC VAX machines. The job they offered me was first shift, and 91% of full-time (state employee benefits included). I was a junior in college, who accidently landed a job that was no worse than what a new grad would get. I decided to take a break from school and go back when the job ended. Well, the job that wasn't third-shift or part-time wasn't temporary either. The original employee on leave never came back, so I became an accidental full-time permanent employee. I never went back to school, because I stayed 13 years, with five promotions, ending as the Director of Technical Services.

      If I had stayed in school, I would have finished in 86 or 87, and the job market was really hopping by then (but who knew back in 85?) I was so happy to have found a job, I thought it would be stupid to finish school if that meant graduating into a down market. Having seen how many employers "required" degrees but "hired" experience, I determined that experience would win out over degrees most of the time, or at least often enough to keep me working. My cynical view of employment has served me well. After 17 years of uninterrupted employment, I'm having a hard time seeing the downside of quitting college early.

      So, why do I post this mini-autobiography? To illustrate just how cyclical the IT has always been. When it's hot, anyone who can type can get a job. When it's cold, having a Ph.D. won't help. So, I think the strategy is to build credentials and manufacture your own experience in the "cold" years, as you wait for the "hot" years. If you live in a high-cost area, consider moving someplace cheap. There is no reason to tolerate a high cost of living unless you have a big paycheck to cover it. Go back for an MSCS or MBA degree if you can; work outside IT if you must. Either way, start your own little empire of computers, using open source (Linux) or free downloads from Oracle (free for non-commercial use, including home hacking). If you can pick up contract work of any type, then you'll be in a position to do something when the market heats up again. Timing is everything.

      The fact that we have a down market combined with a glut of H1Bs makes me wonder if we are going to see a massive correction when the market heats up. I predict a shortage of IT people, because it makes no sense to invest 4 years of tuition just to compete with H1Bs. Then again, my prediction plus $1.10 gets you a medium coffee at Dunkin Donuts.

    9. Re:It's not that simple by Safety+Cap · · Score: 2
      The company has been around for almost 60 years, so they won't be disappearing anytime soon.
      Tell that to the (ex-)employees of Arthur Andersen.
      --
      Yeah, right.
    10. Re:It's not that simple by dcavanaugh · · Score: 2

      Considering how all the big accounting firms are motivated to lie, it was only a matter of time before one of them got caught. I'm not claiming that any of them lie, but the motivation is surely there. People who pay for accounting & consulting services are not always interested in the truth.

      In my line of business, lying would not help, not even short-term. Had I gone to work for Arthur Andersen, I'm sure they would have paid more than I make now. However, it would have meant sitting a little further out on the risk/reward curve. Working in a conservative industry means I can spend my free time on Slashdot instead of Monster, Careerbuilder, & Dice.

    11. Re:It's not that simple by dcavanaugh · · Score: 3, Insightful
      "...I tend to find the people who have moved around a lot are much more flexible..."

      That is certainly one of the possibilities. There is something to be said for a person with 5 years at 5 different employers -- a richer experience.

      When a contractor is really good, the employer is often motivated to make an attractive full-time offer. When I see a person whose career consists of 10 six-month assignments over 5 years, I have to wonder:
      • Why didn't any of these 10 employers want this person for more than six months?
      • Did this person rely on the short-term nature of these assignments to avoid following any of these projects through the entire development cycle?
      • Could they actually maintain these projects or have they been sliding along?
      When you make a good hire, you worry about how long you can retain the person. When you make a bad hire, retention is no problem; mediocrity lasts forever. If I want a good person and I want to keep them for at least a few years, the many-job candidate is not my first choice. Unless the interview process turns up something important, I can't expect them to stay any longer than their track record would indicate. A competent person who stays 5 years is more valuble than a superstar who is gone after 1.

      If I want a temp, I'll hire one. For projects of a temporary nature, the job-hopping issue is no problem. Either the person works well and I offer a full-time deal, or they're gone at the end of the contract.
    12. Re:It's not that simple by susano_otter · · Score: 2

      Fair enough. All of my job-hopping was a result of walking into a very volatile job market at an entry level. At first I figured I'd start out as a temp, then earn a permanent position. After a while it became clear that most of the IT departments in my area had a very different idea about temps: they're cheaper than full-time employees, and if you purge them every six months, you never have to worry about the headhunter's fee for making them perm. Then there was the company that hired me perm, and within a year they'd cut their staff from forty down to ten, and moved from San Jose, CA, to Spokane, WA. After that was the perm job where I got laid off in one of the many layoff waves that plagued every company in our sector. They just kept reducing staff, and replacing expensive, experienced techs with cheap, entry-level monkeys.

      My worst nightmare during this period was walking into an interview with a manager who didn't "get it" and would dismiss me out of hand for my job-hopping, rather than actually interviewing me and getting some idea of my actual skills, attitudes, and desires (namely, for a stable, long-term job where I'd actually have time to make meaningful contributions to the company).

      --

      Any sufficiently well-organized community is indistinguishable from Government.

  29. How I did it by mikosullivan · · Score: 4, Interesting
    Without planning it or expecting it to happen, I got a new job developing open source software last month.

    My wife Starflower and I have been volunteering for the Rescue Mission of Roanoke, a Christian organization that provides meals, shelter, and other needed services to the homeless in the Roanoke area. It's a great place and Starflower and I are very proud to help out there.

    One evening I was having dinner with Joy, the director of the mission, and she mentioned that her computer had crashed a dozen times that day. Out of habit I said that that sort of thing doesn't happen in Linux. She got very interested and said that I was the fourth person to say that, so tell her more about this Linux thing. Well, I gave her the standard pitch, talking about the value and quality of open source in general and Linux in particular. I told her about LTSP and how the mission could make life a lot easier with a set of thin clients and one good server. I talked about how great and helpful the open source community is. I even mentioned that Larry Wall (I'm doing the database project in Perl) is an evangelical Christian. Joy was very interested in all of this.

    The following week, I presented a requirements document for a new database system using Apache, PostGres and Perl. I call the system Joyis, and you're welcome to read through the document yourself.

    My intention was to develop the system on a volunteer basius. The management team had a better idea: they offered me a full time job on the spot. I accepted on the spot. I'll be developing Joyis for the next couple months, then migrating the entire mission to a completely open source infrastructure: Linux, LTSP, OpenOffice.org, Evolutions, and of course, Joyis.

    The pay ain't much, but we can get by on it. On the plus side, I get to spend all my time in my favorite development environments, working my own hours, and creating a system that will actually help people and make the world a better place. When I'm done, Joyis will be released open source so that other homeless organization can use it. Keep an eye on SourceForge for the first release in a month or so.

    --
    Miko O'Sullivan
    1. Re:How I did it by MAXOMENOS · · Score: 2

      Sweet. I'm doing the same thing more or less for my own church, except they can't pay me squat. :)

    2. Re:How I did it by krinsh · · Score: 2

      The pay ain't much, but we can get by on it.

      I'm glad you are humble enough to go this route. I sincerely doubt that despite all the hippie hype; many others would be willing to balance their satisfaction with their pay. For example; recall the posts of those that say "They can't afford me."

      --
      I think with the interesting people, their lives can't possibly be wrapped up into a nice little package.
  30. Re:work for google by ninkendo84 · · Score: 2, Insightful
    Work at google

    Hmmmm... If only google was open source. Then maybe you would have a relevent comment.

    --

    $ make love
    make: don't know how to make love. Stop
  31. Re:Right on! by AJWM · · Score: 3, Insightful

    Do you think that maybe one of the reasons he got the 3000 was more due to the market flood?

    That's part of it. And that number is probably low for this area (Denver -- lots of former telecom high tech workers on the streets, and most of the new jobs (Lockheed, Raytheon) require security clearances).

    Another part is that typically the unemployment insurance system tends to encourage it -- if you're required to make N job contacts per week, if there's only one or two that really match your skills you'll send out resumes to places you know you don't have a hope in hell of getting hired at just to meet your quota. (Of course, just responding to ads is one of the worst job-search strategies, but it's the one most people default to.)

    --
    -- Alastair
  32. Re:Put up your resume in HTML and *Word* format? by Brad+Wilson · · Score: 2, Informative

    Yep, he's serious. I worked for a company that provided software for recruiters. Bar none, they were interested in Word format resumes ONLY. We took in plain text and HTML, and converted them to Word automatically, which at least gave you a chance (if you stuff converted well).

    Even when the world runs on the web, it's still hobbled by Word. :-p

  33. Re:A Ticketmaster recruiter? Double-fault! by WeeLad · · Score: 2, Interesting
    My girlfriend used a headhunter to apply for a not-IT job, and was turned down. A short while later she had an opportunity to talk to the would-be employer and they said they would've loved to have hired her, but the headhunter was way too pushy.

    The headhunter called the prospective employer numerous times every day trying to pressure them to make a decision and lied to the employer by saying that his client was currently weighing a couple of offers, "So they'd better hurry and make up their minds". The prospective employer told my gf that they would've hired her if she hadn't used that headhunter.

    That quickly turned me away from headhunters.

    --
    Seriously, Don't take anything I say seriously.
  34. Re:work for google by jnana · · Score: 2, Interesting

    My question is: what is Google doing that requires a top security clearance: http://www.google.com/jobs/openings.html#deploy

  35. a bit late by Tablizer · · Score: 5, Funny


    1999: "How To Get Hired As An Open Source Developer"

    2001: "How To Get Hired As A Developer"

    2002: "How To Get Hired"

  36. work cheap? by phorm · · Score: 4, Insightful

    Even with a College/Uni degree, or diploma, nobody should really expect to get out and immediately get a $75000/yr+superduperbenefits job. Really, what you should look for is a job that you would like, make you enough income to survive the first year, and looks really good on a resume.
    Barring that, you can also spot the companies you'd wish to work for that do pay the big bucks, and try getting in on one of the lesser positions.
    It's 100% easier to climb a ladder when you're already working in a company. It's also (ironically) very often easier to get a job when you've already got a job. You don't have to mention on your resume that you're "undervalued and underpaid", just list what you're capable of, and the fact that you are currently doing it helps prove so.

    There are a lot of small/starter companies who need computer support that frankly can't afford to pay big bucks in the beginning. They do look good on a resume though, and the work generally isn't too hard. Oftimes if you are lucky, said companies can end up growing, and as they grow - so often does your paycheque.

    It's hard to think of with the cost of living nowadays, but sometimes the value of a position is not in the paycheque, but in the respect, references, and experience it gains.

    Oh, and a big problem with small companies is that it gets really hard to leave when you're ready to move on... they tend to grow on you.

    1. Re:work cheap? by geekoid · · Score: 3, Insightful

      "It's 100% easier to climb a ladder when you're already working in a company. "

      I find that to be false.

      If you want to climb the ladder, the best way is to find another company that is hiring for that position. In general you get a higher pay increase, no need to deal with the projects that you have gotten associated with, and a better opertunity to start focusing your next step right away.

      I wish it wasn't that way, but it is.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    2. Re:work cheap? by krinsh · · Score: 2

      Oh, and a big problem with small companies is that it gets really hard to leave when you're ready to move on... they tend to grow on you.

      A big problem with small companies is that they'll call you on Monday and tell you your last check is that upcoming Thursday; so sorry, nice working with you these past eight months.

      There are risks and advantages to any size team or company. The smaller the team; the more likely you are to have several responsiblities where you can handle support tasks of varying types. You aren't just there to do one task, and one task only. You get into larger groups and oftentimes you aren't going to be branching out into other areas of interest because there are several specialists per task already.

      I was going to say that you risk the smaller company going under and you losing your job; but larger companies are just as likely to rid themselves of you nowadays than they would have been 2 or 5 years ago. I'll take the less pay and broader opportunity of a small team inside a big company and wait for the economy to so-called "right itself" in due time.

      --
      I think with the interesting people, their lives can't possibly be wrapped up into a nice little package.
    3. Re:work cheap? by phorm · · Score: 2

      Good point, that actually happened to me... found out Monday, done on Thursday. Of course, nowadays you're not even safe in a big company. It's easier to see it coming, but if you're a small guy you tend to be vulnerable to downsizing.

    4. Re:work cheap? by krinsh · · Score: 2

      Yep. And now I've discovered as a consultant; you need to be aware that companies struggling very hard to continue being viable in the current market will try and slide a lack of specific benefits (like holidays) past you and also put a lot of pressure on you if you *do* find better work during a 2- or 3-month gig and leave before it is complete.

      On the same note; you may have to be pretty flexible with your days and hours in a one- or two-week period as you transition and help the other temp get situated. But you know; 10+ years ago when I was an admin assistant trying to go to school and get a different career than clerical; you knew you had to be flexible in order to get paid.

      --
      I think with the interesting people, their lives can't possibly be wrapped up into a nice little package.
  37. Well... by Snork+Asaurus · · Score: 5, Insightful
    It's easy to forget that there are several different categories of software development, each with different things driving them. Here's a gross simplification of how I see it:

    There are 3 distinct major groups of developers:

    1 - people who earn money developing software for sale as a product: to them, open source generally != good

    2 - people who earn money developing software (embedded, hardware device drivers, etc.) to support another product that is sold: to them open source: sometimes == good and sometimes != good (gives away, architectures, secrets)

    3 - people who earn money developing software for IT purposes and/or in-house use: to them, open source generally == good

    Of course, there are many other groups of developers (academic, recreational, etc.) and there is intermingling, so the above is not a hard and fast rule.

    I also think that this is also one of the reasons that you often see acrimonious debate here at /. - each group has a different set of objectives and priorities.

    --
    Sigs are bad for your health.
    1. Re:Well... by Snork+Asaurus · · Score: 2
      Here's an example of the acrimony that I was talking about - note the use of the phrase 'outright lie' :

      this because it is an outright lie

      No, it is not. To be an outright lie I would have had to say "to them, only open source == good ". I did not.

      I said "to them, open source generally == good". Perhaps "generally" is too strong for you - YMMV, etc. I'll accept amending it to "sometimes". All situations are unique and neither of us should be so foolish as to suggest that we know and understand every possible scenario.

      I don't disagree with your IP argument, but I think that you are fixated on the applications development end of things. Don't lose sight of the hosting end of things. Many IT applications are Linux hosted because Linux is open source. There's a lot to be said for having control of your own destiny. Also, don't forget that not all IT exists in a competitive business environment (think governments, academic institutions, etc.).

      --
      Sigs are bad for your health.
  38. Why to hire OSS developers by Adam+Wiggins · · Score: 4, Insightful

    I spend a lot of time dealing with hiring for the IT staff at my company. These days, I pretty much instantly trash any resume doesn't include some sort of background with creating or maintaining an Open Source projust of reasonable size. It may be an unfair bias, but experience has shown me that OSS developers are almost always an order of magnitude more skilled and more responsible than applicants from other backgrounds.

    The self-motivation, self-discipline, organizational skills, and willingness to write code that the author isnt ashamed to display to the whole world are exactly the sort of traits that employers look for (or should be, anyway).

    1. Re:Why to hire OSS developers by spectecjr · · Score: 2

      I spend a lot of time dealing with hiring for the IT staff at my company. These days, I pretty much instantly trash any resume doesn't include some sort of background with creating or maintaining an Open Source projust of reasonable size. It may be an unfair bias, but experience has shown me that OSS developers are almost always an order of magnitude more skilled and more responsible than applicants from other backgrounds.

      The self-motivation, self-discipline, organizational skills, and willingness to write code that the author isnt ashamed to display to the whole world are exactly the sort of traits that employers look for (or should be, anyway).


      And, of course, the willingness to work for next to nothing doesn't hurt when it comes to your balance sheet.

      --
      Coming soon - pyrogyra
  39. Re:lol.. .. open source is hireable..? by foistboinder · · Score: 2
    ...and did you actually earn an income during this time?

    Yes

    and if so, who was paying it?

    A large aerospace company

  40. In this economy by Twister002 · · Score: 3, Insightful

    You should probably check to see whether or not the places they've "hopped" to in the past 12 months are still in business. I've had 3 jobs in the past 3 years and I have YET to voluntarily LEAVE a job. :)

    --
    "For a successful technology, honesty must take precedence over public relations for nature cannot be fooled." -Feynman
    1. Re:In this economy by dcavanaugh · · Score: 2
      There are different kinds of layoffs:
      • If you have 1000 non-union IT people, and a 5% layoff, then 50 of the "weakest links" are going to be gone.
      • If you have the same 1000 people and a 50% reduction, then there will be plenty of talented people among the 500 casualties, but the worst will go first.
      • With a 100% reduction, the talent pool starts to look pretty good, since the best & brightest are now available.

      Reference checks are difficult when the applicants past employers are out of business. Even when the ex-employer is still in business, most will never say anything negative ex-employees, and many have "zero disclosure" policies that circumvent the entire purpose of a reference check. I have had some success asking the magic question "Would you rehire?" Asking for an opinion instead of a statement of fact works wonders.

      It's difficult to tell the difference between a compulsive job-hopper, a deadbeat who gets consistently canned, and a talented person who is stuck with the LIFO scenario. It's also difficult to read a resume (or check references) to determine which of the 3 layoff scenarios has taken place. A letter of reference (with an e-mail that works) from a past supervisor may be the only thing that helps.
  41. Uhh by mindstrm · · Score: 2

    public company, etcetera.... Larry Ellison does not do all the hiring.

    Not having a degree WILL keep you frmo many corporate executive positions... there will be a point where you can go no further.. not because of what you know, but because of public perception... if they hire a VP with no degree, and he screws up, it's the fault of those who hired someone without even obvious credentials.

    1. Re:Uhh by El · · Score: 2

      Larry used to interview every potential new hire personally, until the company became too large for this to be practical. The point was that Larry and Bill do to a large extent determine the corporate culture of their respective companies.

      --

      "Freedom means freedom for everybody" -- Dick Cheney

  42. Re:Business Plan by killthiskid · · Score: 3, Interesting

    No no no no... the missing step is make something of value! OSS can do that. The problem is extracting profit from it... if the software itself is free, then there must be a alternative, such as service and support.

  43. In short, shy people have no chance (again) by bluGill · · Score: 2

    In short, shy comptuer geeks, which is many of the good ones, have little chance. I'm a good programer, but I like to sit in my little corner and program. One day I found myself out of work, and boom, I looked around, and so where most of the people who knew I was a good programer. (My small group)

    Mind you, the above story is nothing new. Every shy person faces it everytime we need a new job. I can deal with people, I just prefer not to, and when I have a good job I like to get the job I'm hired to do done.

  44. Re:Interesting... by the+eric+conspiracy · · Score: 2

    I think that 'self-taught' guys are better than graduates because they have the burning passion

    I think that some of the very best coders I've seen are field switchers - they have a strong educational background/knowledge of some other field, plus the passion/self-taught characteristics of the non-graduate. That is a powerful combination.

    One thing I watch for when hiring is what the programmer has at home - if he doesn't have at least three machines all running differeent OS's he doesn't have the calling.

  45. Re:Business Plan by shnarez · · Score: 2, Funny
    But then again, telling a potential employer that you read a lot of slashdot might not be a good thing :)
    Depends where you're applying for the job. For instance, if you're applying to Slashdot... oh, wait...
  46. Tin Foil Hat THIS, buddy!! by The+Iconoclast · · Score: 2

    Right, so this story is currently in the midst of being played out by YOURS TRULY.

    Thanks to everyone's FAVOURITE media monopoly, ClearChannel, which is the OWNER of TM, I and a friend were EACH screwed out of $40 because of our dietary restrictions due to our religious/ethical beliefs. Just for the record, I keep Kosher & my friend is a vegan, just like the HEADLINER of the Area2 concert, Moby. We wanted to see the Area2, obviously.

    We bought tickets over the web to the Area2 concert when it rolled into Philly. Before purchase there was NO indication of what restrictions would be placed on our tickets. Of course, AFTER we had paid, and our tickets printed on our printer, did we see all the fine print on the ticket that said, "subject to venue rules" or somesuch.

    Ok. Fine. We check the website for the venue, the Tweeter Center in Camden, NJ (btw, ALSO owned [or is that 0WN3D?] by ClearChannel), and it seems like we'd be allowed a backpack & a small amount of our own food. Of course, when we GET THERE, they inform us that we cannot bring our own food in. We are REFUSED ENTRY due to our religious beliefs. I and my friend cannot eat the food they have there, and it its a 6 hour+ show. Oh, I also forgot to mention the fact that they were only allowing ONE bottle of water per person. This was on quite possibly the HOTTEST day of the year in a venue that has NO shade.

    So, to sum up, I (and my friend) were REFUSED ADMITTANCE based upon our religious beliefs, not to mention the fact that apparently, ClearChannel wants to KILL all of their customers through dehydration. They refuse to refund the ticket price, claiming "all sales are final." However, they did NOT divulge the terms of purchase until AFTER the purchase had been made, and then even CHANGED terms on us!

    If that's not a tangible example of someone being harmed by CC's evil monopolistic behavior, I don't know what is.

    --
    Quando Omni Flunkus Moritati
  47. LUGs by Idou · · Score: 2, Insightful

    Join a LUG or create your own. I know a guy who kind of "took over" a LUG I helped started and then became to busy to participate in. He got a really good gig through the LUG and paid for the LUG's new site, as a token of gratitude.

    He knows his stuff and was always patient with everyone he explained stuff to. I lot of people come to LUGs thinking they can learn how to solve their own IT problem but instead they find it is easier pay a signficant amount of $ to this friendly guy they met at the local LUG.

    What can I say, Open Source is a give and take institution. Give freely and often, and you are bound to be noticed.

    Good luck!

    --
    Sdelat' Ameriku velikoy Snova!
  48. Well by mindstrm · · Score: 2

    then please, go hop jobs all you want.

  49. One way to get your resume taken seriously... by esconsult1 · · Score: 4, Insightful

    I've never been turned down for a job I interviewed for, and I dont have a degree, and I've never been fired. My skill sets are sparse: PHP, Postgresql Perl, MySQL, Apache, Linux etc... Here's what I did:

    1. Went into detail what I did in the last 3 jobs, I mean serious detail. It means that the people that I'll work well with, will appreciate my resume instead of some PHB looking for acronyms.

    2. Include links to articles I wrote, and postings I made in forums for all the above technologies. The last job I got was because they received help from some silly posting I made and forgot about years ago.

    3. Include links to interactive sites that you helped build. Forget the pretty stuff, the fancy HTML, that's not what you will be hired for, instead, link to the interactive portions of the site that actually do something.

    4. Always have some code samples handy with lots of comments. Include some OOP examples along with traditional procedural code.Even if they dont use OOP, at least they know that you can.

    5. Make sure that you will have lots of hits in google, which will turn up all your online activity.

    6. Dont bring your resume to the interview. Instead, when they ask for it, give them the URL where they can view it.

    7. Refuse a job where they require your resume in Microsoft Word format. It means that they are not really an open source shop, and the PHB's probably use Outlook, Exchange, Office and IE. Tell them that you are refusing the job because of that reason. They will respect you for having the balls to do it, and in the same vein, always submit your resume in text format in the email to the recruiter (not as an attachment).

    8. Be assertive in your resume, tell them exactly what you want to do. Dont be vague about what you want to do. Tell them how you can help them, and that you will make a great fit in their org. If possible, tailor your resume for each job you are applying for.

    9. Don't mention that you can use a word processor, browser, or spreadsheet. That's passe, everybody's expected to do that. Don't mention that you can admin an NT/2000 box (even if you can), instead, tell them in the interview.

    I guess there are more tips out there, but for last 2 jobs and 4 interviews in 6 years, those have worked well for me.

    1. Re:One way to get your resume taken seriously... by Maul · · Score: 2

      How do you avoid the problem of a PHB or HR Drone who is LOOKING for acronyms or fancy buzzwords in your resume? Or do you not, and feel these companies aren't worth your time?

      Your method sounds great if you're applying to a place where the person who is reading the resume is someone with a clue.

      However, more often than not they are looking for X+Y years of experience with something that sounds hot in the market, where X is the number of years the product has been out, and Y is greater than 0.
      A college degree is often "preferred but not required," but it seems an absolute requirement to have 5 years experience with a technology less than a year old. Either that or you must know about all the new fads in web design as well as know how to operate ancient systems from the 80s.

      For example, I saw a posting that required 5 years of experience with .NET and C#. Seriously! How the heck does anyone get past that without lying?
      The HR Drone will just toss a resume in the garbage if it doesn't say "5 years of .NET and C#" on it, won't they?

      --

      "You spoony bard!" -Tellah

    2. Re:One way to get your resume taken seriously... by Frobnicator · · Score: 2
      Most of these are the generic items that apply to everyone. I've looked for jobs, I've hired people. When looking for a job, think first about what you would do when hiring people.
      1. Went into detail what I did in the last 3 jobs, I mean serious detail. It means that the people that I'll work well with, will appreciate my resume instead of some PHB looking for acronyms.
      Not enough detail is a problem, but so is detailing everything. That's covered in pretty much every job-hunting book.
      2. Include links to articles I wrote, and postings I made in forums for all the above technologies. The last job I got was because they received help from some silly posting I made and forgot about years ago.
      I doubt they read your links. Someone may have looked at one or two, but that looks like they went searching and found you, not the other way around.
      3. Include links to interactive sites that you helped build. Forget the pretty stuff, the fancy HTML, that's not what you will be hired for, instead, link to the interactive portions of the site that actually do something.
      4. Always have some code samples handy with lots of comments. Include some OOP examples along with traditional procedural code.Even if they dont use OOP, at least they know that you can.
      Never hire a programmer without looking at code. Never apply for a job without a code sample. If you are fresh out of college you have the most code samples -- every assignment you ever did. You have the least if you are a 10-year in-the-trenches person, but then the company should consider work history over your coding style.
      5. Make sure that you will have lots of hits in google, which will turn up all your online activity.
      That's only important if that's your line of work. Just like getting a job in the game industry is easier if you have your name in credits, or the movie industry if your name is on the credits. Or going into academia you should bring or have online a list of your publications. Or applying for a broadcasting position, try to show how you affect television ratings. That step is just another way to say "I can do this job." What's more important is that if you google for yourself, you don't find NEGATIVE things.
      6. Dont bring your resume to the interview. Instead, when they ask for it, give them the URL where they can view it.
      I did that ONCE. Never again. ALWAYS bring a resume. You can say 'I would like you to look at my web site, which has links' if you interview is going well (or bad). A good resume/CV will lead the interviewer and help them ask specific questions about you. Such as "I see you worked on project X. Tell me about it." When I interview, I bring a folder. The top-most tabbed section has several sets of resumes and CV's, including some specifically targeted for them asking me questions. I have copies of questions that I would ask if I were interviewing myself for my dream job. I have statistics for the job they are offering, salaries for the area, and other notes. I have extensive notes about the company (which I make some sort of comment about). I also have the normal stuff (old jobs, old salaries, contacts, references, etc.) I have in my binder many code samples, including a CD with samples that I can leave with them containing many samples. In short, when you go to an interview, BE PREPARED, they may actually want to hire you.
      7. Refuse a job where they require your resume in Microsoft Word format. It means that they are not really an open source shop, and the PHB's probably use Outlook, Exchange, Office and IE. Tell them that you are refusing the job because of that reason. They will respect you for having the balls to do it, and in the same vein, always submit your resume in text format in the email to the recruiter (not as an attachment).
      I would change that to say "Refuse a job where they want you to use tools that you don't want to use, and tell them why if you have moral, ethical, or professional reasons." That argument applies equally well when applied to any other area. Just saying "I WON'T use (brand) tools" is bad, it makes you look immature, uncooperative, and unprofessional. Saying "I WON'T use (brand) tools because I have had these experiences with it" is still bad, it implies that you didn't bother to get over the learning curve. Saying "I will not use or don't like (brand) because (state reasons), may I use (alternate tools) instead?" is about the best you can do in that situation, because they can see your reasoning (or lack thereof) and consider your alternative. They may feel the same way and just haven't expressed it.
      8. Be assertive in your resume, tell them exactly what you want to do. Dont be vague about what you want to do. Tell them how you can help them, and that you will make a great fit in their org. If possible, tailor your resume for each job you are applying for.
      You can read that in any resume book, and most job hunting books. Some people will give you the job if you are basically qualified and are the only one who asks "Will you give me the job?"
      9. Don't mention that you can use a word processor, browser, or spreadsheet. That's passe, everybody's expected to do that. Don't mention that you can admin an NT/2000 box (even if you can), instead, tell them in the interview.
      I disagree. If you are looking for an entry level data-entry person, they WANT to know that you can type. They WANT to know your WPM and ten-key speed. They WANT to know that you can use spreadsheets IF that's what they're using. If you are being hired for your PHP and SQL knowledge, don't bother going into detail about your C++ skills. If you are being hired as an assembly-level programmer for 3D graphics, don't ramble on about the PHP solution you wrote on your last job.

      But on the other hand, the article was pretty good.

      --
      //TODO: Think of witty sig statement
  50. please stop the fud. by gimpboy · · Score: 2


    Most companies consider their internal IT applications to be Intellectual Property which is used as a competitive advantage in the marketplace. You do not want your business competitors to get a hold of your internal apps and make money off of your development efforts. From the company's prespective, there is nothing to gain, and everything to lose.


    speaking in terms of the gpl: if you extend a gpled product for internal use, you dont have to relaease the source. this is because the software is being used internally and thus not being distributed. because the applications are being used internally, your competitors wont have this advantage.

    --
    -- john
  51. Re:work for google by aat · · Score: 2

    For deploying google at defense or defense contractors' internal networks, seems likely.

  52. Shared political ideology, not talent, got you job by AHumbleOpinion · · Score: 2, Troll

    Because I hated Microsoft. Im not kidding. He figured that if I was smart enough to dislike Microsoft that I probably knew what I was talking about.

    You may very well be a very talented person, but your boss may be an idiot. It seems your boss hired you due to a shared political ideology. Do you think half the vocal MS haters around here could build a working non-trivial system?

  53. Open Source needs very few Pros by AHumbleOpinion · · Score: 2

    I guess the -98%- rest of us hard working experienced programmers, project managers and architects can just suck eggs.

    Well open source needs very few Pros, or rather it can support very few Pros. It is like sports, there is only a handful of professional spots available. After toying with the idea in school you should expect to need to find a "real" job and resign yourself to playing in a local softball, basketball, or soccer league.

  54. Excuse me by brandonsr · · Score: 2, Insightful

    How to get hired as an open source developer. I'm sorry, I don't understand how this is possible. Mod me down, I don't care! How on earth can someone get paid for developing free software. Yes, I know all the pro-open source people are going to attack me. Bring it on.

  55. Self-taught are not as good ... by AHumbleOpinion · · Score: 3, Insightful

    I guess I have to own up and say that I think that 'self-taught' guys are better than graduates because they have the burning passion for computers, technology and programming - and they want to do something tangible with it now!

    The self-taught are usually not as good as those who are self-taught and formally educated. Why do so many think the two are mutually exclusive? At age 37, I'm there too, you should be able to recall a time when those entering computer science programs did so because they had passion and interest, not because the high school guidance counselor said it was a good career path. College can give you access to a lot of equipment, resources, and experience that can be used for personal project and interests.

  56. Re:Business Plan by Leeji · · Score: 2

    But then again, telling a potential employer that you read a lot of slashdot might not be a good thing :)

    Especially when your cover letter starts off, "Dear M$"

    --
    It all goes downhill from first post ...
  57. Re:Right on! by klevin · · Score: 2

    Everyone I've talked to says this (responding to ads almost never works). The method, apparently, is to get work by having/developing contacts that have inside info on and/or influence over the hiring process. I can't say that they're wrong. The problem is what to do if you have no real contacts other than with the people you used to work with.

  58. A CompSci degree is more than just a bit of paper by horza · · Score: 2

    My experience is that good managers who are knowledgable about the workforce will hire people without degrees. People who are poor managers and in over their heads are too afraid to hire non-degreed personnel because they feel it will reflect poorly on them. It's the HR equivalent of "no one ever got fired for buying Microsoft".

    I would consider someone with a degree over someone without (if they were roughly equal in all other ways) as I know the person that studied CompSci will have a reasonable exposure to algorithms, OS and hardware architecture, as well as software engineering methodology. You at least know you aren't going to get someone that would use a O(n^2) algorithm for a basic sort. Of course you can take time and give all the candidates extensive technical tests, but with a degree that's already done at someone else's expense.

    Phillip.

  59. Open Source Development Labs by Bryce · · Score: 2

    OSDL (http://www.osdl.org/) is hiring
    right now, particularly looking for people
    with perl/C/Linux development and sysadmin
    experience.

    OSDL's a non-profit in Beaverton, Or, focused on helping provide tools,
    patches, etc. to make Linux better.

    Needs exactly the sort of
    people described in this article as
    looking for exactly this kind of company.