Front-end development + UX + Accessibility

Write an awesome CV

A lush dark green forest with strong sunlight coming in from the right.
Make your CV shine.

My CV in its previous iteration was decent enough. Out of my 8 last applications I got 4 interviews, which from what I gather is pretty good.

But then I came across a job in an amazing organisation. For this I really wanted to do my very best applying.

So I did a lot of research, both about how to write a CV in general, and the more culturally specific issues that might come up in this particular country, and the organisation itself of course. I wrote it on Google Docs so I could get feedback from family and others I trust, and after 2 weeks I had something I felt was a new level of good enough.

Then the next week, out of the blue, my wife is told about an upcoming position that could be great for her, and us. However the deadline had passed, but they said she could apply that very day. A slightly stressful afternoon followed, but I got to make good use of what I'd learned working on my own CV, and realised I'd actually learned quite a bit!

Based on my comments to her old CV, I've put together this overview of what's needed to make a good CV.

First impression #

Keep it short #

Recruiters must often read 100s of applications for a single position. That means they're not going to read through your CV word by word. Most likely they'll scan through it in less than 3 minutes. Come to think of it, this is the main reason for most of the tips that follows.

Aim for 2 pages #

Two pages, plus a 1 page cover letter should be enough. That means kill your darlings!

Remove cruft that isn't relevant for this position. And yeah, that means potentially rewriting the CV for each new job. But after a few rounds you'll have a few different templates that don't need that much work to fit whatever you're applying for. I've got one for UX, one for Accessibility, and one for front-end dev.

Avoid the wall of text #

Keeping it short doesn't mean cram as much as possible into the 2 pages. A friend of mine, a recruiter in a different industry, told me it's not unusual to receive 7 pages(!) with wall to wall text and no margins. It doesn't matter how skilled you are at your job, nobody is ever going to read through that.

Everything is a list #

I'm a huge fan of lists, both in my HTML and at home, so adjusting my CV for that wasn't very hard.

Bullet points makes it easier to scan the whole document. It might make some sections longer, as each bullet point can be less than one line-length. Which again makes the total length longer. And whops! -suddenly it's more than two pages again.

So this is another challenge to shorten down the text even further, and be even more specific.

Design #

Use whitespace #

Whitespace is your friend. Have a generous line-height, spacious page margins, and just in case - more whitespace.

Whitespace is luxury, and Good Design™️. It's enough to make your CV stand out from the pack. It makes it easier to read, or rather scannable, allowing the reader to quickly find (and come back to) the key information.

And yes, this will also make the total length longer. You know the drill now: Keep on optimising that text!

I let my CV overflow to 2.5 pages just in order to have enough whitespace. Remember I said to aim for 2 pages. It's not a fixed rule. Better have it a little longer and much easier to read, than just short enough, but harder to read.

Consistent typography #

Make sure you use the same font-family, font-weight, font-size and line-height for all the body copy, as well as the the different sized header levels and all other repeating copy.

This helps setting up the information architecture. The information architecture shows where a section starts and ends, how sections are related to each other, and divided within, which ultimately makes it easer to read and find key information.

Templates #

Ok, so you're not a graphic designer. There are tons of free and paid templates online, in various formats (psd, docx, indesign etc.). Grab one that you like, and you've saved yourself a lot of time.

I avoid using anything with coloured backgrounds. There's a good chance the recruiter is printing out your CV, so there's no need to use all their ink, and it makes it harder to read.

Include keywords #

Use the words and language used in the job brief throughout the CV. Often companies use automatic scanners to filter the applications based on keywords before sending it on to a human.

Introduction #

If you're going to spend extra time on the copywriting of anything, this is it! This is your chance to make the all-important First Impression.

Some recommend not having a intro, others do. Again, it also makes the total length longer. But this is our chance of grabbing someone's attention with only one or two short sentences.

These sentences will have to show how exactly you are especially well suited for this position and this company. Try to get across what you will do for the company. Why do they need exactly you?

And while bigging yourself up, also rub their egos a bit. Find something exceptional about the company, and use that.

Show, don't tell #

Avoid fraises such as "I'm a passionate developer". Instead provide some evidence of your passion. Mention an award you won, pro-bono work you've done, or a particularly successful project you've worked on. A teaser is enough, and you can include more details under the relevant job history section.

Oh yeah, and if you're making more than one point: Use a list ;-)

Case in point:

Job history #

This is the main bulk of the CV. It's not enough to say "My responsibilities where database design, website management, cleaning dishes...". We need to include something about how good we were at these tasks. Which means providing some kind of evidence of this.

Start by briefly introducing the client or project's goal. List what and how you achieved that, and provide evidence of its success.

If you're a developer like me, you might not have been that involved in those parts of projects, so a bit of research might be necessary.

See if the company you worked for have some press releases, a blog post, or a case study of the project. They are good places to find this kind of information. E.g.“Visitors increased by 12% for the duration of the campaign.”

For each position:

Delete or compress old history #

If you've had a long career, or changed places often, the list of places you've worked might be very long.

Delete those that aren't relevant to the job you're applying for now. Then compress those early, yet relevant, jobs under one sub-header, and only include the most impressive projects.

If you're new, there's still no point including those non-relevant jobs. I have a long series of jobs that aren't on my CV: security guard, mail carrier, parking inspector, shop assistant, data entry etc.

Name-dropping #

You can also do some name-dropping if you've worked for any large or impressive sounding clients.

For example "I developed HTML templates" is ok, but "I developed templates used by MegaCorp in 24 countries" is better.

Skills #

Skills/Competencies/Tools/Methodologies... call it what you want. This can be a useful dumping ground for all those things that you want to include in your long paragraphs, but need to delete in order to keep it short.

But of course, having an endless list of keywords listed as your skillset is probably not the best idea either. For my CV I first entered everything I could think of that was relevant, which ended up being 69 items. That seemed rather excessive, so after a lot of pruning I got it down to 24, divided into three categories.

Bonus tips #

That sums up the writing of the CV itself. I still have couple other small tips that I learned along the way.

Header photo by Sebastian Unrau on Unsplash.

This article was originally published on dev.to.

← Home