It’s all very well designing your future but now you need to actually engineer it by testing and building. An obvious place to start is with your CV or résumé, because that’s where most people get going. How can you create a bug-free CV, résumé or completed application form? How can you support applications with a strong personal statement or covering letter? These documents are crucial part of your future so how can you debug them? 🐛

## 7.1 What you will learn

By the end of this chapter you will be able to

1. Structure and style the content of your CV and résumé appropriately
2. Articulate your story7 as evidenced by your experience, projects and education etc
3. Identify and fix bugs in CV’s by:
• Constructively criticising other people’s CVs
• Asking for, listening to, and acting on constructive criticism of your own CV
4. Quantify and provide convincing evidence for any claims you make you on your CV
5. Identify gaps is your CV and how you might begin to fill them

## 7.2 Beware of the black hole

Before we get started, let’s consider some advice from software engineer Gayle Laakmann McDowell. Gayle is an experienced software engineer who has worked at some of the biggest technology employers in the world: Apple, Microsoft and Google. She has also authored a cracking series of books on technology careers, particularly Cracking the Coding Interview which we’ll discusses in chapter 10. Gayle refers to the employer “black hole” described in figure 7.2.

If you’re applying to big employers, you’ll need to create a CV that is good enough to stand out before it disappears over the event horizon and into an employers black hole, see section 8.4.8. Your CV or résumé needs to be good enough to persuade an employer to invite you to an interview. You can start with an employer-agnostic CV but you may need to come back and revisit the issues in this chapter once you have identified some target employers, so that you can customise and tailor your CV and written applications.

## 7.3 The CV is dead, long live the CV!

Résumés and CV’s have reigned supreme in kingdom of employment and recruitment for many years but their demise has often been predicted, see figure 7.3.

While it is true that some employers don’t accept CVs or favour online application forms or digital profiles, it is still worth writing a CV because:

• Your CV provides a record for you of relevant things you’ve done
• Your CV enables you to get your story straight, What’s your story, coding glory? see section 2.2.3
• Your CV forces you to articulate who you are and what you want, see chapter 2
• Some employers will still ask you for one, see section 7.7.6 and figure 7.3
• Your CV helps you script and practice your “lines” for interviews, see chapter 10

Even if an employer never asks you for your CV, you’ll frequently want to use the content of your CV in applications and interviews. So this chapter looks at how you can debug your written applications, whatever the mechanism is for submitting them.

You can of course augment your CV with various public digital profiles such as LinkedIn, Github etc. A public digital profile can help employers find you, see section 8.3.2.

Wherever you’re putting information about yourself for potential employers, on a CV, Résumé, LinkedIn profile the same principles apply. See the checklist in section 7.9 and for specific advice on LinkedIn see:

## 7.4 It’s not bug, it’s a feature!

It’s an age old trope in Computer Science that engineers use to cover their mistakes, passing off their accidental bugs as deliberate features of their work, see 7.4.

“It’s not a bug, it’s a feature…” —A. Hacker

Nobody likes buggy software, but unfortunately we routinely have to tolerate badly-designed, low quality, bug-ridden software in our everyday lives.

In contrast, buggy CVs are rarely tolerated, they will usually end up in the bin. Even a tiny defect, like an innocent typo, can be fetal fatal. Most employers (particularly large and well known ones) have to triage hundreds or even thousands of CV’s for any given vacancy. This means the person reading your CV is as likely to be looking for reasons to REJECT your CV, than ACCEPT it, because that’s a sensible strategy for shortlisting from a huge pool of candidates. A buggy CV, application and covering letter could ruin your chances of being invited to an interview, see chapter 10.

Like writing software, the challenging part of writing a CV isn’t the creation but in the debugging and subsequent re-writing. Can you identify and fix the bugs before they are fatal?

⚠️ Coding Caution ⚠️

If you ask three people what they think of your CV, you will get three different and probably contradictory opinions. CV’s are very subjective and very personal. The advice in this chapter is based on common sense, experience and ongoing conversations with employers. What makes a good CV will depend on the personal preferences and prejudices of your reader. So, this chapter just describes some general debugging guidelines, rather than rigid rules.

It is good practice to triangulate responses from your readers. For example, if three different people point out the same bug in your CV you can be confident that it is a bug that needs fixing.

