The Level System
How to write impact bullet points that place you in the top 1% of CVs
Why does this system work?
After analyzing and rewriting more than 1,000 CVs, I developed the Level System. It's not just a clear way to evaluate each bullet point on a CV: it's also a simple checklist for writing bullet points that convert.
Each level (1-5) is a step where you ask yourself a question. These questions will help you discover what you need to include. The goal is to rewrite each of your bullet points to Level 5, which represents the top 1% of CVs.
What did I work on?
It's a simple question, but more complex than it seems. You need to decide what to write about. The easiest way is to use a role profile. As a rule of thumb, you should write about each of the individual responsibilities present in your job description.
"Tested a web-based ticket management application."
💡 The only information here is that we tested something and what that something was.
- Don't use personal pronouns
- Write everything in past tense
- Focus the story on what you have already achieved
How did I do it?
Now the real work begins. This question helps you focus on the specific tasks involved in your achievement.
"Evaluated a web-based ticket management application with unit tests and end-to-end (e2e) tests."
💡 At Level 1, the recruiter only had a vague idea of "doing some testing". Now they know you have experience with both unit and e2e testing.
- Include abbreviations in parentheses, e.g., "end-to-end (e2e)"
- Recruiters tend to be less technical and may not understand abbreviations
- Both the full spelling and abbreviations can be used by recruiters to filter CVs
What tools did I use?
This is an essential question, especially for technical roles where tools matter. Software engineers: show your toolbox! 🔨
"Evaluated a web-based ticket management application in TypeScript/Node.js, using Jest for unit testing and Cypress for end-to-end (e2e) testing."
💡 Now you provide recruiters with a clear idea of your skill set and tech stack.
- Add all types of tools involved in the task, even if they are secondary
- Provide general context of the environment and programming language
- Give the hiring manager the complete picture
What method did I follow?
This is where you score extra points with recruiters. This question will help you talk about your understanding of key methodologies, frameworks, theories, or processes involved in your delivery.
"Implemented Test-Driven Development (TDD) methodologies to evaluate a web-based ticket management application in TypeScript/Node.js, using Jest for unit testing and Cypress for e2e testing, achieving 89% test coverage."
💡 Your potential employer probably employs such methodologies. The hiring manager is probably the one in charge of implementing these frameworks. Show them you care.
- Even tasks that seem simple are based on some theory
- If you sell: mention "SPIN selling" or "consultative selling"
- If you present: talk about "storytelling techniques"
What was the result?
We're almost there! This is another crucial step that will differentiate you from most of your competition. Show your real impact and that you care enough to measure and report it.
"Implemented TDD methodologies to evaluate a web-based ticket management application in TypeScript/Node.js, using Jest for unit testing and Cypress for e2e testing, achieving 89% test coverage and a 3% bug escape rate."
💡 This places you above 99% of CVs in terms of quality. It provides the reviewer with a clear idea of your real impact.
- If you only use one metric, select the most important one
- Add metrics even if they are not "very strong"
- Hiring managers value more that you are results-oriented than the actual performance
That's it!
Repeat these five steps for each bullet point in this way, then compare your new CV with the previous one. The improvement should be obvious to you. This means it will also be obvious to recruiters.
In my experience, this should place you above 99% of CVs in terms of quality.
Frequently Asked Questions
Answers to the most common questions about bullet points
How long can a bullet point be? Is more than 1 line okay?
2-3 lines are acceptable for a bullet point, as long as: (1) It's clearly structured, with easy-to-read syntax. (2) It's well-paced, allowing the reader to easily digest each phrase. (3) It's not inflated with filler words that add no value. It's about readability more than pure length!
What if I don't have metrics/measurements to share?
Metrics are a plus, not a requirement, however they make a difference during CV screening. The more precise they are, the more impactful your bullet points will be, and the better impression you'll make on recruiters.
Can I use estimates for metrics/measurements?
Recruiters and hiring managers care more about the fact that you measured your impact, rather than the actual number. The idea is to show that you were aware of your impact and measured it realistically. It's okay to use your best (honest) estimate, as long as you can justify it during an interview.
What if my impact can't be quantified with a number?
Some achievements are not quantifiable. For these, it's better to use a "qualitative" measurement. For example: "...Did X, which received overwhelmingly positive feedback from my peers." Where possible, numbers are better because they have a stronger psychological impact on the reader.
Can I use tables or text boxes instead of bullet points?
This would be a big mistake. Tables prevent many ATS from parsing the data accurately. That can result in automatic rejections or hiding your profile from searches.
Ready to improve your CV?
Apply the Level System to each bullet point in your CV and watch your interviews multiply.