​​I've been recruiting Software Developers for over seven and a half years, during which I've reviewed thousands of CVs of varying quality. Over this time, I've developed a strong sense of what makes a credible CV, what businesses are looking for when they first open a document, and what they prefer to avoid.

Here are three common mistakes I frequently encounter, along with suggestions on how to improve the quality of your CV by avoiding them. Many of these may seem obvious, but it's often the obvious things we tend to overlook. It’s important to note that these are my opinions and are specific to the industry I recruit for. That being said, correcting the mistakes outlined below can improve your CV, regardless of your job title or industry.

Failing to Showcase your Skillset

A major mistake I come across on CV’s is the lack of clarity regarding the technical skillset of an individual. Too often the skillset section of the CV lists every technology that person has ever used in a commercial or personal setting, of which it dilutes the quality of your profile and can remove you from contention for a job that you’re potentially suitable for.

Take the below as an example that I come across quite often:

Key Technical Experience: C, C#, C++, Java, JavaScript, PHP, Python.

Usually when I have an opportunity to dig a little deeper with a candidate that has something similar to the above, it’s often the case that they have used the majority of them sporadically throughout the career and many of them are not recent commercial experience.

Of course, you can mention technologies you've used in a commercial work environment (with more detail typically provided in each job description). However, the best CVs I see clearly highlight the technologies the candidate is most proficient in, those they've had commercial experience with but haven't used recently, and the technologies they've worked with on personal projects.

It's important to remember that if a company's internal talent team or HR is handling the initial CV screening, they likely won't have a technical background. Occasionally, initial screenings rely on keyword matching, so clearly highlighting the technologies you're strongest in can greatly improve how well your profile is represented for the right job opportunities.

Who are you?

Since the pandemic, most first-stage interviews have shifted to 30–45-minute video calls. This has been a change for the better – no longer do you need to book a half day annual leave to attend a first stage interview that you can often tell in the first five minutes whether it’s a suitable fit. Instead, you’re able to schedule the interview around your day, which allows for a more informal setting to find out more about the business and the position you’re interviewing for.

Alternatively, a negative aspect I hear from video interviews is that it can be more difficult to build rapport, as opposed to an in-person meeting. Therefore, your CV plays a key part in painting a picture of who you are as a person, and can prompt further questions for the interviewers to ask.

CV’s need an opening statement to introduce your profile as a candidate. This is who I am, this is what I do (I’m a Software Engineer with eight years commercial experience…), this is what I’m skilled at, and this is what I’m looking for in a new position. It doesn’t need to be more than a few lines, but it introduces who you are and states your intention on where you want your career to go. CV’s require a personal touch rather than it being just a list of your experience.

I get asked on occasion, whether hobbies should be included on CV’s – absolutely. Same reason as above; it provides your profile with more personality and you will be surprised how this can often prompt questions in an interview setting should they also share the same interests (just don’t put your hobbies at the top of the CV).

Waffling

CV’s don’t need to be longer than 2 pages, 3 pages at most. The whole purpose of a CV is to start a conversation; it’s to get the interest of the person reading it to want to find out more about the person behind the page. Too often I come across CV’s that are 5+ pages, mostly consisting of the same responsibilities repeated from one job to another.

Your most recent experience is the most relevant. Ensure the last five years contain the most detail of your experience, as this is what prospective employers will be seeking. If you have experience on your CV that isn’t relevant for the positions you’re applying for, it doesn’t require more than a line or two describing it. If it’s a role outside of Software Development/Technology, it needs a mention to explain what you were during that period of your career, but nothing more than that (I’ve had applications from software professionals with elaborated explanations of their university/first jobs – it’s not necessary).

Similar to what I mentioned in the Key Technology section, having too much information in your CV can distract from what your main responsibilities were, and what value you can provide to a new business.

Conclusion

In summary, while the three points I’ve discussed may not be revolutionary, they are often overlooked—particularly in the frantic pace of today’s job market. Over the past eighteen months, many candidates have faced redundancy, creating an urgent desire to secure new employment. Unfortunately, this rush can lead to hasty CVs that fail to accurately represent one’s skills and experiences. I chose to address this topic because I have witnessed these common mistakes repeatedly throughout my career.

Remember, you only have one chance to make a first impression with a potential employer; it is crucial to establish the right tone from the outset to effectively showcase your qualifications and expertise.