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.
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.
We all know that technology has its own language, and technology executives are fluent in the jargon. However, fluency in techno-speak does not always translate to fluency in the language of resumes. While your resume needs keywords and some of that industry jargon to satisfy the electronic and techno-savvy reviewers, the HR recruiters who are often the first screeners need more than that. They need to see accomplishments, challenges/actions/results, and that you can relate to non-technology associates, too.