Article contents
A developer CV gets read twice. First by a recruiter, often non-technical, who checks in a few seconds that the profile fits the role. Then by a technical lead, who looks for concrete evidence: technologies used, projects shipped, level of responsibility. To pass both, the CV has to be readable at a glance and verifiable in depth.
This guide is for junior and experienced developers alike, whether they aim at web, mobile, back-end or data work. It does not repeat the sector-by-sector samples in our article on CV examples by profession; it concentrates on what is specific to development: the stack, the projects and how to measure the work done.
What a recruiter looks for first
Before technical details, three pieces of information should appear at the top.
- The target role: "Java back-end developer", "React front-end developer", "Junior software engineer".
- Your level of experience in years or concrete situations (apprenticeship, internship, first job).
- Your main technology, the one matching the posting.
A CV opening with a list of twenty technologies makes the recruiter guess your specialism. Prioritise, as explained in our guide to the CV headline and job title.
The technical skills section: sort, do not stack
The technology list is the most consulted and worst written part. Three principles help.
Group by category. Languages, frameworks, databases, tools and DevOps, methods. It reads better than a run of comma-separated words.
Rank by real level. Put first what you use daily; flag what you have used occasionally. Avoid progress bars: "JavaScript 85%" means nothing and proves nothing.
Match the posting, honestly. If the vacancy asks for React and TypeScript and you use them, lead with them. If you do not know them, do not add them: technical tests and interviews will reveal it quickly.
Example section (fictional)
Languages: TypeScript, Python, SQL Front-end: React, Next.js, HTML/CSS Back-end and data: Node.js, PostgreSQL, REST APIs Tools: Git, Docker, GitHub Actions, Jest Practices: Scrum, code review, automated testing
Projects: proof that you can build
For a junior developer, the projects section often matters as much as experience. For an experienced profile it complements the work history. Each project should read in three lines.
| Element | Question to answer | Example (fictional) |
|---|---|---|
| Context | What is the project for? | Budget-tracking app for personal use |
| My contribution | What exactly did I do? | Designed the API, authentication, 40 automated tests |
| Stack | Which technologies? | React, Node.js, PostgreSQL, deployed with Docker |
| Result or link | What can be checked? | Public GitHub repository, live demo |
Practical tips:
- Include only projects you can explain in detail. You will be asked why you made a given technical choice.
- Give clean links (repository, demo) and check they work. A dead link leaves a poor impression.
- Prefer quality to quantity: three well-kept projects beat ten empty repositories.
- For team projects, state your real role.
A well-maintained public repository (clear README, readable commit history) is an excellent complement; see also our article on the CV and the LinkedIn profile for how to connect the two.
Experience: show impact, not a task list
"Developed new features" is vague. A technical lead wants to know the complexity, the team size and what improved. Use the structure: action verb + technical context + observable result.
| Weak wording | Stronger wording (fictional) |
|---|---|
| Developed new features | Added online payment to an e-commerce app (React, Node.js), integrated with a payment provider's API |
| Fixed bugs | Cut a page's load time from 3 s to 1.2 s by optimising SQL queries |
| Part of the team | Weekly code reviews within a team of five developers, set up CI with GitHub Actions |
| Maintained an application | Migrated 12 endpoints to a new API version with no downtime |
These figures are invented to show the form. In your CV, use only verifiable measures, and write "about" when a value is approximate. Our article on quantifying experience offers ways to recover that data.
Sample junior developer CV (fictional)
Sam Hadley, Manchester: Junior Full-Stack Web Developer
Profile: Computer Science graduate who completed a degree apprenticeship, with two web applications shipped to production (React, Node.js, PostgreSQL). Looking for a junior full-stack role contributing to product work in a team.
Skills
- Languages: TypeScript, JavaScript, Python, SQL
- Front-end: React, Next.js, CSS
- Back-end: Node.js, REST APIs, PostgreSQL
- Tools: Git, Docker, Jest
Experience
- Degree apprentice, web developer, digital services company, 2023-2026: built React and Node.js modules, took part in code review, fixed defects raised by support, introduced automated tests on a billing module
Projects
- Budget-tracking app (personal project): REST API, authentication, 40 tests, public repository and live demo
- Team project during studies (four people): room-booking platform, deployed with Docker
Education: BSc Computer Science (degree apprenticeship), 2023-2026 Languages: English (native), French (B1)
The CV is short, ranked and verifiable. The recruiter and the technical lead each find what they need.
Presenting a portfolio or code repository
A link to your work is an asset, provided it is ready to be read.
- A clear README for each project: what it is for, how to run it, which technologies.
- A readable commit history, with explicit messages rather than "fix" or "test".
- Tests where relevant: they show professional practice.
- A live demo for web projects, more telling than a screenshot.
- A selection, not a graveyard: pin three representative repositories, archive or hide the rest.
Avoid linking a repository containing keys, passwords or personal data. Check before sending your application. And if your work for an employer is confidential, describe the context and technologies without revealing internal information: a recruiter understands that kind of limit.
Junior, mid-level, lead: adjusting the level of detail
The same CV is not written the same way at every stage.
| Profile | Stress | Trim |
|---|---|---|
| Junior or apprentice | Projects, stack learned, placement or apprenticeship, curiosity | Detailed education, hobbies |
| Mid-level (3 to 8 years) | Team deliverables, technical responsibilities, measured impact | Abandoned technologies, small college projects |
| Lead or senior | Architecture choices, team support, results delivered | Exhaustive tool lists |
A mid-level or senior profile gains from telling what they decided and why, not only what they coded: technical trade-offs, debt reduced, mentoring younger developers. For the general presentation of achievements, our article on quantifying experience remains the foundation.
Preparing for the technical interview from your CV
Technical questions almost always target what is written. For each technology at the top of the list and each project cited, be ready to explain:
- the problem you had to solve;
- the choices you made and those you rejected;
- what you would do differently today;
- the limits of your solution.
This preparation is the best way to check that the CV is honest: anything you cannot explain does not belong on it.
Common mistakes
- Listing everything you have touched. A stack of thirty technologies suggests shallow knowledge.
- Forgetting the business context. A feature only makes sense for the user it serves.
- Neglecting readability. A layout loaded with colours and pictograms distracts.
- Including dead links. Test every link before sending.
- Sending the same CV everywhere. Adjust the lead technologies to the posting, as explained in our guide to tailoring your CV to a job posting.
- Copying terms you do not understand. Technical questions will expose it.
Checklist
- The target role and main technology are visible at the top.
- Skills are grouped and ranked, with no level bars.
- Each project has context, contribution, stack and a verifiable link.
- Experience shows measurable or observable impact.
- All links work.
- The CV fits one to two pages depending on experience.
Frequently asked questions
How many pages should a developer CV be?
One page for a junior profile, up to two for an experienced one. See our article on how long a CV should be for general benchmarks.
Should I put a GitHub link on my CV?
Yes, if your repository is well kept and representative. Otherwise feature one or two precise projects rather than an empty profile.
How do I show my level in a technology?
Avoid percentages. Use concrete markers: "used daily for three years" or "practised on a personal project".
Can a self-taught developer get hired?
Yes, if their projects and skills are verifiable. Our article on a CV without a degree gives a suitable layout.
Does a good CV guarantee a technical interview?
No. It maximises the clarity of your application, but the outcome depends on the vacancy, the competition and the conversations.
