As a professional resume writer, there are some issues that I see over and over again in the initial client IT resumes that cross my desk.
One of the most common is to see every job described in an almost identical number of words, the same number of bullets, the same visual space on the page - whether that job is current, or was a decade and a half ago.
As one of the few specialized IT Resume Writers in the careers industry, I see a number of common problems in the initial IT resumes my clients send me.
One of the most common of these is a resume that has grown - without any real change in strategy or direction - for my client's entire career.
The CAR - Challenge Action Results - approach makes it far easier to see the major themes of your career - rather than getting in lost in the weeds.
In an earlier post, I discussed the value of the CAR - Challenge Action Result Resume format.
As with so many resume issues, there are a number of opinions on whether or not to include hobbies and interests in a technical leadership resume.
Those opinions range from "absolutely not, under no circumstances, never!" to "sure!"
One common issue that I hear from clients in my technical resume writing service is that my clients are getting calls back from their resume - but not the right kind of calls.
Usually, this means that a client - an IT Manager or even Director - is getting calls that would be more appropriate for a hands-on technologist.
The first question I ask clients in my technical resume writing service is simple.
What do you do better?
What are your differentiators? What do you differently? What do you bring to the table, that your competition may not?
Technical resumes may seem pretty dry...
Resumes - particularly technically resumes - can seem like rather dry documents. But however dry the resume may appear, the resume has to tell a clear, compelling story. That is, ideally, a story of clear, consistent career progress - leading to the irresistible conclusion for the hiring authority that "I need to interview this person to fill a critical position."
Should I Tailor my Technical Resume for Every Job?
In my technical resume service, I'm frequently asked this question. As with many technical resume issues, there are a range of opinions. Several authoritative websites suggest that tailoring your resume for every job is a good idea.
One of the most common misconceptions about resumes in general - and technical resumes in particular - is the question of length.
"But I Never Heard Back After I Submitted my Resume…"
Unfortunately, this is something that I hear constantly in my technical resume writing service. Applying online, or even in person, doesn't always lead to call back. Often you won't hear back after submitting your technical resume.
There's a lot of discussion about the most appropriate length for technology resumes for job seekers at all levels from hands-on to senior technology executives including IT Manager, IT Director, and CIO. This is the first of two blogs discussing technical resume length. In this post, I'll address the "less is more" approach to the technical resume - and the potential downsides to that.
Technical Resume Writing - Clarity is Key! I have to admit - I'd resisted the idea of blogging. But I'm really glad that I started this blog. I hope that it's of value to my clients - but in addition, I'm finding that blogging regularly is helping me to clarify the strategies and value that I use in my Technical Resume Service.