While referring to this guide, remember that:

• The main purpose of your CV is to get an interview, not a job. Your CV should catch attention and provide talking points for an interview
• Your CV will be assessed in seconds, rather than minutes so brevity really is key
• Bullet points with verbs first (see section 7.7.4) will:
• avoid long sections of flowery prose which the reader will very probably skip anyway. Instead, you can use your beautiful prose on your covering letters or personal statements, see section 7.10

You’re not trying to tell your whole life story from section 2.2.3 but to distill the essentials into several short stories which can be summarised into a handful of bullets or sentences. It’s a bit like the blurb or synopsis on the back of novel, can you entice the reader into wanting to find out more (by inviting you to an interview)?

## 7.5 Is it a bug or a feature?

Wherever criticism of your CV comes from, don’t take it personally - it is probably one of the first you have written. Think of your current CV as an alpha or beta version that you continuously test, release and redeploy. There are many chances to debug and improve your CV during your study but before potential employers read it. The aim of this chapter is to help you improve your CV, whatever stage you are at. Employers often grumble that Computer Science graduates lack written communication skills. Written applications and CV’s are a common example of this.

1. EDUCATION: Is your year of graduation, degree program, University and expected (or achieved) degree classification clear? Have you mentioned things you are studying now, not just courses you have finished? See section 7.6.2
2. STYLE: Does it look good, decent layout, appropriate use of LaTeX or Word or whatever? Are there any spelling mistakes, typos and grammar? Don’t just rely on a spellchecker, some typos can only be spitted spotted by a human reader see section 7.7.7
3. LENGTH: Does it fit comfortably on (ideally) one page (for a Résumé) or two pages (for a CV)? See section 7.7.3
4. STRUCTURE: Is the structure sensible? Is it in reverse chronological order? Most important (usually recent) things first? Not too many sections or anything missing? See section 7.6
5. VERBS FIRST: Have you talked about what you have actually done using prominent verbs, rather than just what you think you know? Avoid long sections of prose, see section 7.7.4
6. RESULTS: Have you also demonstrated and quantified the outcomes of your actions where possible, see Context, Action, Result & Evidence (C.A.R.E.) in section 7.7.2
7. SEE ALSO: This is just a quick checklist, see the longer CV checklist in section 7.9

How you structure your CV will depend on who you are and what your story is. Recruiters at Google suggest four or five sections, that follow a header section. Before we look at those, lets look at some general points about CVs, watch the videos shown in Figure 7.5.

As Jonathan Black, director of the careers service at the University of Oxford has pointed out, a key part of your story that you want to communicate in your CV is that you :

1. take responsibility
2. achieve things
3. are nice to have around

How can you demonstrate this? Watch the short video in Figure 7.6.

Quantifying and providing evidence for any claims you make will make your CV much more convincing. This can turn meaningless assertions described in figure 7.6 into meaningful evidence. So for example:

* Achieved excellent results

…is a bit vague, what were the results exactly, can you measure them somehow? Or at least describe them?

* Worked in a team

So you worked in a team? Worked is vague. What was your role and contribution exactly? How long did the project last? How many people were on your team? What was the result of your action? What’s the story, coding glory?

The first thing in your CV is the header, a simple section giving your name, email, phone number and any links shown in the CV in figure 7.7 for Alan Turing. That’s it!

1. 🎓 Education: the formal stuff, see section 7.6.2
2. 💰 Experience: paid work, see section 7.6.3
3. 💪 Projects: personal, school, social, side or University projects see section 7.6.4
4. 🏆 Leadership and awards: see section 7.6.5
5. Optional: but don’t call it that, see section 7.6.6

Let’s look at each of these sections in turn:

Unless you have significant amount of experience, the EDUCATION section of your CV is likely to be the first real section, after the header. Your education section needs to strike a balance between:

• Describing in enough detail what you’ve studied and any projects you’ve completed at University as part of your formal education
• Keeping it short and sweet by avoiding getting bogged down in tedious details

You’ve invested a significant amount of time and money in getting your degree. At this stage, your degree justifies more description than a terse one line BSc Computer Science. You’ll need to:

