Whether you’re starting to look for new opportunities or just want to get your CV in shape, it can be difficult to know how to best portray a software skillset on a single piece of paper. We hope that this article will provide general CV-writing best practices, as well as specific strategies to highlight your software engineering expertise.
Trust us, the clutter is not something you want to be remembered by. This applies to all CVs in general - recruiters and hiring managers generally do not have the time and energy to sift through multiple pages, opaque wording, or confusing formatting, especially if the opening is an attractive one, which means high volume of applicants.
So, be sure to keep your CV to a single page. Even if you have many experiences that seem worth sharing, you are better off choosing the most important, relevant ones (and including more details about them) rather than trying to squeeze everything in, but losing the important details of your most impressive achievements.
A way to keep it short is to use concise, straightforward language rather than using fluffy language to impress. Once you’ve written a draft, go through and think critically about each bullet point: Ask yourself whether there’s a way to say the same thing in fewer words, or to make it punchier with more action-oriented words. It can also be helpful to have a friend, colleague, or mentor read it over for a second opinion.
Lastly, keep the formatting clean by using section headers and consistent fonts/font sizes. Must-have sections include education, employment, and skills (where you can list your proficiency with various programming languages); Others might include personal projects, awards, certifications, or interests/hobbies (this can give your potential employer a better sensing of you as a person).
Whether you’re applying to a very specific role or applying more broadly, be sure to tailor your CV accordingly. If there are a few types of roles you’re considering, it might be worth keeping a different version for each.
Some people prefer to keep a “master” CV with all of their experiences listed (this might exceed the one-page limit), which can be trimmed down based on which skills a role requires and how your background fits into that profile. Others may keep a few versions of their CV ready to go depending on which best fits a job they’re applying for.
Whatever your strategy, don’t underestimate the importance of what you do and don’t include on a CV you submit to a job posting: Even if you have the most relevant experience, if it doesn’t come through on your CV then the hiring team won’t know what a good fit you might be. Further, including more relevant jobs or projects may increase your chances of talking about them in the interview, as interviewers often use the candidate’s CV to guide the conversation.
Unlike many other careers, software engineers’ work (e.g. tools, apps, websites, etc.) can often be publicly viewed. When it comes to CV writing, this is a huge plus, as it gives you the chance to show, rather than tell, what you’ve done.
Some engineers like to include a ‘Projects’ section, particularly if they’re earlier on in their careers but have undertaken personal projects to boost their skills or to explore an area of interest. Even if the work is incomplete or the projects are small, this section can also demonstrate your passion for engineering as it will indicate you’ve taken on this work outside of your day job.
You might also include links to online portfolios such as GitHub or StackOverflow, which can give the hiring team clear evidence of which skills you bring to the table. If you have a personal website with links to various projects, this can be a way of keeping your word count down while still showcasing all of your work.
At the end of the day, your CV is only one small piece of the candidate profile that a company will assemble in the process of interviewing you—but it’s an important one as it’s often the first impression a hiring team will have of you. Spending time to tinker with and tailor your CV may seem mundane, but it’ll certainly be worth the effort if it helps you make it past the initial screening process.
Not so much of a tip but if you still feel confused on how to write yours, why not reach out to one of our NodeFlair Talent Advocates here. We'll help guide you to get your CV in shape, after all, we are all about empowering developers like yourself to succeed and code() at where you love. Or if you are all about that LinkedIn game, why not check out our nifty guide on 7 actionable tips to get noticed on LinkedIn as a developer.