← All guides

Best practices

Common Achievement Writing Mistakes

After enough resumes, the mistakes start repeating. Here are the ones that do the most damage, and what fixing each one looks like.

Vagueness dressed as modesty

The most common mistake by far. "Improved team efficiency" could describe anyone in any job in any decade. The fix is always the same three questions: what improved, by how much, and how?

The original survives none of those questions. The rewrite answers all three before anyone has to ask.

The responsibility instead of the result

Close behind, and the single most common thing early testers get wrong when they first fill a vault. "Responsible for managing the marketing budget" describes the chair you sat in. What a reader wants is what happened because you sat in it.

Same job, entirely different sentence. A quick test: if the line would still be true on your last day, having accomplished nothing, it is a responsibility, not an achievement.

The missing so-what

"Migrated the database to PostgreSQL" is a fact in search of a point. Migrations, launches, and rewrites only matter for what they made possible, so say it.

Weak verbs and crowded bullets

Helped with, assisted in, was part of. Each one quietly forfeits credit you earned. If you led it, write led. If you built it, write built.

And when one bullet contains three accomplishments ("improved sales, trained new hires, and rebuilt the CRM"), it is not one strong achievement, it is three starved ones. Split them and feed each its own metric.

Two subtler ones

Match the technical depth to the audience. A hiring VP does not need your service mesh named; they need "handled 10x the users at 40% lower infrastructure cost." Save the architecture for the interview, where someone will actually ask.

And do not let hard skills crowd out everything else. Mentoring, stakeholder wrangling, and unglamorous cross-team diplomacy read as senior, because they are. Most people under-record exactly this work, because it never produced a ticket.

The mistakes nobody warns you about

Two more show up constantly and rarely get named. The first is ordering: strongest achievement first, always. Readers spend seconds per role, and burying the best line under three routine ones means it may as well not exist.

The second is staleness. A bullet written the month you shipped something says "launching next quarter." Read two years later it reads as a promise nobody kept. Anything written in future or in-progress tense needs revisiting once the outcome is known, which is the entire argument for keeping achievements somewhere permanent instead of rewriting them from memory each time you job hunt.

A five-minute audit

Run every bullet past this list. Any line failing two or more is worth rewriting before you send anything.

• Does it name a result, not a duty?
• Is there a number, a range, or an honest estimate?
• Does it say what you did to cause the result?
• Is the verb the strongest one that is still true?
• Could you defend every claim in it, out loud, under follow-up questions?
• Is it one achievement, not three?