• say more than Pen Tester and Rick Urshion, who haven’t said enough about their University education
• say less than Mike Rokernel, who has given way too much information on his degree.

You don’t need to name every single module and give a mark for each. Neither do you need to give your result to FOUR or FIVE significant figures: 71.587%9. Two significant figures will do just fine: 72% (first class). You might like to pick out relevant modules, or the ones you enjoyed most. Employers like Google encourage applicants to emphasise courses on data structures and algorithms, but you’ll need to tailor your description to the role and be brief. On a one page CV, you might only have two or three lines to describe your higher education. 🎓

Experience is where you can talk about any paid or voluntary work experience you have. For paid work call it EXPERIENCE rather than WORK EXPERIENCE as the latter can imply work shadowing, see section 5.3. Work shadowing is valuable, but paid work is even better so you should make it clear if your experience was paid or not. Don’t discount the value of casual labour, such as working in retail or hospitality, these demonstrate your work ethic and ability to deal with customers, often under pressure. You are more than just a techie too, so anywhere you’ve worked in a team is experience worth mentioning, even if that team was just two people. Two people is still a team.

If you don’t have much experience, don’t worry, there are plenty of opportunities to get some. For details, see chapter 5 experiencing your future.

Are you experienced? Whatever it is, make sure you add it to your experience section. 💰

The PROJECTS section of your CV is a where you can describe all other things you get up to. These might include:

• personal side projects
• social responsibility projects
• open source projects
• entrepreneurial projects
• University projects (although these might fit better in your Education section)

Your projects will most likely be unpaid because paid work tends to fit better under the heading experience, see section 7.6.3. Perhaps you’ve completed some courses outside of your education such as a massive open online course (MOOC) or similar. Hackathons and competitions, fit well here too. You don’t need to have won any prizes or awards, although be sure to mention them if you have. Participating in hackathons and competitions clearly shows the reader that you enjoy learning new things. Demonstrating an appetite for new knowledge and skills will make your application stand out. If you’re looking for some inspiration for side projects, the codecrafters-io/build-your-own-x repository is a good starting point. Building and creating new things is a great way to understand them, just ask Richard Feynman shown in figure 7.9. What you cannot create you do not understand. One way of doing this is with open source projects which we describe in section 5.3.3.

Any longer projects you’ve done at University are worth mentioning. Your projects are important because they differentiate you from everyone else in your year group. Try to be more descriptive than this:

* First year team project

or perhaps

* Second year team project

or even just

* Final year project

By themselves, those project names are pretty opaque. They are OK for giving the context of your story but don’t give the reader much else to go on. What was the story (the context, action, result and evidence (CARE) we described in section 7.7.2) of those projects? How many people were in your team? How long did you collaborate for? What did you build? What was it called? What did it do? What roles and responsibilities did you have in the team? Was their conflict in the team? How did you resolve it? How did you motivate the free-riders in the team to contribute? This is all excellent CV fodder, see 7.10

It’s often better to describe what YOU did before you describe what the software, hardware or project did. Your reader is much more likely to be interested in the former than the latter. Let’s imagine you’ve developed a piece of software called WidgetWasher. You might describe it like this:

* WidgetWasher is a web service that washes widgets
* Makes use of an HTTP API and secret keys
* Tested WidgetWasher on a range of different operating systems
* Collaborated with one other contributor over two days
* Designed and implemented an API

Instead, you could reverse the order to change the emphasis like this:

* Designed and implemented an API
* Collaborated with one other contributor over two days
* Tested WidgetWasher on a range of different operating systems
* Makes use of an HTTP API and secret keys
* WidgetWasher is a web service that washes widgets

The latter has all the same information, but by reversing the order, you’ve emphasised what you did, rather than what the software did. 💪

If you can demonstrate leadership, you may want to dedicate a whole separate section for it. If you have experience of tutoring or mentoring other students, perhaps younger ones, make sure you highlight it as leadership. Teaching is a different kind of leadership to running a small business or captaining a sports team, but it is leadership nonetheless.

A leadership section is also a good place to add any prizes you’ve won. If you’ve been granted any interesting awards or honours be sure to mention them. You’ll typically need a bit more than:

* Awarded the Poppleton University scholarship for excellence

