Sunday, March 12, 2006
Thoughts on Resumes and Interviewing...
Was thinking about something said (or at least hinted at) by a fellow blogger and figured I would expand upon it...
As far as resume building goes, I have the following five tips to share:
| | View blog reactionsAs far as resume building goes, I have the following five tips to share:
- Always attempt to work on projects on the money-making side of the company. Ideally, it is better to work for a company that acknowledges the contribution of IT folks not only in delivering "value" but in making money. It is actually better on one's resume to be a revenue generator which affords itself more opportunities to make more money. Have you ever noticed that having any of the big four insulting firms on one's resume seems to land jobs higher up the foodchain.
- You should always think of yourself as an independent consultant regardless if your position is permanent. You should change jobs often which increases visibility within an organization and allows you to put more stuff on your resume. Don't be caught redheaded with one years worth of experience twenty times.
- If you are an architect, you should blog. Headhunters nowadays when attempting to find candidates will use magical tools such as google to find folks. Blogging increases your findability.
- Pay attention to the research work by industry analysts. Yes, the vast majority of it is crap but it will teach you how to speak in the monotone that is loved by today's non-technical IT executives. Borrow some of the opening phrases and use them while interviewing and they will open lots of doors.
- Consider joining an industry standards body. I have joined the Java Community Process and am on two different JSRs. Of course, both died due to lawyers and we never really did any real work but it still goes on the resume and folks may ahh and oooh when they read it.
