Over a million developers have joined DZone.

The Worst Resume of the Week: Template of Doom

DZone's Guide to

The Worst Resume of the Week: Template of Doom

Resume templates can cause problems for many users. Keep these tips in mind before considering a template.

· Agile Zone
Free Resource

See how three solutions work together to help your teams have the tools they need to deliver quality software quickly. Brought to you in partnership with CA Technologies

It's not surprising to see the increased use of resume templates by technology professionals, as the industry avoids the need for reinventing the wheel by creating new frameworks and templates. I would imagine that perhaps 50% of the resumes I see in my recruiting work and my resume business were built using a template. 

So far I have never used any templates when writing resumes for Resume Raiders, but I understand the temptation. The problem with resume templates should be obvious to anyone who has been forced into using a framework/language/tool that was unfit for the task at hand. The resume template has to somehow work with the material that is to be showcased - otherwise the resulting document will have issues.

Our inaugural Worst Resume of the Week candidate, Template of Doom, is a fine example of a template gone wrong.

Image title

This is a relatively common two-column template that I see frequently used by developers and designers with varying levels of success. I've deleted the actual content to protect the guilty party, but does anyone see the problem?

Mistake #1

The person who selected this resume surely had the option to include some text fields or other blocks in the left column, but didn't take advantage. In this case, one can only surmise that the template user simply liked the color red. Unfortunately, now a one page resume has turned into a three page resume because most of the page is just a block of red. Image title

A two-column resume can work for some people, but that format is rarely effective with for resumes longer than one page. This user included name, contact info, and links (GitHub, LinkedIn, blog) in the marked white box. The space below that box could have been used for relatively short bits of information, which might include education, certifications, or technical skills. 

If you choose to go with two columns, make sure you actually need (and will use) the second column - otherwise it looks ridiculous.

Mistake #2

The content has been deleted for obvious reasons, but this resume included the words "I/me/my"over 20 times. The use of first person is not generally recommended, but the repetitive use of first person starts to sound like someone taking full responsibility for tasks that may have been a team effort. 

Use the first person, but avoid the pronoun. "I developed a..." becomes "Developed a...", and so on.

Mistake #3

Most templates include default section headings, and it's assumed almost all users will want to include details for common default sections such as Experience or Skills. The issue is when the default headings are kept from the template but don't apply to the individual user's career history. 

In these situations the headings may actually highlight an area of weakness instead of a strength. Job seekers without certifications, formalized education, or volunteer experience are better off deleting those sections entirely instead of listing "NONE" or trying to force an entry that may shine a light on a shortcoming. Just because a template includes a section doesn't mean you should list that section on your resume.

Many templates will also include an objective section, which is now considered a bit passé. 


Use templates with caution. Two-column templates are almost exclusively beneficial to single page resumes. Avoid using first person pronouns. Don't think you need to keep every section recommended by the template.

Discover how TDM Is Essential To Achieving Quality At Speed For Agile, DevOps, And Continuous Delivery. Brought to you in partnership with CA Technologies

resume tools ,resume ,career advice

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}