For too long, the CIO was seen as the 'junior partner' in the C-suite—the nuts and bolts guy who kept everything running, but didn't have a lot of input into business strategy—and who, too often, wasn't taken terribly seriously by the other members of the executive team. Sure, the title was CIO. But too often, the CIO was still asked to get the AV running for a presentation—as though he or she was still a technical resource.
Happily, that's changed to a large degree…
There's a lot of discussion of the role that keywords play in creating effective, powerful, compelling executive resumes. Many resume writers advise that keywords are absolutely necessary in any strong document—and that executive resumes 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 them. The executive resumes that lead 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.
IT Careers are evolving rapidly. For the first time in a decade, I'm hearing about "talent wars." And - from what I'm hearing from my own resume and coaching clients - the demand for IT talent is continuing to increase.
That's providing IT professionals with a range of options that we haven't seen for several years - and one of those options is remote work.
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.
The news on CIO transformation continues to be very positive.
Gone, it seems, are the days when every morning I'd see headlines on "the death of the CIO," or the "war between the CIO and the CMO." These days - I'm very happy to see that the technology journalism community has caught up with reality.
There's a lot that I like in this interview - Mr. Moore has some great points on the need for the CIO to balance the three seemingly incompatible roles of visionary, pragmatist, and conservative. I think that's an excellent way to define the (seemingly) incompatible types of leadership that a CIO needs to deliver.
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.
I've blogged on this topic before - but I think that it's important - do to the amount of misinformation you'll find on the web.
It's a rare week that I don't see a career "expert" suggesting customizing IT Resumes for every job you apply for.