Trent at thesimpledollar.com writes:
Over the last month, I’ve helped three different readers polish their resumes as they look to make a major career shift. In each case, I noticed several problems crop up over and over again. These problems weren’t ones that would sink the person, but they did prevent that person from standing out from the crowd, and adding the problems together ended with a forgettable resume.
resume comparison
resume comparison (Photo credit: TheGoogly)

Here are ten things I would always do when writing a resume, regardless of the conventional wisdom about resumes.

1. One page only, period.
This often bothers some people. “I have tons of good things to write about,” they think, so they fill up their resume with six pages of good stuff with just a sprinkling of great stuff in there. Hot tip: it’s not the “good” stuff that will get you the job. The only stuff you want on your resume is the cream of the crop, and that cream will fit on one page. If it doesn’t, you’re not cutting out enough merely “good” stuff.

2. Write everything with active verbs.
Every bullet point on your resume should sound like you took some sort of decisive action, and the more action-oriented, the better. Employers want people who get things done, not people who “participate.” Don’t write that you were involved with a project that produced $5 million in sales, state that you wrote 20,000 lines of code for a project that produced $5 million in sales. Don’t say that you “helped with the development of a new system” – write that you developed that system in a team environment.


3. List everything positive that you can think of about past positions, and use the best.

resume wordle
resume wordle (Photo credit: gloomybrook)
Was there positive growth at the organization while you were there, even if you weren’t directly involved? Mention it. Were you involved, even in a cursory fashion, with a hugely successful project? Mention it. Only mention the things that were clearly and strongly successful on your resume.

4. Be concrete.
Don’t state that you were involved with a hugely successful Project X, state precisely (in an action-oriented form) what your role was with that project, followed by a statement of exactly how successful it was in a quantitative fashion. Don’t state that you were involved with writing a new HR manual – instead, state that you contributed 24 proofread pages to a documentation system used by 25,000 employees. Don’t state that you did some coding for the public interface – state that you wrote 41% of the code for a website used by 2,000,000 visitors a month. If you’ve done the job of trimming things down to only the big successes, these numbers should be impressive ones.