Stop Boring Employers with Your Resume

Imagine picking up and reading someone’s resume in which line after line all you’re reading is what the person does at their job day after day.

For instance, a sales person’s resume may read, ‘Made cold calls to create new business’. 

Would you be impressed or bored?


Would you read the entire resume or stop after just a few sentences?

Yes, you would be bored and have thrown the resume away in less than 15 seconds.

Well, this is exactly why your resume is not getting you the interviews you think you should be getting.

Stop boring employers with your resume!

Think of your resume as your professional marketing tool to inform hiring managers how great you are at your profession and most importantly can solve their problems.

So stop telling people what you do all day at work and instead tell people about your achievements!


So how do you go about telling people about your achievements?

Well, the formula that has always worked for me is…

Achievements = Action + Quantifiable Numbers

You want to start your sentences with your achievements as this keeps the reader engaged and interested in reading more.

You then want to tell the reader how you went about reaching those achievements by stating the action you took and anytime you can quantify your achievements the more you’ll stand out compared to your competition. 

For instance, let’s look back at the example above of a poorly constructed bullet point from a sales person’s resume, ‘Made cold calls to create new business’.

This sentence would be better stated as, ‘Increased new business accounts by 10% through establishing new partnerships.’ 

‘Increased’ is your achievement, establishing partnerships is your action and obviously 10% is your quanitfiuable number.

Here’s another example of a poorly vs. well-constructed sentence…

This time we’ll use a project manager’s resume.

Poorly constructed would be, ‘Held weekly team meetings’

Now isn’t that impressive….NO! That is just another example of someone who is telling you what they do…nobody cares!

Instead a better well constructed sentence would read…

‘Lead a team of 50 resources in delivering IT projects for the client that decreased their operational costs by 15% while increasing the end users experience’. 

Here’s another example that would be better received by the reader...

‘Created and delivered weekly reports to executive management that allowed the client to make informed decisions regarding risks and issues to their projects.’

As you can see there is a clear difference between simply telling someone what you do at your job versus detailing your achievements.

Employers Hire Services/Outcomes

Another way to get your mind to come around to this framework is the following…

Employers are looking to hire people who are able to provide exceptional services and deliver positive outcomes!

Think of something you have bought for yourself in your life like a car. You didn’t buy that minivan because it takes you from point A to point B as many cars can do that. Instead you bought the outcome it provides which is it has enough seating to fit your entire family. 

Another example is a wedding planner. You don't hire a wedding planner to order flowers, hire a DJ or secure the reception venue. No, instead you hire that person to provide you the postive outcome of a stress free and beautiful wedding day!

Therefore if you want an employer to be interested in you based off of reading your resume you must be able to convey you can provide exceptional services and/or deliver positive outcomes.


  • 1
    Stop telling employers what you do at work.
  • 2
    Instead convey the services/outcomes you can deliver for an employer.
  • 3
    Articulate your services/outcomes through achievements, actions and quantifiable numbers. 

Why do you think your resume is not getting you the interviews you want?

Sign up to the mailing list so you can receive strategies and courses to help you write a resume that demonstrates and quantifies your achievements!

Leave a Reply 0 comments

Leave a Reply: