In my previous post, I discussed reasons to include enough information in your technology resume to demonstrate what you can do to solve the hiring authority's problem. The challenge, of course, is knowing what "enough" is. While some technical professionals err too much on the side of brevity to provide a clear picture of who they are or what they can do in their technical resume, others go to the opposite extreme.

Technical professionals are, by their very nature, thorough people. What is a small detail in many professions can, for IT or engineering, mean the difference between project success or failure.

As I've mentioned previously, I'm a believer in completeness in the technical resume. But that completeness must be tempered with respect for the hiring authority's time.

I have had resumes cross my desk that are 5 (or more) pages long, clocking in at 2500 or even 3000 words. Speaking as a former recruiter, that level of detail is overwhelming. So while I don't believe in resume rules, in writing a technical resume, it's rare that I'd produce a resume of more than 3 pages.

So think carefully about what you're going to include. In my technical resume writing service, in each IT resume project, I ask myself whether each detail is critical, and supports my client's goals. You should too.

Comment