Looking for work 03 Jan, 2005
Ah yes, a timely article for this time of year, via Damien Katz:
Hands up who’s quitting theirs in 2005?
OK, so where’s this coming from… Well, I’ve been with my current employer for some nine years now. For someone as wet behind the ears as me, that seems like a long time (I’m 32 and have worked for this lot since I left university at the age of almost 23 — only six years as a coder I hasten to add). There’s no such thing as a job for life, so speaking as someone who could be in the position of actually recruiting developers (if only the freeze that’s been in place since I was promoted to manager some three years ago was lifted), I’d pretty much require that candidates had some kind of experience beyond one employer (sixteen within a seven month period is probably pushing it though).
But how do you know who’s a good bet? How do you make that decision? Plenty is written about technical tests, the importance of the first interview, ya-da ya-da, but how do you know who’s good for you? Do you google people, check out their weblog if they have one, what?
Valid points as far as I’m concerned, and all raised as I considered my somewhat throw-away response to Robert Scoble’s post, Rob Fahrni is looking for a software development job in which Mr. Scoble says this:
Forget the resume. That won’t get you a job in today’s market. Your blog will, however.
I question whether that is for real in my response to his post, and there are plenty of other comments in there, so check it out. I’m really interested in this side of things, not just from the point of view from someone who would dearly love to be head-hunted ;-) A few fellow ’bloggers have secured new jobs since they started posting (Declan and Joe spring to mind), but just how useful is a ’blog / on-line presence in securing the next job or contract?