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.

Much advice on leadership resumes encourages an extremely streamlined approach to describing career highlights. In this blog, I'd like to detail why I believe that a technical leadership resume - for a Director / VP of IT, or a CIO / CTO - often requires more depth and detail than those for other executives.

Non of this, of course, is meant in any way to lessen the importance or impact of the achievements of VP of Sales, or any other business leader. My goal is simply to explain why I believe that resumes for IT leaders need more detail, and more depth, and a somewhat different strategic approach to enable the hiring committee to make an informed choice. In many fields of business endeavor, it's the result that counts. A VP of Sales is mandated to grow sales - and while a brief discussion of strategy and approach will help make it clear to the hiring authority why he (or she) is the best fit candidate, people are looking at the numbers, at the results.

In IT, it's different.

The results are critical - that's why I focus on hard, quantifiable results in every project I deliver. But for technology, it's not only the achievement. It's the "how?" of that achievements. What technologies were used? What strategies were implemented to contain costs. What is the overall approach that a candidate takes to ensuring that IT is more than just a cost center?

That's why I believe in writing technical leadership resumes that present these crucial career details. Don't get me wrong. I don't write 5-page, 3000 word novels. My resumes are clear, clean, and tight.

But I do include enough detail to clearly differentiate my clients from the competition. Does it work? Yes it does.

Comment