Viewing entries tagged
IT Director Resume
The very few, specialized, IT Resume Writers like myself have access to some very interesting - and sometimes disturbing - trends within the IT industry.
One that I've been hearing a lot of lately, is IT professionals who may career the IT Manager title, but who's job description can ofter be little more than a senior system administrator.
When prospective clients call me, they're often frustrated - frustrated in their current job and frustrated with the challenges of the job search.
After all, if a prospective client loved their current job, they wouldn't email me. That's why, in my initial conversation with a prospective client, I always want to get a strong feel for what's going on in their current job - what prompted them to pick up the phone - and what their concerns are about the job search.
As an IT Executive Resume Writer, one challenge my clients often face is the maze of titles that can be used to define "top-of-the-food-chain" IT executives.
Shakespeare said "What's in a name? that which we call a rose by any other name would smell as sweet."
As a professional IT Resume Writer, a significant part of my job is keeping my finger on the pulse of technology - and technology hiring - trends. That's why I found this article on ZDNet to be extremely valuable.
It may be a cliché, but time really is money.
And the time spent on an extended job search incurs significant costs - in lost or lessened revenue, in missed opportunities, and in generalized stress.
How to Write a Job-Winning IT Director or IT Manager Resume When Transitioning from a Technical Hands-On Role
I've seen a good deal of interest in my earlier post on Technical Resume Strategies for New IT Leaders. I'd therefore like to expand on that post, and give more detail on technical resume best practices for the critical transition points in your IT career. Today, I'll address the transition from a hands-on role to IT Manager or IT Director. One very common issue I see in the resumes that cross my desk is the tendency to simply update an existing resume with each new job. That can work when the jobs are relatively similar. However,...
There's much advice on the net - good and less good - on creating the "perfect resume."
I don't, personally, believe that there is a "perfect" resume. I believe that there are a number of approaches that can work effectively for any strong candidate.
The CAR - Challenge Action Results - approach makes it far easier to see the major themes of your career - rather than getting in lost in the weeds.
In an earlier post, I discussed the value of the CAR - Challenge Action Result Resume format.
There are several strategies to ensure that your resume value proposition is absolutely clear to the reader. I discussed that one reason an IT leadership resume may not get the right calls back is that there may be an ineffective headline - or none at all. Today, I'd like to address the resume headline or branding statement. Here are a couple of options for a headline that are direct, and clearly let the hiring authority know your next career step and your current career level.
One common issue that I hear from clients in my technical resume writing service is that my clients are getting calls back from their resume - but not the right kind of calls.
Usually, this means that a client - an IT Manager or even Director - is getting calls that would be more appropriate for a hands-on technologist.
The first question I ask clients in my technical resume writing service is simple.
What do you do better?
What are your differentiators? What do you differently? What do you bring to the table, that your competition may not?
Needless to say, in my technical resume writing service, I see a LOT of resumes - as I did when I was recruiting. I've discussed a number of major issues to help build powerful, targeted technical resumes in previous blogs, and I'll continue to in the future. But today, I'm going to mention something that may seem minor - but can make a significant difference in ensuring that your resume is easily found by a hiring authority.
Technical resumes may seem pretty dry...
Resumes - particularly technically resumes - can seem like rather dry documents. But however dry the resume may appear, the resume has to tell a clear, compelling story. That is, ideally, a story of clear, consistent career progress - leading to the irresistible conclusion for the hiring authority that "I need to interview this person to fill a critical position."
I recently had a resume cross my desk from a prospective client. My process is always to review the existing resume thoroughly, to see what works - and what may need to be improved.
My first thought was that the resume was pretty solid - I could definitely see areas that I could make stronger, but on the whole, it was pretty good.
The greatest change in the format, strategy, and approach of your technical resume comes at the transition from primarily hands-on work to a leadership role - often at the IT Manager or IT Director role. In writing a technical resume at this critical junction, it's important to realize that the resume for an IT Manager or IT Director role contains different types of information than in a more hands-on role. The "look and feel" of the resume for a technical leadership resume will also be significantly different. Here a few ideas I've used successfully in my technical resume writing service.