Congratulations, but how many people were awarded that prize? How many applicants or entrants were there and what percentage were successful? Was it a regional, national or global award? How frequently is the award given? It is unlikely that your reader will have heard of the award unless it is widely known. So if you’re going to mention awards, give the context where you can so the reader can understand what the prize was for. 🏆

If you have anything else you want to highlight besides your education, experience, projects and leadership and awards you may still have room for one more optional extras section. Try to come up with a better name than Miscellaneous, Extracurricular or Other highlights, which sound like dumping grounds for the leftovers. You might decide to have a dedicated skills section but see section 7.6.7.

You may opt to have a hobbies and interests section which can add a bit of colour to what can otherwise become quite a dull list of facts. However, it is debatable how many (if any) hobbies and interests you should list on your CV. For a one-pager you’re usually pushed for space and looking for things to edit out (rather than add in), so if you’re going to list hobbies, I’d stick to those that are relevant to the job or those that demonstrate particular transferrable or soft skills. Organising or participating in team sports is a good example of a relevant hobby as it provides evidence of your teamwork, commitment, reliability etc, see figure 7.11. Other collaborative activities outside of sport will also demonstrate your communication skills.

The fact that you enjoy swimming, reading, football, cooking and hiking is a vague and pretty boring, making it unlikely to be a factor in the decision to invite you to interview. There’s nothing wrong with these pastimes but there’s not much point mentioning them on your CV unless you have, for example:

• coached a swimming team
• trained as a mountain leader
• organised, hosted and participated in a book club
• regularly participated in or organised competitive sports matches (for example)

In this case, the way you have engaged with your hobbies demonstrates your communication and leadership skills. So in this context, your hobbies are worth talking about if you have any space left. However, if they are just hobbies that enable you to amuse yourself, you should probably leave them out as they are unlikely to be of interest to an employer. Sure, they add colour to your CV, but you’ve probably got more interesting and important things to say about who you are.

Of course, you might get lucky and your interviewer could be intrigued (or even share) your esoteric passion for Quidditch (say), but you can’t rely on it. So, I reckon if you’re going to mention hobbies and interests at all then …

• pick the unusual hobbies that make you unique
• describe the interests that add some colour and personality to your CV
• be specific, e.g. reading japanese novels from 20th century might sound more interesting than just reading
• highlight any actions you’ve taken, see chapter 18

… or just leave them out altogether. That option is up to you.❓

You may be tempted to dedicate a whole section on your CV to skills, particularly the technical ones. Maybe it makes you feel good listing them all in one place like a stamp collection. If you’re going to have a skills section, keep it short. Why? Let’s imagine, that like Rick Urshion, you include Python in a long list skills, with its own dedicated section. There are at least five problems with Rick’s not so skilful approach:

1. No Context to give the reader an idea of where he’s developed or used his Python skills. Was it during his education, as a part of his work experience or his personal projects? We don’t know because he doesn’t say.
2. No Actions to demonstrate what he’s done with his Python skills. So Rick claims he knows Python. So what? What did use them for? We don’t know because he hasn’t told us.
3. No Results given for what the outcome of using the skills was. Did he save his employers some money? Did he make something more efficient? Did he learn some methodology? We will never know.
4. No Evidence to support his claims. Perhaps he DOES have Python skills, perhaps he DOESN’T. Is he telling lies and peddling fake news (see section 8.4.4)? It’s difficult to tell.
5. No C.A.R.E. There’s no story told for that skill, see figure 7.12. This makes for a very dull and boring read. Yawn. NEXT! 🥱

So, this doesn’t mean Rick shouldn’t mention his Python skills. Where he can, he needs to give us the context, action, result and evidence (C.A.R.E.) of his story described in section 7.7.2. This will make his Python story much more convincing and interesting to read. Showing a bit of C.A.R.E. will improve his chances of being invited to interview.

This applies to soft skills too, not just hard technical skills. Best to mention the context in which you’ve used any skills you mention on your CV. So, if you’re going to have a skill section:

• keep it short (one or two lines maybe) but personally I’d avoid dedicating a whole section to it
• stick to your strongest and most relevant skills that you are comfortable to answer questions on in your interview, rather than an exhaustive encyclopædic inventory
• avoid listing mass marketed office products of Microsoft (e.g. Word etc) as a skill, they are not generally very interesting skill because almost everyone has them. They won’t set you apart much from your competition, so don’t waste valuable space talking about office unless you’ve done something interesting with them, like some advanced integration with other software. Cloud services can be a slightly different matter, see section 11.4.1.

