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?"
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.
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.
Guilty!
I hate marketing stuff, I hate business stuff, and I really hate "networking" .. what I love is building software. I'm happy to be able to come in, do my thing, and let someone else worry about all that other shit. Long as I'm reasonably well treated and paid... I'm happy being a wage slave.
I suspect the same is true of most geeks. As a community we are not known for wanting to wear suits, speak in buzzwords, work with excel and powerpoint, etc. Some pull it off, and some even enjoy it, but I think for the most part we like to be in the background doing our thing while the "suits" figure out how to make money from it.
Most of this is business advice, not Drupal advice, but it all goes hand-in-hand. Make a name for yourself. Be good at what you do. Manage expectations with clients. Get a brochure and business cards. Write a blog; I wrote a book on Drupal which has been amazing for business.
This economy is a bitch. Good luck if you start your own thing.
sysadmins and parents of newborns get the same amount of sleep.
What do all these books have in common?
Oh yeah, they all STARTED with a big-ass pile of cash that they could fritter away on risk.
Like the recent Republican debate - Gingrich talks about Bill Gates being a "high school dropout" who founded Microsoft, but he fails to mention that Gates was the prep-schooled son of upper 0.5%'ers who had a ton of mommy and daddy's money to pay Paul Allen (the real programming genius of the company) and later to front in order to buy 86-DOS from Seattle Computer.
Funny how that all tends to work out only for those who already inherited wealth.
I working in IT now despite not having any related qualifications on paper at the moment. I'm working towards getting those credentials though. I got in through networking and getting my PMP (project management professional) certification. I'm currently working towards becoming an enterprise architect (certified).
A couple of key things to getting in the door (past HR):
1) HR people are all about risk reduction. HR staff don't get rewarded for hiring good staff, but they do get fired for hiring too many bad ones. From an HR perspective ideally you have 1) credentials (including degrees) 2) a track record of performance 3) come recommended by someone they know (someone in the company will do). Typically anyone having all 3 won't turn out to be a bad hire. They don't hire for intelligence and capability, they are looking to be able to cover their asses in case you turn out to suck. Whatever you do don't lie on your resume, if even the smallest thing is determined to be untrue HR will drop you like a hot potato.
Keeping the above in mind most applicants have some credentials (1), some experience (2) and no internal recommendation (3).
To get credentials spend the money and get some certifications in the area you work in or others related. Pick credentials in areas where you already know the material and have had some experience as well as frequently occurring as a requirement in the type of jobs that interest you, buy the prep books and study and you can be certified inside of a month or two for $300-1000. You can list credentials you are "working towards" as well (helps with the keyword search).
2) Networking (not the computer kind), If you haven't started building a network (of people) start now. Set the objective to add 1-2 people to your network every week (during your job search) once you're employed continue to do this 1-2 people per month. Use a tool like Linked in. Once you get about 30 or more people in your Linked in Network it becomes useful in that you can find someone you can be introduced to that may be able to help.
Key concept in networking: its about informal meetings 10-15 min, at the convenience of the person you want to talk to, to do these things:
1) give something back (listen, or share something that interests them).
2) create the opportunity to meet other people in the area you want to work in
3) learn about the industry you want to work in.
Finding an opening or opportunity and reference from the inside are not the primary objective.
By giving I mean: treat the person with respect like a person, only ask them for what they can give you (aka do not ever ask for a job), ask them for advice, ask them how they got to where they are, and make them feel like you care and are listening (this is the give back).
Think about it from the networking contacts side. Imagine you're the contact: A colleague (Bob) you trust emails you and writes I'd like to introduce you to an interesting guy (you), he's trying to learn about our industry and find out what he need s to know to be able to fit in. A day latter you get a polite email from the guy asking if you'd be willing to share your expertise and advice in a 15 min meeting at a coffee place and time convenient to you or to talk to you by phone for 10-15 min. You agree to meet because 1) you trust Bob, 2) you're curious 3) you have 15 min 4) its convenient 5) it beats working ;).
In the meeting you talk about your own success and answer a few interesting questions and generally feel good about your own success. You leave the meeting feeling like you met an interesting person with good questions (that you could answer). The person emails you a day or two later and asks a follow up question or two and if you have any suggestions of people you know in the industry that would be good to talk to. You liked the guy so you offer to introduce him to Keith and Sharol two of your suppliers. You also agree to join his network on Linked in.
So now how does a network translate into a
----- "Profanity is the one language that all programmers understand."