Last significant update:
Developers are often judged on what they have built rather than on a long list of tools. A strong developer CV names the technologies, explains the problem each project solved and makes your role in a team clear. The example here is fictional; adapt it only to work you have really done.
Lead with a precise title and profile
Use a job title that matches the role, such as “Frontend Developer” or “Backend Developer”, and follow it with two sentences about your main stack and strengths. Fictional example: “Frontend developer with three years of experience building accessible interfaces with React and TypeScript.” Be honest about your level, because technical interviews will test it.
Group your skills in a meaningful way
Instead of one long list, group languages, frameworks, tools and practices. Put the ones the advert needs first. Do not add a technology you have only read about; the interviewer may ask you to explain a recent use of it.
Describe projects with problem, action and result
For each role or project, say what you built, which technologies you used and what changed. Fictional example: “Rebuilt the customer dashboard in React, split it into reusable components and wrote tests for the main flows.” Add a result only if you can support it, such as a measured load time or a feature that shipped.
Make your role in a team clear
Say whether you worked alone or with others, and what part was yours: code reviews, mentoring, writing documentation or fixing bugs. Avoid claiming sole credit for team work. Employers value people who can explain what they decided and why.
Link to work they can open
Add a GitHub, portfolio or demo link only when it is tidy and opens correctly. A short README that explains what a project does is more useful than many unfinished repositories. Do not share private company code or confidential details.
Keep it one or two pages
Three to five lines per role, with the most relevant first, is plenty. For a first developer job, put education and projects above experience. Check the PDF carefully: code-related words and links are easy to garble.
Related examples and guides
Sources
Frequently asked questions
Should I list every technology I have used?
No. List those that match the role and that you could discuss in an interview. A shorter, honest list reads better than a long one.
Is a GitHub link necessary?
Not always, but a clean profile with a few well-described projects can support your CV. Make sure the links work.