If you’re a computer scientist, you also have demonstrable meta skills like the ability to learn things quickly. You can also think logically and critically, reason, problem solve, analyse, generalise, decompose and abstract - often to tight deadlines. These computational thinking skills are future-proof and will last longer than whatever technology happens to be fashionable right now. Employers are often more interested in these meta capabilities and your potential than in any specific technical skills you may or may not have.

## 7.7 Birds eye view

Having looked at the sections you’re likely to have, we’ll take a birds eye view of your whole CV. The issues in this section apply to the whole of your CV, rather than individual sections.

Making your CV look good can take ages, but a well presented CV will stand out. While its worth making an effort to style carefully and consistently, you need to be be wary of the huge time sink of typography.

Whatever your typographical style is, portable document format (*.pdf) is the safest way to deliver it. It’s called portable for a reason. While Microsoft Word is fine for editing, it is difficult to ensure that a Word document doesn’t get mangled by transmission via the web, email or even Microsoft’s own products like Teams! PDF is much safer, you can be more confident that it will work well on a range of different operating systems and devices. Try opening a Word document on any smartphone or tablet and you’ll see what I mean. It helps if you can give the file a descriptive name so ada_lovelace.pdf is a better filename than my_cv.pdf, especially if its being read by a human and not a robot. 🤖

It’s fine to author your CV in Microsoft Word, but you’ll want to save it as a PDF to make it more platform independent. LaTeX and overleaf can be used to create professional PDFs and there are plenty of good templates. See Getting started with LaTeX (LaTeX4year1) if you’ve not used LaTeX before, or you need to refresh your memory.

### 7.7.2 What’s your story, coding glory?

One way to structure descriptions of items within each section of your CV is to use Context, Action, Result and Evidence (C.A.R.E.) to tell your stories. What’s your story, coding glory? The C.A.R.E. method can also be useful for structuring answers to interview questions, especially if you get nervous. So for example, rather than just listing Python as a skill, you could tell the reader more about the context in which you’ve used python, what you actually did with it and what the result was. You really need to spell it out.

• CONTEXT: So you’ve used Python, but in what context? As part of your education? For a personal project? As a volunteer? In a competition? All of the above?
• ACTION: What did you do with Python? Did you use some particular library? Did you integrate or model something? What verbs can you use to describe these actions, see chapter 18
• RESULT: What was the result and how can you measure it? You picked up some new skills? What was the impact? Perhaps you made something that was inefficient and awkward into something better, cheaper or faster? Some things are hard to measure but you should quantify results where you can.
• EVIDENCE: Where evidence exists, you should highlight it. That could be a quantification, for example describing a result in numbers (see as measured by below) or it might be certification described in chapter 12. If you’re talking about software, point to a copy online if you can, but beware of plagiarism if you publish university coursework on github. Nothing says “I can build software …” quite like “ … and here’s one I made earlier”.

You don’t have to stick rigidly to the order C.A.R.E. as long as they appear somewhere. For example, recruiters at Google (see figure 7.5) advise candidates to describe their experience and projects using this simple pattern:

* Accomplished [X], as measured by [Y], by doing [Z]

Where accomplished is Result, measured by is Evidence and doing is the Action. So instead of just saying:

* Generated reports for end users

You could say:

* Generated daily reconciliation report for team by automating workflow of 8 different tasks

The latter is better because it is more specific, captures the result (accomplishment), by giving evidence (8 different tasks) and talks about the actions (the doing part). Choose the verbs you use carefully, see chapter 18 for examples.

How long should your CV be? Many people start with a two page CV, which is a sensible starting point shown in figure 7.14. It is also advisable to create a one page Résumé.

At this stage in your career you should be able to fit everything on to one page. However, it can be challenging and time consuming squeezing it all on, see figure 7.15.

