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.
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.
It seems innocent enough; after all, what does a little white lie on a resume hurt, especially if it’s about a piece of paper you never earned but said you did? Or if you claim to be proficient in certain technical skills when you actually just read an article about the subject in a journal, why does it matter if you won’t be using those skills, only managing people who do the real work? You might justify it by saying you’re just doing it to get in the door, and you’ll fix it later, or you swear you’ll learn the claimed skill as soon as you can.