Comment: Wrong path (Score 1) 441
For me it was easy. I got my degrees in philosophy and psychology. They're much more useful in job interviews that boring old technical information. My technical knowledge came from years of DIY projects, some open source when that became cool, using skills as lame as writing excel and access projects at jobs, taking dozens of classes on my own time for a CS degree that never materialized, etc.
Seriously, the amount of technical information you have, starting out, is pretty moot. There's not a huge difference you can tell from looking at your academic list of knowledge other than a basic skillset. Most grads are the same, unless you just finished your PhD from MIT and hold 12 patents.
Psychological jokes aside, I just focus on pacing, leading, and manipulating the interviewer to wanting to hire me. How long I've been working with what tool or language is irrelevent if I can convince them I can learn anything in two weeks. I don't need to be able to write the greatest data structure in the world if I can convince them of the business reason why you would or wouldn't want one and what the affect is on the bottom line.
Of course, good or bad, none of it matter if you can't even get a technical interview with a human in the first place. I don't know if it was mentioned by others, but I went through contracting companies originally. They do all the work of getting the interview, and I just need to get the suit, tie, 37 pieces of flair, and a winning smile.
After that point, most everything is word of mouth and "social networking" whatever the hell that is. IT seems to luckily constantly churn, so I just keep in touch with those who can give me a job (or recommend me to a boss) and return the favor.
I haven't had to apply or interview for a gig in years that I didn't already have the job going in.