Rewrite Your Tech Resume, Pt 2

This post was originally posted on the now-dead ProjectSherpa blog.

Welcome back for part 2 of our Rewrite Your Tech Resume series!

In part 1, we discussed avoiding skillz proliferation and the acronym wasteland. In this post, we’re covering something equally important: consistency.

Consistency is especially important on tech resumes because…

 

Attention to Detail
Even if you don’t know coding, you can tell that the above snippet is ugly. There are misspellings, variable names are not informative, there’s no consistency around use of braces, underscores or indentations, the sole comment provides no insight, error logging is not helpful. This snippet shows no attention to detail, lack of experience, and/or lack of care – all things you wouldn’t want to demonstrate on the job, or if you care at all about your work.

If your resume is riddled with misspellings, bad grammar, weird capitalizations, and lack of formatting, then who’s to say your on-the-job work, emails or programming or other, will look any better.

There’s no shortage of helpful sites on resume grammar – pick a few and follow the rules. Some of our own suggestions follow.

Stick to one verb tense. If your job description bullets mix between present and past tenses, you’re doing it wrong. Just stick with one tense.

Bad

  • Designed write-ups for migrating…
  • Implementing a new XML feed…

Good

  • Designed write-ups for migrating…
  • Implemented a new XML feed…

Do not end some bullets with a period, and others with nothing. If you want to finish each bullet with a period, do that, but be consistent.

Do not arbitrarily capitalize. Capitalize proper nouns and the first word of sentences (generally). This is a Very Bad example: I created stored Procedures, Tables, and Views for each Product. Also note that many resume purists suggest avoiding ‘I’ or any first-person references.

If you capitalize an acronym, make sure you capitalize it similarly throughout. For example, do not write ‘xml’ in one place and ‘XML’ in another.

For marks like ampersands, slashes, and dashes, decide when and why you want to use them, and stick to those rules.

Are your bullets all lined up and indented to the same place? Are your dates all formatted the same? Are your job titles and positions formatted similarly across your work history? If your resume has section headings, are they formatted similarly? Have you even read the damn thing yourself!?

One Comment

  1. Pingback: Rewrite Your Tech Resume, Pt 3 – That's a Big Idea

Leave a Reply

Your email address will not be published. Required fields are marked *