A good developer CV puts the technical stack at the top (languages, frameworks, tools), followed by experience described by impact ("migrated X to Y, cut build time by 40%") rather than a list of tasks. It includes a projects section (with GitHub / portfolio links) that counts as much as your degree, especially for junior profiles. It fits on one to two pages, stays single-column to remain readable by ATS, and reuses the exact technologies from the job posting. The classic trap: listing 30 technologies with no level or context. Ten technologies you actually master, shown in action, are worth far more.
A developer CV is unusual in one respect: it gets read twice. First by screening software (the ATS) and a non-technical recruiter, both looking for keywords: a language, a framework, a job title. Then, if you get through, by a lead or a CTO who wants to see what you have actually built. A good CV speaks to both readers at once.
In this article: the structure section by section, a concrete example of how to organise it, how to present your stack and your projects, and the mistakes that get solid profiles turned away.
What is the structure of a developer CV?
The order of the sections is not neutral. A tech recruiter wants to find your stack and your achievements fast. Here is the framework that works, from top to bottom.
| Section | What goes in it | Why it comes first |
|---|---|---|
| Header | Name · title ("Back-end Developer", "Full-stack") · city · email · GitHub · LinkedIn | The title frames the read; the GitHub link is a differentiator |
| Summary (2-3 lines) | Your profile, your main stack, what you are looking for | Gives context before the details |
| Technical skills | Languages, frameworks, databases, tools, cloud | This is what the ATS and the recruiter scan first |
| Work experience | Roles, described by impact and technical context | The heart of the CV |
| Projects / open source | Personal builds, side projects, contributions, with links | Counts a lot, especially when junior |
| Education | Degrees, certifications (AWS, Azure, Scrum, etc.) | Useful but rarely decisive on its own |
| Languages | French, English (often essential), German | Swiss market: technical English is almost always expected |
For a junior or career-changer profile, the Projects section can come before experience: that is where you prove you can code, even without years in a company.
How do you present your technical stack?
This is the most poorly done section. Two mistakes keep coming up: the catch-all list of 30 technologies, and the total lack of hierarchy. The recruiter has no idea what you truly master.
The right method: group by category and prioritise. For example:
- Languages: TypeScript, Python, SQL (fluent) · Go (basics)
- Front-end: React, Next.js, Tailwind
- Back-end: Node.js, PostgreSQL, REST/GraphQL
- Cloud / DevOps: Docker, AWS, CI/CD (GitHub Actions)
- Tools: Git, Jira, Figma
Three principles:
- Highlight what the posting asks for. If the ad wants React and AWS, those two need to jump out, not be buried at the end of a list.
- Do not list what you cannot defend in an interview. A technology on your CV means a potential question. Bluffing shows within five minutes in front of a lead.
- Indicate a level when it helps, without inventing an absurd scale (no "React 92%"). A simple "fluent / basics" is enough.
How do you describe your experience: impact, not a task list?
A tech recruiter does not care that you "took part in developing an application." They want to know what, with which stack, and with what result.
Compare:
- ❌ "Developed features and fixed bugs on the application."
- ✅ "Built the payment module (Stripe, Node.js) used by ~5,000 users/month; cut the payment failure rate from 12% to 3%."
The formula that works: action + technical context + measurable result. Even without an exact figure, add a sense of scale ("on a 200k-line codebase", "for a team of 8 devs"). It turns a task into an achievement.
This line-by-line rewriting work is tedious. candidat.app does it from your real background: it rewrites your experience into impact-oriented bullet points and reuses the technologies from the target posting, without inventing anything. Handy for getting past the blank page.
Why are projects your best proof?
For a developer, a link is worth a thousand adjectives. A well-built projects section can make up for an unusual degree or a lack of years.
For each project, give: the name + a link (GitHub, demo, portfolio), a sentence on what it does, and the stack. Example: "Real-time Kanban, a collaborative task-management app (React, Node, WebSocket, PostgreSQL). [github.com/…]". Favour two or three finished projects over ten empty repos.
What about the Swiss case and ATS?
Two reflexes specific to the Swiss market and automatic screening:
- Single column, text PDF format. Very graphic dev CVs, in two or three columns with skill bars, pass ATS poorly and scramble extraction. Plain and structured stays the winner. Details in our article on the ATS-friendly CV.
- English is almost mandatory. Many tech postings in French-speaking Switzerland are bilingual or in English. State your level clearly, and do not hesitate to use English titles ("Software Engineer", "Front-end Developer") alongside the French ones.
For everything else (length, order, restraint), the conventions of the Swiss CV apply just as they do for any other profession.
In short
An effective developer CV prioritises its technical stack at the top, describes its experience by impact rather than by tasks, and leans on a projects section with links. It reuses the exact technologies from the posting, fits on one to two pages in a single column to stay readable by ATS, and shows only what you can defend in an interview. For a junior, projects prove what the degree does not say. In Switzerland, add a clear English level: it is often the criterion that decides.
FAQ
Should you put your GitHub on a developer CV?
Yes, if the profile is active and presentable. A GitHub with two or three finished projects is a major asset, especially when junior. On the other hand, a link to an empty account or one full of forks with no contribution can work against you: it is better to leave it out than to show emptiness.
How many technologies should you list on a dev CV?
Aim for mastery, not quantity. Around ten technologies you actually practise, grouped by category and prioritised, are worth more than a list of thirty you could not defend. Every technology shown is a potential interview question.
Can a developer CV be creative / graphic?
With caution. An overloaded design (multiple columns, level bars, icons everywhere) hurts readability for ATS and does not impress a tech lead, who judges the code and the achievements. Plain, clear and well-structured stays the most effective.
What is the difference between a junior and a senior dev CV?
The junior puts projects and education up front to prove their skills; the senior puts experience, impact, architecture and sometimes technical leadership (code reviews, mentoring, stack choices). The stack stays at the top in both cases.
Do you need an English CV to apply in tech in Switzerland?
Often, yes. Many tech companies in French-speaking Switzerland recruit in English or in a bilingual environment. Having an English version ready, or at least the right English titles, clearly widens the number of postings you can reach.