Slashdot Mirror
How Does a Self-Taught Computer Geek Get Hired?
An anonymous reader writes "I'm essentially a self-taught computer geek who started learning BASIC at age 12, but decided NOT to do the traditional computer-nerd thing (comp sci or physics, computer degree, etc.). I've essentially kept up with computers as a hobby, teaching myself web-design, Linux/LAMP, Javascript, and now Drupal. I've worked for a short time at a web dev shop but mostly have just done freelance projects and here-and-there stuff for websites or projects, many of which have gone under or are no longer accessible. I'm creative, have Photoshop/GIMP skills, I'm personable and self-motivated...and I'd like to get a 'real' job now but I don't really look like much on paper — how can I (specifically with Drupal) make myself look good on a CV and/or establish solid credentials that will make people more willing to take a chance and hire me? Will Drupalcon 2012 help me make inroads? Are there other ways to 'prove' myself to be a capable web admin/developer?"
Instead of running your own business. Then you don't need to provide your quality and skills to anyone, and it can make more money in the long run as you are not limited to your salary and don't have to fear getting fired. If you know web-design and running Drupal, then start to work with those. Make your websites. Now, learning some information about other subjects will help. Learn things like marketing, SEO and in general running a business. Most of the information can be found on webmaster forums. Then it's up to you - you can even sell your services to local businesses. You also have the added benefit of working with your projects instead of someones else, which is always more boring.
It seems like most people, especially geeks, want to take the easy route and try get a job. Being self-employed or running a business isn't all that hard and it is much more rewarding, especially for a computer geek now in internet age.
Show examples. Show your hobby projects. Show sites that you've built and that currently are in use. Show contributions you've made to open source projects.
What you're looking for is a portfolio. They're common in any artistic arena such as photography, web design, hair styling and fashion.
You need to SHOW people what you have done, using examples relevant to what the potential employer would be interested in.
Also, just to make the HR people happy, get some certifications.
Learning HOW to think is more important than learning WHAT to think.
Evidence, evidence, evidence.
I don't work in the IT or compsci sectors, but I think there are a few general principles about how recruitment works that you might want to note.
You don't have formal educational qualifications. Obviously, that's a handicap. However, you're not in a field here where qualifications are a legal requirement (unlike, say, medicine or law), so it's not insurmountable.
Some employers still have a policy of requiring a degree from all applicants, but - personal view here -in many cases they're foolish to do so. In the current climate, a lot of bright people are choosing not to take on the expense and debt associated with a degree. I see a lot of employers insisting "graduates only" who are achieving little except needlessly inflating the starting salary they need to offer (though by less than in the past - the graduate premium isn't what it was).
I've done a fair old bit of recruitment over the last decade or so and what a sensible employer will be looking for - when recruiting people for their "first proper job" - can be distilled down to: a degree of committment (as in, ability to stick at something which is difficult and takes time), reasonable interpersonal skills and, where appropriate, technical competence.
Interpersonal skills you'll need to demonstrate at interview (and by writing a half-way competent CV and application form). The ability to stick with something and technical competence might traditionally be demonstrated - to a basic level - by the fact that the applicant has both had the perserverence and the ability necessary to earn a degree (though with degrees as debased as they are these days, it's increasingly difficult to use this as a firm indicator).
So without a degree, you will need to have independent evidence of committment and technical ability. You've done some freelance projects - that's good. The companies you did them for may have gone under, but you kept your own work, right? Right? And maybe if those companies aren't around any more, there's less of an issue in sharing the work you did for them as part of your application?
In addition, if you've done any non-technical work - even just office admin and stuff - that's also good and worth including in your job applications - particularly if you can get a reference. It shows you can get along with people in an office environment on a day to day basis, turn up for work on time, follow basic codes of conduct and so on (which is something that a surprising number of people - even graduates - in some fields especially graduates - fail at). Don't under-estimate this one. As a recruiter, in 95% of cases, I'd rather see a few summers spent temping in a "serious" workplace on a CV than some glamorous, expensive (and usually irrelevant) piece of gap-year do-goodery.
Remember, being at a technical disadvantage, you'll need to use hard facts to sell yourself so far as possible. Part of TFS reads like a "personal statement" from a CV. Saying stuff like "I'm personable and self-motivated" is all well and good, but it won't get you a job. You'll need concrete evidence to demonstrate your skills and your ability to stick with a task. So yeah, I hope you kept all that evidence of your previous work.
Portfolio, portfolio, portfolio.
Don't let a piece a paper show a potential employee that you have the skills on just that, paper, actually show them what you're capable of. Build a portfolio of work, showcasing your best products and sell yourself through that.
If an employeer doesn't respect or look to the portfolio of a potential employee in that line of work, truth be told they probably aren't worth working for.
I am a self-taught geek, similar to you. I was a construction worker, and I wanted to change careers. I don't have a college degree. I built my skills by taking a few night classes at a local community college and by spending a couple of hours a night (or more), every night, working in my home lab, doing networking/IT kinds of things, and writing code. Next, I got a job doing some IT work for a construction company, on a project where a lot of construction knowledge was needed.
After I got to the point where I felt comfortable with my skills, I put together a resume and got an interview with a small IT consulting company. I offered the company the following deal: Pay me whatever you want for 90 days. If at the end of that time I have demonstrated sufficient ability I want a raise to market rates. If not, I will move on, no hard feelings. Within 45 days, I got the raise. Within 3-4 years, I was making 100k a year.