As I mentioned in an earlier post, I'm not a big believer in extensive lists of technical resume writing do's and don'ts. Every career is different, and every technical resume writing service brings a unique approach to writing a technical resume. So, with that said, I'd like to discuss a few approaches that I've found useful in formatting technology resumes.
Viewing entries tagged
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.
In my Technical Resume Writing Service, I often work with Technical Professionals - up to the IT Manager, IT Director, and CIO level - who feel uncomfortable discussing achievements. So the process of writing a technical resume often involves helping my clients clearly distinguish cause and effect, to be able to effectively highlight the real achievements that are the core of a strong technical resume. One valuable approach to writing the technical resume for IT professionals - up to senior technology executives - is the CAR format.
If you're an IT Director or CIO, and you've been searching the web to find information on writing a Technical Resume, you've no doubt seen many opinions from the many fine Technical Resume Writers who post regularly. I think that's a great thing, personally. I don't believe in one-size-fits all approaches writing a Technical Resume. I think that different clients need to explore the options, and pick the Technical Resume Service that best meets their needs.
Everything in the technical resume should support your "value proposition" - the things that set you apart from your competition. In my previous post I discussed the critical importance of the professional profile in writing a strong technical resume. Today, I'd like to expand on that.
Technology Resumes for Project Management Professionals present a unique set of challenges, particularly if you've been in a role with multiple simultaneous projects, or a number of (relatively) short-term initiatives. The tendency to want to include everything is understandable - but can be a strategic mistake. As an IT Resume Writer, I've had client resumes cross my desk that are 6, 8, or even 10 pages long - and that's just not a good idea.
Technical Core Competencies are an absolutely critical element in a solid, interview winning IT or Engineering resume. But - as with all elements of a strong resume - it's important to have a clear, definite strategy in the approach you choose to highlight these technical strengths.
It is critical to ensure that you demonstrate the necessary technical depth. But it's equally important to present technical skills in a way that doesn't overwhelm the reader.
One of the most common problems I see in my client's initial technical resumes is a lack of clear structure. Often, my clients have great information throughout the resume, but it's in unconnected nuggets that can be hard to mine for critical information. Duties and accomplishments are often mixed and formatting may not give a clear vision of which is which.