It takes more time to write less. Writing a one page résumé is a valuable exercise, because it forces you to distill and edit out any filler or fluff, which you sometimes find on two page undergraduate or graduate CVs. It is much better to have a strong one-page résumé than a weaker two-page CV that is padded out with filler to make up the space, as described in the video in figure 7.14. Adding more features (pages and content) to your CV doesn’t necessarily make it better. Sometimes adding more features to your CV will make it worse, as shown in figure 7.16.

If you’re struggling to fit all the information onto a one page résumé, revisit each section and item carefully. Is there anything you can drop? Can you save a wasteful word here, or a lazy line there? Check for any spurious line breaks because every pixel counts. Don’t throw your two page CV away, it is still a good store of stuff you might want to add to customised one-page résumés.

A simple but effective technique for emphasising what you have done, rather than just what you know, is to start the description of it with a verb. Employers don’t just want to know what you know, but what you have actually done. So, for example, instead of saying e.g.

* In my second year CS29328 software engineering module I used Java, Eclipse and JUnit to test and build an open source Massively Multiplayer Online Role-Playing Game (MMORPG)

you could say:

* Built and tested a large open-source codebase using Eclipse, Ant, JUnit and Jenkins”

followed by:

* Added and deployed new features to a Massively Multiplayer Online Role-Playing Game (MMORPG) in Java

The latter examples get to the point much quicker and avoid the problem of using I, me, my... too much which can sound self-centred and egotistical. Although your CV is all about you so it is natural to have a few personal pronouns in there, too many can look clumsy and give the wrong impression. Choose the verbs you use carefully, see chapter 18 for examples.

### 7.7.6 Robot proofing your CV

It’s a good idea get feedback from as many different sources as you can on your CV. By sources I don’t just mean humans, but also robots. Larger employers will use automated Application Tracking Systems (ATS) to log and trace your application. These “résumé robots” (if you like) are unlikely to have arms and legs like the one in figure 7.18, but they will be looking for keywords and standard headings in your CV. You can get automated feedback from a range of different automated systems, though it is a good idea to remove any personal information like phone numbers and emails before using these free services. You might also want to check what the services privacy policy says about what they do with your personal data. Résumé robots include:

Besides providing feedback on the content of your CV, using these systems can help address issues such as the use of tables or layout which may cause problems for some systems. For example, some systems ignore the second column of a two-column CV because they can’t parse the PostScript reliably to identify columns. Some things to check with automated CV screens:

• Have you used standard headings for the sections? Non-standard sections maybe ignored or misunderstood
• Have you used appropriate verbs to describe your actions?
• Is your layout and design robot friendly? Sometimes tables and two column layouts can get horribly mangled, see what happens to tables and columns in an applicant tracking system

### 7.7.7 Spellchecking

Bots, grammar and spell checkers will improve your CV but you can’t rely on automated help completely. The résumé robots described in section 7.7.6 will just encode the biases and prejudices of whoever wrote their algorithms. Spellcheckers can’t be relied on completely either, as shown in the poem below:


Eye halve a spelling checker
It came with my pea sea
It plainly marques four my revue
Miss steaks eye kin knot sea

Eye strike a key and type a word
And weight for it to say
Weather eye am wrong oar write
It shows me strait a weigh

As soon as a mist ache is maid
It nose bee fore two long
And eye can put the error rite
Its rare lea ever wrong

Eye have run this poem threw it
Its letter perfect awl the weigh
My chequer told me sew

---Anon

While automation can help improve your writing, ultimately there is no substitute for people (you know: actual humans) reading your CV, and the more people that read it the better. This could be potential employers, your critical friends shown in figure 7.19 or just reading it out loud to yourself described in section 4.5.1.

You might be tempted to put your referees details on your résumé. Don’t bother because;

• references waste valuable space. You can say much more interesting things about yourself than who you referees are
• references aren’t needed in the early stages of a job application anyway. Employers typically ask for your referees much later, when you’ve been offered or are about to be offered the job
• references disclose personal information. Do you really want to be giving personal details out to anyone that reads your CV? It could easily be misused.

It’s not even worth saying references available on request - that just wastes space as well and is implied information on every CV anyway.

## 7.8 Breakpoints

Let’s pause here. Insert a breakpoint in your code and slowly step through it so we can examine the current values of your variables and parameters.

* PAUSE ⏸️
* RESUME ▶️

## 7.9 Checklist: Big Bad Bugs

