Software Developer CV: what to include

Updated 16 September 2026 · 2 min read

A developer's CV has one main job: to convince the reader that you can build software that works. Employers look for relevant experience, projects that demonstrate skill, and clear evidence of the technologies they use. This guide explains how to present that evidence concisely and credibly.

How this guide was made

Written for this site with AI assistance, then checked automatically before publishing. The topic table, sample questions, worked examples and study plan are generated from this site’s question bank: each worked example is recalculated by separate code, and each sample answer says where it came from.

The guide deliberately states no salaries, grades, pass marks or exam dates. Those change, and they could not be checked here, so take them from the advert itself.

This site is independent and is not affiliated with MIFOTRA or any employer.

Match the advert

Note the languages, frameworks, databases and practices the advert lists, and the qualification it requires. Make the ones you genuinely have easy to find, preferably shown in the context of real work or projects rather than only in a skills list.

Lead with projects and impact

For each role or project, describe what you built, the technologies you used and the result. "Built a REST API in Node.js for a school records system used by 30 schools" is far stronger than "backend development". Where possible, include measurable impact, such as faster load times or fewer support requests, but only when the figures are accurate.

Link to your code

Include links to a code repository and any deployed projects. Choose your best work, make sure each repository has a clear description, and remove anything sensitive, such as passwords or client data. One tidy, well-documented project persuades more than many unfinished ones.

Present technical skills honestly

Group skills by type: languages, frameworks, databases, tools and practices. Indicate depth honestly, for example by separating technologies you use daily from those you have only studied, because interviews test the skills you list.

Include education and learning

List your degree or diploma, and any relevant bootcamps, courses or certificates. For newer developers, relevant coursework or a final-year project can be valuable evidence.

Explain your part in team projects

Employers know that university and bootcamp projects are usually built in groups. Say clearly which parts you wrote, which decisions were yours and what you learned from the rest of the team. Being precise about your contribution builds more trust than implying you built everything alone, and it prepares you for the interview questions that follow. Panels often ask a team-project candidate which part they would change if they rebuilt it today.

Mistakes to avoid

Listing many technologies with no evidence of using them.
Linking to repositories that are empty, broken or contain secrets.
Describing duties instead of what you built.
Writing a long CV that hides your strongest projects.
Using vague claims such as "expert" without support.

Open adverts for this position

No open Software Developer advert matched when the jobs board was last checked. It is refreshed every morning.

Browse every open vacancy

Common questions

Should I include freelance or volunteer projects?

Yes. Describe them like employment: the client or purpose, what you built and the result.

How long should a developer CV be?

One or two pages for most developers, with the most relevant experience and projects first.

Should I include a technical blog or talks?

Include them if they are relevant and of good quality, because they show you can explain technical ideas clearly, which employers value.