Slashdot Mirror
Ask Slashdot: Re-Entering the Job Market As a Software Engineer?
First time accepted submitter martypantsROK writes "It's been over 15 years since my main job was a software engineer. Since then I have held positions as a Sales Engineer, then spent a few years actually doing sales as a sales rep (and found I hated it) and then got into teaching. I am still a teacher but I want to really get back into writing code for a living. In the past couple of years I've done a great deal of Javascript, PHP, Ajax, and Java, including some Android apps. So here's the question: How likely would I be to actually get a job writing code? Is continual experience in the field a must, or can a job candidate demonstrate enough current relevance and experience (minus an actual job) with a multi-year hiatus from software development jobs? I'll add, if you haven't already done the math, that I'm over 50 years old."
At 34 I've re-entered the job market myself after giving my own business a shot and I landed a job as CTO of a start-up game company. We're developing a couple of games now (one while will be in beta tomorrow) and when I look for programmers, I could care less about a space in employment as long as they can demonstrate the skills needed for the job.
I'm 63, I still love to code and am quite good at it, and I just got hired away from my current company at a significant pay increase. If coding is stressful, then you're probably not cut out for it or you're doing it wrong. Coding should be fun.
I was in IT for 24 years, starting in 1985; worked for a lot of large companies and was highly sought after. Following a typical vector, asm, C, C++, VB. .NET, T-SQL, PL/SQL, JSP; managed some sizeable projects for many years, never stopped coding. Actually I think I'm an excellent coder. Reliable. Then, job was outsourced in mid-2009 and I, stupidly, partly because I had hardly ever looked for work (always came to me), just took some time off; first big vaca in decades. Error! Well, that was it. Lots of bites on Monster, etc., but between not currently employed and as soon as they did some math, no call backs. Oh yeah, one, I was yelled at. I'm > 60. So, now I have to change my field to paralegal. Hopefully, that will be a bit better; who knows. All I can say is, give a job hunt a whirl but after 6+ months of rejections, start rethinking. Grim news. (and of course 50 is not >60; >60 is the kiss of death, at least for me.
The best DBA I know was a fellow from Florida named Keith Grey who STARTED his tech career when he was in his fourties. He learned a little database and supported it for a small company, learned Oracle, enhanced the prototypes I'd written for them using Oracle a year earlier, and just kept going from there.
He's now one of the most experienced and skilled DBAs I know, riding herd over a clustered Oracle RAC installation with multiple data warehouses hanging from the main systems.
In other words, it's never too late to start a new career, much less resume an old one. The question is whether you have the skills, the dedication, and the willingness to learn it'll take to succeed. Personally, I'd much rather recommend someone with the "right attitude" and a background in business for a tech job than any of the impatient, inexperienced hot-shot kids whose resumes crossed my table over the past few years.
I do not fail; I succeed at finding out what does not work.
HR will never pass your résumé up to the person who can actually appreciate your experience and knowledge.
Any shop that has let HR insert themselves into the hiring process like that is pretty much doomed. Avoid at all costs.
Well, when the company gets beyond about 50 employees, that "Just happens". It sucks big time; but every Head Hunter I have spoken with has lamented the "Checklist" type of HR résumé-culling.
It's almost enough to make you want to stuff your résumé full of impossible experience, like many of the résumés of particularly Chinese "engineers", where it seems like the vast majority will list 30 years-worth of experience on every high-level engineering project in China they can find a reference to on the internet, and then being of an age where they would have started to work 10 years before they were born, knowing full well that there is absolutely no way to verify any of their claims. I don't want to sound racist (I most assuredly am not!); but I have seen some pretty laughable engineering-candidate résumés come across my desk, and it seems like Chinese engineering candidates seem particularly inclined to "pad" their experience (and I would suspect their schooling in some cases, too).
So, you might give that a shot, just to get past the HR gatekeeper. Then, when you get to actually talk with the person who will be your new boss, be prepared to SHOW them what you can do, and get off the subject of specifics in your résumé.
I aced an embedded developer interview a few years ago by taking out a sample of a particularly compact and component-dense product I designed the hardware and software for, and tossing it on my (future boss') desk, and saying, literally "Any Questions?"
The moral of the story is, if you can get past the HR droids, you can usually demonstrate that you have the skills. It's just getting to that point that is soooooo difficult!