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 resume.
It was an interesting - and, I think, an important - question.
There are some hiring authorities - especially for lower level positions - who feel that a candidate must write his or her own CIO Resume.
I think, frankly, that that's nonsense.
An IT leader has a wide range of technical, strategic, tactical, leadership, and business skills.
But - for any leader - the chief among those many skills is the ability to delegate, to find the best resources to accomplish the myriad tasks involved in any major IT initiative.
A CIO who's writing code isn't much of a CIO. A CTO running cable is not spending his or her time very effectively.
And a CIO, CTO, or IT Director who writes his or her own IT Executive resume is wasting his or her time.
Sure, my clients are really smart people. They can read dozens of books and hundreds of blogs, and cobble together decent CIO resumes.
But that takes time. Time that can be better utilized to do their jobs. To increase efficiency. Deliver state-of-the-art development projects. Migrate major systems.
Because writing CIO resumes is a complex skill - one that I've honed over many years in my professions. Writing CIO resumes requires a deep knowledge of hiring trends and resume best practices - combined with the ability to effectively interview a client to get "under the hood" of his or her career and find the accomplishments that may be buried - but may provide the critical difference between getting an interview. And, well, not getting an interview.
So - in the unlikely event that a hiring authority asks one of my clients whether they wrote their own resume?
My counsel is simple. I suggest that they say that, as with any task, they did their due diligence, vetted the best possible professional.
And got back to doing their jobs.