Here is a quick check-list for debugging your CV before you send it off to an employer:

1. ✅ Does it fit comfortably on exactly one page (résumé) or two pages (CV)? Definitely not one-and-a-half pages or more than two? See section 7.7.3
2. ✅ Does the style look good? Is it easy on the eye? Is there adequate whitespace, not too much (gappy) or too little (cramped)? See section 7.7.1
3. ✅ Is your year of graduation, degree program, University and expected (or achieved) overall degree classification clear? See section 7.6.2
4. ✅ Have you eaten your own dogfood (woof), see section 4.5.1? Is everything relevant? e.g. no swimming certificates from ten years ago?
5. ✅ Have you spell-checked using both automatic and manual (proof-reading) techniques? See section 7.7.7.
6. ✅ Have you got a second opinion from a “résumé robot”? Is it robot proof? See section 7.7.6 🤖
7. ✅ Have you shown you C.A.R.E? Are the Contexts, Actions, Results and Evidence described in section 7.6.7 clear? Have you added context using relevant hyperlinks that an interested reader can click on? See section 7.7.5
8. ✅ Is it in reverse chronological order with the most recent things first? Can your timeline be easily scanned, with all dates clearly aligned for easy reading? See Neil Pointer as an example with a clear timeline using right-aligned dates.
9. ✅ Have you avoided using too many personal pronouns? I, me, my ... everywhere? See section 7.7.4
10. ✅ Have you made it clear what you have actually done using prominent verbs? See chapter 18
11. ✅ Have you given sufficient information on your education without going into too much detail? Have you mentioned courses you are studying now (and next semester)? See section 7.6.2
12. ✅ Have you quantified and evidenced the claims you have made where you can? See section 7.6
13. ✅ Is it balanced, including both technical and non-technical (softer) skills? See section 5.3.5
14. ✅ Does it have a good, clear structure? Not too many headings, around five sections for a one-pager see section 7.6.1?
15. ✅ Have you clearly distinguished between paid, unpaid and voluntary experience? Have you done the same for your projects, see section 7.6.4? Have you included all of the relevant experience that you can fit on including casual work, see section 5.3.5?
16. ✅ Has your CV been reviewed by other people? Do a CV swap with a critical friend (see figure 7.19) and score each others CV’s using this rubric. This is a bit like pair programming. According to Linus’s law “given enough eyeballs all bugs are shallow” so the more people who give you feedback the better
17. ✅ Have you reviewed other people’s CV’s? This will put you in the shoes of an employer or recruiter, thereby helping you to write a better CV yourself. See the examples in chapter 15. Who would you want to interview and why?

## 7.10 Covering letters & personal statements

Applications and CV’s are often accompanied by covering letters or include some kind of personal statement. Whereas a lot of your CV is essentially a bulleted list of facts and statements, a covering letter or personal statement gives you a chance to really demonstrate your fluent written communication skills in clear prose. If you’re going to have a personal statement or profile on your CV keep it short, unlike Mike Rokernel who waffles on for ages without providing any evidence. Usually this kind of information is better in your covering letter.

Let’s say you’re applying for a widget engineering position at widget.com. There are three things you need to cover in this order:

1. Why them? Why are you applying to widget.com
2. Why that role? Employees of widget.com have many roles and responsibilities but what is it about widget engineering (say) that attracts you?
3. Why you? Why should widget.com employ you? What skills and experience make you stand out from all the other candidate widget engineerings? What are your Unique Selling Points (USPs)? Say why you would be good for them (not why widget.com would be good for you and your career).

You can see some examples of answers to these questions at:

### 7.10.1 Does anyone actually READ covering letters?

Some employers will read your covering letter very carefully, others less so. It is not always clear which employers will bother and which won’t.

Even if nobody reads your covering letter, it is still worth writing one because formulating answers to the three basic questions in section 7.10 will force you to rehearse standard interview questions.

Think of your covering letter as practicing some of the lines of your elevator pitch.

## 7.11 Debugging summary

Too long, didn’t read (TL;DR)? Here’s a summary:

In this chapter we have looked at how to debug your CV. If you fix the bugs we’ve described here, before an employer sees your CV, you’ll stand a much better chance of getting an interview. The checklist above in section 7.9 is a good place to start.