There's a lot of discussion of the role that keywords play in creating an effective, powerful, and compelling CIO resume. Many IT resume writers advise that keywords are absolutely necessary in any strong document—and that a CIO resume without those magic keywords will doom your hopes of getting an interview.
I don't agree with that position, and I'd like to present a few thoughts on keywords, to help you build an effective strategy for your executive resume and job search.
We've all seen one. The CIO resume that leads with "27 years of experience" in the first line of the resume summary on page one.
On the surface, that seems like a great strategy. It's apparently clear, and seems to give a sense of career level. Also, many job postings do start with number of years required for the position – so, it seems reasonable to address the issue of experience directly, at the very beginning of the resume.
I was speaking with a client of mine yesterday, and we were discussing his unique value proposition - and his equally unique approach to technology leadership.
And he told me an interesting story (with all details changed to protect his privacy). He was recruited - by a large, US-based manufacturing firm headquartered in a major Midwest city - to lead a very low performing IT organization. His mandate, essentially, was to fire the entire team within a month, and rebuild from scratch.
I was talking with a good friend of mine yesterday, who just made a change from a job she really hated - to one she really loves.
That transition took some time - and we worked through many of the issues. But our conversation got me thinking. One of the biggest issues she was dealing with is a very common one - at every career level, up to C-level.
In that article, I focus on the need for today's transformational CIO to be bilingual - to communicate value to ensure enthusiastic stakeholder buyin - and to further ensure that IT is recognized as a value center, and not a cost center.
You don't become a CIO / CTO / CISO / CDO without being able to deal with stress.
At every stage of a technology career - from early days "in the trenches" to a leadership position in the boardroom, you've dealt with high pressure, mission critical initiatives - and major decisions that impact every aspect of the enterprise.
We're all driven by metrics these days. Whether it's cost, revenue, increase in market share, streamlined operations, or KPIs, numbers often seem to tell the story of success or failure.
That's why Executive Resumes Writers - myself included - work to dig out the quantifiable achievements to demonstrate our client's success.
It's a rare week that I don't see a blog post or article with the 3, 5, 7, or 10 things that a job seeker MUST or MUST NOT include on a resume.
There's one big problem with articles like this. They go on the assumption that every career is the same, and that there's an simple template - a cookie cutter approach - that works for every career, every resume, every job seeker.
In this series of blogs, I'm going to address the 3 most significant issues that I see in the IT resumes that cross my desk.
And I'll start at the top of the organization - with CIO and CTO resumes - and continue the series with IT Directors, IT Managers, and then address issues that I see in the resumes of "hands-on" IT professionals.
As a professional IT Resume Writer, I follow IT hiring trends very carefully - to ensure that I craft the best possible IT resume for my clients.
And there's some bad advice out there - advice that I see consistently. So I'd like to take a moment to discuss some of the things that you'll see - from the early stages of your due diligence finding a professional IT resume writer through the later stages of the job search.
A client of mine - a senior IT leader - asked me for counsel of he was asked during the interview process if he had written his own IT resume.
It was an interesting - and, I think, an important - question.
I've blogged a fair amount recently on the rapidly evolving role of the CIO - and it's a rare day that I don't see signs that that evolution is becoming, if anything, more rapid.
In just the last couple of days, I've found a couple of interesting stories.
Late last year, I wrote a couple of blogs on various CIO Career Suicide threats.
I'd like to continue that thread with another blog on something I see quite often in the initial CIO Resumes that cross my desk.