An easier alternative - I'm really surprised that out of work graduates from the US aren't getting Australian working holiday visas and flooding down here. Due to a resources boom (thanks China) unemployment is only 5% here. There are skills shortages in most technical areas and particularly mining. The Reserve Bank of Australia just raised interest rates again because it was worried about the economy overheating.
The working visa has some restrictions - you must be between 18 and 30. It's only valid for 12 months and you can only work for a maximum of 6 months for any one employer. The last provision is a bit tough, but there are still plenty of 6 month contracts around.
Why do Americans have such a strong reluctance to travel abroad for work? I've never understood it. It's a great opportunity to get some work experience, live a little and, particularly for the mid-west and east coasters, skip winter!
>Why do Americans have such a strong reluctance to travel abroad for work?
To fully understand this you'd probably have to live in the US. We grow up constantly hearing things like "in America at least we know we're free" and many of us can't help but think "why do they keep repeating this? Is everyone else not?". We're constantly indoctrinated about being the best in the world, so no matter how bad things are here, they must be worse everywhere else right?
We have an enormous amount of people in the US who've never been outside of it and have a completely wrong picture of the rest of the world. It was shocking for me, for example, when I came over to Europe and saw places like Sweden and France. I saw what I knew as socialism, but it seemed to be working! And the more I looked the more it appeared to actually work better for the average person. It was so demonized back home, who could have imagined that it's actually just a trade off like everything else. Some previously good friends of mine now literally think I'm a communist (sadly I'm not even exaggerating).
There are plenty of reasons why Americans don't like to travel abroad for work. I'm sure other posts will cover them.
However, I don't think many people know about this particular working visa. My sister lives in Australia and I hadn't heard of it until your post. I just looked it up and it looks like it started in 2007. Too bad I no longer fit the age requirements. I'll pass the info along to my younger brother, though. Good tip.
I think you will find the majority of the western world have a strong reluctance to travel abroad for work.
- Working abroad means leaving behind friends, family etc. To many people, this is a big deal
- A large majority of the working population have children. Moving abroad is not a simple process when you have a family and it then also means many people's support network (fellow parents, grandparents) disappears
Also I must say, there is a dearth of interesting companies to work for in software / technology outside of the USA (I'm sure someone will now provide me with a nice list and prove me wrong :). I'm in the UK and can only think of a handful of companies I would love to have a job at.
[I'm hoping to do something about this with all the job talk at HN recently and make discovering cool companies to work for easier]
I have no reluctance to travel abroad for work at all. There's tons of places elsewhere in the world I'd love to work. But when the jobs you want are in America (or at least in greater density or number than elsewhere) why would you leave America?
Are you sure that US citizens can get working holiday visas in Australia? I was under the impression that most common-wealth countries had such agreements (and for some odd reason Japan is included in there), but that was it. For example, a US citizen can't get a working holiday visa in Canada, but a Japanese, Australian, or UK citizen can.
Why do Americans have such a strong reluctance to travel abroad for work? I've never understood it.
Do Americans have a strong reluctance to travel abroad for work? I haven't noticed one way or the other. When I graduated in 2001, my 'reluctance' was based on broke-ness. The difficulty affording even a $75 fee (for a background check to work for the local school district) meant that the thought of leaving all my connections and going several thousand dollars into debt for overseas relocation didn't even cross my mind.
Actually, that's a 103 step program, but I agree with the advice. If you want to get a job, you need experience... And the internet is full of projects that need bugfixes. That stuff looks -great- on a resume. Take that from someone who interviews hirees.
I agree. As I mentioned on one of my CV reviews from the other week(Sorry if I didn't get to yours yet, I have my list but it takes me 10-15 minutes to do a good one and I've been short on time). When I get a CV I scan it quickly for an idea of what the person is about then throw it out or in another pile for a more in depth read.
A link to github or a blog or something where I can see some of their work "in the wild" (not just a portfolio link) always gets them in the second pile as I find code a far better indicator of a good programmer than a good CV.
But there are a few fields that are hiring like crazy. One of them is mine: software engineering. Major tech firms cannot hire fast enough. It's so competitive that you do not need to have a degree (I don't).
Was this written in the late 90's?
I follow job listing sites almost daily, and I'm just not seeing this. I'm also not seeing it in the volume of headhunters contacting me.
And thirdly, what job listings I do see, they have absurd ideas of what qualifications they require. Yesterday I saw a job listing for perl scripter for system automation tasks requiring a BSCS, MS preferred, and a little while ago I saw a sysadmin job requiring a BSCS.
I'm not in the middle of nowhere, I'm in the Boston/128 area.
So do I have the worst job hunting skills ever or is this guy living in a bubble?
Your difficulty and this gentleman's relative lack of difficulty finding a job probably has a lot to do with location. Second runner up is probably credibility. Let me explain.
My experience is in line with the author's. Finding a job has always been relatively easy (beginning at a certain point, which I will elaborate on) and I do not have a degree of any kind. It's my opinion that three factors are primarily responsible for my state of affairs.
1. I started working at a local ISP when I was 15 years old. This was around the time that 28.8kbps modems were all the rage. While I was very green I had unbounded enthusiasm and desire to learn whatever I could about technology. The ISP got a super cheap tech support person and I got paid to learn. After a year I got a chance to do UNIX sysadmin work, and my level of experience began to snowball.
The (fairly obvious) takeaway here is that I built experience. Businesses don't want to train you if they can help it. Not able to find a learn-on-the-job opportunity? Take the author's advice and contribute to an interesting open source project.
2. Befriending an employee of one of the largest ISPs in the United States ended up landing me a development position on a pretty large contract. I worked damn hard, and ended up contributing in a fairly visible way. Because the job was for a company in the Fortune 50 I've since been able to point to it as social proof that I at least have a vague idea of what I'm doing. Employers love this. This is when job hunting became dramatically easier.
You may think the takeaway here is to be lucky, but I disagree. The takeaway is to get to know people that you can develop mutually beneficial relationships with. To this day I still get contract work and referrals from people I worked with on that one job.
3. Location. Companies will sometimes relocate you, but I've never seen one that will do it without there being a very compelling reason to have you on staff (ie, experience and a proven track record). You have to go where the jobs are. Sometimes you have to suck it up, move away from your family and friends, become a nobody, and start pulling in a paycheck. Once you do you can start planning (and saving) for the luxury of living and working in a desirable place.
The takeaway here? Get away from the crowd. In my experience there are at least two good markets for developers, Denver/Boulder CO (Denver being easier than Boulder), and Kansas City MO/KS. I'm not a big fan of Kansas or Missouri (sorry natives, you're all great people), but Colorado is a beautiful place with lots to do outside your cube/apartment. The job markets in both those places are reasonable and you can be relatively well paid even with limited experience. How do they compare with SF/NYC? Not even close, but it's way easier to stand out from the crowd when there is no crowd. Being in the middle of nowhere can sometimes be a benefit.
In my experience, mainstream jobsites are awful for software jobs. Jobseekers are sitting there firing off CV's left right and centre, and the recruiters put things like "MUST have a BSc or MSc in Computer Science" to try and stem the tide.
Good companies don't care if you have a CS degree as long as you can code and think. That said, someone may have embellished the job requirements and if you think you'd be a good fit for a job it may be worth applying anyway.
I'm not sure what the situation is if you have no degree at all, or a degree with no scientific or technical element, but it helps to have evidence of your skills, and whatever your situation it really helps to know people who have a good impression of you and your abilities.
I'm about to graduate BSCS from an engineering school, and every networking job I've seen wants experience + CCNA/CCNP, and the system administration jobs want BSCS + experience. I have 5+ years of part time IT experience and a summer of full time basically admin level experience and yet I can't even get interviews. Pretty depressing. =|
I see two problems with this. One you're expecting them to come to you just because you are there or looking in the worst spots for good jobs(public job sites).
Get out and contact the headhunters yourself and work with them and network with all the people you do know and hit them up for positions. They might not have anything at their work but its possible they or one of their colleagues has or knows someone who does have a position open.
Secondly you are taking the BSCS or MS lines in job ads at face value. When they say "Requires a BSCS" what they mean is "Requires a BSCS or experience".
If this article is targeted at people with no experience (ie it mentions learning how to use IRC), is recommending that they fix bugs in C++ code really the right answer?
Why not start with a Python project or something more realistic?
I specifically chose Chromium (or another browser) because it is one of the few pieces of open source software that normal people would have direct experience using.
Seeing your fixes shipped to you and your friends' browsers is an awesome motivational tool.
It's true that it's harder, but it seemed like a reasonable trade-off.
My main concern with picking a browser wasn't the difficulty it was the expense of having a good machine to work with. Sadly this applies to all browsers that I'm aware of. Building Mozilla is terrible. WebKit is probably the best; it just contains less code (you only build the rendering engine when you work on WebKit, not the browser).
Learn the difficult fundamentals of programming first (pointers, data structures) first. Experience with C/C++ and user-level systems programming (IPC, pthreads, BSD sockets and/or their Windows equivalents) makes you stand out amongst job applicants; writing database driven web applications in scripting languages does not. If latter is ultimately your passion, you'll have no trouble transitioning: successful web companies seek out developers who understand more than a thin segment of the full stack (see Brad Fitzpatrick's interview in Coders at Work for a good discussion of this).
I suspect there are also plenty of bugs in Chromium et al which require non-trivial scripting to find and fix (who does exclusively manual testing any more?)
My friend is quite impressive at the guitar despite never having lessons. He says the day he went from beginner/average to pretty damn good was when he decided to learn a Hendrix part way beyond his then skill level.
C++ isn't that hard, I got a pretty good hang of it after a couple months on my first project out of college. Why is a Python project "more realistic"? the learning curve is probably similar.
Advice is to contribute to Chromium, fixing 50 bugs over the course of a year or so. Might not be an easy path though, personally when I tried to compile Chromium, it took my PC 8 hours compiling before coming up with a fatal error. Been thinking about getting EC2 instances to compile it, has anyone tried that? Software license costs for Visual Studio put me off a bit.
Might not be an easy path though, personally when I tried to compile Chromium, it took my PC 8 hours compiling before coming up with a fatal error.
Welcome to software development. :-) Seriously, I probably spend at least 10% of my time dealing with broken libraries, badly documented build processes, and other depressing obstacles.
If you can get past these kinds of problems—and more importantly, if you submit fixes to spare the next person the pain—then you'll make a great developer.
Compiling Chromium crashed my box by overheating it. Definitely not a newbie-friendly project as so much of it is implemented in C++. While Mozilla's build may be equally terrifying, at least they have the good sense to implement good portions of the UI in Javascript.
It's great that the community is giving advice on what steps to take for getting a programming job, but I would like to add that finding a job is a short term fix. If one is only trying to work out how to get a job for the sake of getting a job, it will only be a matter of time before one is bored. But then again, you'll probably only realise this only having gone through the process. Try to find something that interests you, which may or may not be programming.
1. Employers are often focused on hiring very specific skills sets. Having fixed a C++ bug in Chromium should impress them, but if they need a Django expert they still see you as a novice. It can be hard to present yourself as a well-rounded candidate if all your experience is with one project.
2. In a couple of interviews I've had, I've noticed a distinct bias towards valuing paid work more than open source contributions. It's often hard to get interviewers to understand that something I've done for free is on the same scale (or greater) than things I've been paid for.
This article is like a breath of fresh air. One of the few things you read about the industry that doesn't make you feel vastly underqualified. I'll definitely take aboodman up on his offer (coincidentally I logged onto freenode for the first time in my life a few hours before reading this...), although I expect he's inundated with responses right now so I'll leave it a few days.
This is an interesting path to get a good software job. I agree that when it comes to software jobs, a good resume with a lot of techno buzz words does not mean anything. An interview that gives coding puzzle can easily tell a person if he's capable or not. But a non-tech hiring manager will not be able to carry one out, a few references of open source projects, bug fixes definitely boost up your scores quite a bit. I've hired some good people and some bad before, at the end of day, your project success is not based on how many PhDs there are on the team, but how many coders that can deliver.
What's the most effective way to mention open source work on resumes? I generally mix it in with other non-school- or -work-related stuff in a "projects" section, but is there a smarter way to emphasize it?
If you've got a lot of it, make it its own section. If you don't, but you think it's significant work experience, I'd put it under 'work experience'.
Last time I wrote a resume, I didn't have enough that I felt it was significant, so it went down as a relevant hobby, just like volunteering at the computer shop in and winning awards for computer knowledge high school.
For code, the best way is a URL to the bug tracker or commit log which shows all of your contributions. Use bit.ly if need be. A surprising number of people will list projects they've barely contributed to, using languages they barely know.
If you have 2 or 3 projects to list, an "Open Source Contributions" section is fine with me. The main thing to avoid is fancy formatting. How you divide things up into sections is not a big deal.
I like this article because I got my job this way. :)
Part of me loves this kind of inspiring advice ("you too can grow up to be president"). And it certainly is true for some people.
But the truth is that most people who try this will fail. Very few people have the right combination of aptitude and attitude to do this (especially considering that the intended audience is people without an IT background).
[edit] Perhaps the message to take away is that there is a low barrier to entry in our field, so it's worth giving it a shot.
I agree that learning how to get a website up and running is an easier way to go (and hence more likely to succeed and be morale-boosting). Even if web development isn't considered as "hard-core" as working on compiled applications in C++, there are still a decent amount of jobs available.
[+] [-] tjmc|15 years ago|reply
The working visa has some restrictions - you must be between 18 and 30. It's only valid for 12 months and you can only work for a maximum of 6 months for any one employer. The last provision is a bit tough, but there are still plenty of 6 month contracts around.
Why do Americans have such a strong reluctance to travel abroad for work? I've never understood it. It's a great opportunity to get some work experience, live a little and, particularly for the mid-west and east coasters, skip winter!
[+] [-] loewenskind|15 years ago|reply
To fully understand this you'd probably have to live in the US. We grow up constantly hearing things like "in America at least we know we're free" and many of us can't help but think "why do they keep repeating this? Is everyone else not?". We're constantly indoctrinated about being the best in the world, so no matter how bad things are here, they must be worse everywhere else right?
We have an enormous amount of people in the US who've never been outside of it and have a completely wrong picture of the rest of the world. It was shocking for me, for example, when I came over to Europe and saw places like Sweden and France. I saw what I knew as socialism, but it seemed to be working! And the more I looked the more it appeared to actually work better for the average person. It was so demonized back home, who could have imagined that it's actually just a trade off like everything else. Some previously good friends of mine now literally think I'm a communist (sadly I'm not even exaggerating).
[+] [-] rdouble|15 years ago|reply
However, I don't think many people know about this particular working visa. My sister lives in Australia and I hadn't heard of it until your post. I just looked it up and it looks like it started in 2007. Too bad I no longer fit the age requirements. I'll pass the info along to my younger brother, though. Good tip.
[+] [-] smiler|15 years ago|reply
- Working abroad means leaving behind friends, family etc. To many people, this is a big deal
- A large majority of the working population have children. Moving abroad is not a simple process when you have a family and it then also means many people's support network (fellow parents, grandparents) disappears
Also I must say, there is a dearth of interesting companies to work for in software / technology outside of the USA (I'm sure someone will now provide me with a nice list and prove me wrong :). I'm in the UK and can only think of a handful of companies I would love to have a job at.
[I'm hoping to do something about this with all the job talk at HN recently and make discovering cool companies to work for easier]
[+] [-] sliverstorm|15 years ago|reply
[+] [-] pyre|15 years ago|reply
[+] [-] Goladus|15 years ago|reply
Do Americans have a strong reluctance to travel abroad for work? I haven't noticed one way or the other. When I graduated in 2001, my 'reluctance' was based on broke-ness. The difficulty affording even a $75 fee (for a background check to work for the local school district) meant that the thought of leaving all my connections and going several thousand dollars into debt for overseas relocation didn't even cross my mind.
[+] [-] gaustin|15 years ago|reply
[+] [-] wyclif|15 years ago|reply
Why the restrictive cutoff at age 30?
[+] [-] wccrawford|15 years ago|reply
[+] [-] sanswork|15 years ago|reply
A link to github or a blog or something where I can see some of their work "in the wild" (not just a portfolio link) always gets them in the second pile as I find code a far better indicator of a good programmer than a good CV.
[+] [-] KevinMS|15 years ago|reply
Was this written in the late 90's?
I follow job listing sites almost daily, and I'm just not seeing this. I'm also not seeing it in the volume of headhunters contacting me.
And thirdly, what job listings I do see, they have absurd ideas of what qualifications they require. Yesterday I saw a job listing for perl scripter for system automation tasks requiring a BSCS, MS preferred, and a little while ago I saw a sysadmin job requiring a BSCS.
I'm not in the middle of nowhere, I'm in the Boston/128 area.
So do I have the worst job hunting skills ever or is this guy living in a bubble?
[+] [-] ary|15 years ago|reply
My experience is in line with the author's. Finding a job has always been relatively easy (beginning at a certain point, which I will elaborate on) and I do not have a degree of any kind. It's my opinion that three factors are primarily responsible for my state of affairs.
1. I started working at a local ISP when I was 15 years old. This was around the time that 28.8kbps modems were all the rage. While I was very green I had unbounded enthusiasm and desire to learn whatever I could about technology. The ISP got a super cheap tech support person and I got paid to learn. After a year I got a chance to do UNIX sysadmin work, and my level of experience began to snowball.
The (fairly obvious) takeaway here is that I built experience. Businesses don't want to train you if they can help it. Not able to find a learn-on-the-job opportunity? Take the author's advice and contribute to an interesting open source project.
2. Befriending an employee of one of the largest ISPs in the United States ended up landing me a development position on a pretty large contract. I worked damn hard, and ended up contributing in a fairly visible way. Because the job was for a company in the Fortune 50 I've since been able to point to it as social proof that I at least have a vague idea of what I'm doing. Employers love this. This is when job hunting became dramatically easier.
You may think the takeaway here is to be lucky, but I disagree. The takeaway is to get to know people that you can develop mutually beneficial relationships with. To this day I still get contract work and referrals from people I worked with on that one job.
3. Location. Companies will sometimes relocate you, but I've never seen one that will do it without there being a very compelling reason to have you on staff (ie, experience and a proven track record). You have to go where the jobs are. Sometimes you have to suck it up, move away from your family and friends, become a nobody, and start pulling in a paycheck. Once you do you can start planning (and saving) for the luxury of living and working in a desirable place.
The takeaway here? Get away from the crowd. In my experience there are at least two good markets for developers, Denver/Boulder CO (Denver being easier than Boulder), and Kansas City MO/KS. I'm not a big fan of Kansas or Missouri (sorry natives, you're all great people), but Colorado is a beautiful place with lots to do outside your cube/apartment. The job markets in both those places are reasonable and you can be relatively well paid even with limited experience. How do they compare with SF/NYC? Not even close, but it's way easier to stand out from the crowd when there is no crowd. Being in the middle of nowhere can sometimes be a benefit.
All that said, good luck.
[+] [-] SandB0x|15 years ago|reply
Good companies don't care if you have a CS degree as long as you can code and think. That said, someone may have embellished the job requirements and if you think you'd be a good fit for a job it may be worth applying anyway.
I'm not sure what the situation is if you have no degree at all, or a degree with no scientific or technical element, but it helps to have evidence of your skills, and whatever your situation it really helps to know people who have a good impression of you and your abilities.
For better jobs boards, look at:
Stack Overflow Careers http://careers.stackoverflow.com/Jobs?searchTerm=&search...
HN Who's Hiring threads. Eg http://news.ycombinator.com/item?id=1659409
Also, check local user groups for whatever languages/technologies you're interested in.
[+] [-] greyhat|15 years ago|reply
[+] [-] sanswork|15 years ago|reply
Get out and contact the headhunters yourself and work with them and network with all the people you do know and hit them up for positions. They might not have anything at their work but its possible they or one of their colleagues has or knows someone who does have a position open.
Secondly you are taking the BSCS or MS lines in job ads at face value. When they say "Requires a BSCS" what they mean is "Requires a BSCS or experience".
[+] [-] angelbob|15 years ago|reply
[+] [-] asolove|15 years ago|reply
Why not start with a Python project or something more realistic?
[+] [-] aboodman|15 years ago|reply
Seeing your fixes shipped to you and your friends' browsers is an awesome motivational tool.
It's true that it's harder, but it seemed like a reasonable trade-off.
My main concern with picking a browser wasn't the difficulty it was the expense of having a good machine to work with. Sadly this applies to all browsers that I'm aware of. Building Mozilla is terrible. WebKit is probably the best; it just contains less code (you only build the rendering engine when you work on WebKit, not the browser).
[+] [-] strlen|15 years ago|reply
I suspect there are also plenty of bugs in Chromium et al which require non-trivial scripting to find and fix (who does exclusively manual testing any more?)
[+] [-] Tycho|15 years ago|reply
[+] [-] guelo|15 years ago|reply
[+] [-] ximeng|15 years ago|reply
[+] [-] ekidd|15 years ago|reply
Welcome to software development. :-) Seriously, I probably spend at least 10% of my time dealing with broken libraries, badly documented build processes, and other depressing obstacles.
If you can get past these kinds of problems—and more importantly, if you submit fixes to spare the next person the pain—then you'll make a great developer.
[+] [-] wyclif|15 years ago|reply
Sounds like a good idea to me, esp. for people working on a laptop.
[+] [-] Tichy|15 years ago|reply
Seriously, do you have to compile the whole program for every code change? I suspect that is not necessary?
[+] [-] technomancy|15 years ago|reply
[+] [-] rrrhys|15 years ago|reply
[+] [-] jim_dot|15 years ago|reply
[+] [-] bhoung|15 years ago|reply
[+] [-] celticjames|15 years ago|reply
1. Employers are often focused on hiring very specific skills sets. Having fixed a C++ bug in Chromium should impress them, but if they need a Django expert they still see you as a novice. It can be hard to present yourself as a well-rounded candidate if all your experience is with one project.
2. In a couple of interviews I've had, I've noticed a distinct bias towards valuing paid work more than open source contributions. It's often hard to get interviewers to understand that something I've done for free is on the same scale (or greater) than things I've been paid for.
[+] [-] Tycho|15 years ago|reply
[+] [-] jkin|15 years ago|reply
[+] [-] Mongoose|15 years ago|reply
[+] [-] wccrawford|15 years ago|reply
Last time I wrote a resume, I didn't have enough that I felt it was significant, so it went down as a relevant hobby, just like volunteering at the computer shop in and winning awards for computer knowledge high school.
[+] [-] sayrer|15 years ago|reply
If you have 2 or 3 projects to list, an "Open Source Contributions" section is fine with me. The main thing to avoid is fancy formatting. How you divide things up into sections is not a big deal.
I like this article because I got my job this way. :)
[+] [-] usedtolurk|15 years ago|reply
But the truth is that most people who try this will fail. Very few people have the right combination of aptitude and attitude to do this (especially considering that the intended audience is people without an IT background).
[edit] Perhaps the message to take away is that there is a low barrier to entry in our field, so it's worth giving it a shot.
[+] [-] bsk|15 years ago|reply
There are better routes for new programmers IMHO.
Start at http://rubyonrails.org/ and build a website you find useful.
Learn SharePoint or BizTalk, those are boring but in very high demand now.
Even more boring, sing up for a cheap 6 month Cobol course in India.
[+] [-] jordanlev|15 years ago|reply
[+] [-] smh|15 years ago|reply
[+] [-] RockyMcNuts|15 years ago|reply
[+] [-] RockyMcNuts|15 years ago|reply