Tech CV: The Format Recruiters Expect (Stack, Projects, GitHub)

The tech industry has its own standards: a developer, DevOps engineer, or data analyst CV is often reviewed by a non-technical recruiter first, then validated by a technical lead, after passing through an ATS. This triple filter requires a specific format: skills organised by categories, projects described with context and results, and verifiable links to your GitHub or portfolio. Pour en savoir plus sur la présentation de vos compétences, consultez notre guide sur comment choisir et présenter ses compétences. Here's the expected format, section by section.

Technical Stack: Organise Without Inflating

The skills section is the first thing a technical recruiter scans. Organise your stack by categories rather than alphabetically or personal preference: languages, frameworks and libraries, databases, tools and platforms, methodologies. This arrangement allows a ten-second scan, both by a busy human and by an ATS looking for exact matches.

• Languages: Python, TypeScript, Java, Go, with realistic levels, from intermediate to expert.
• Frameworks: React, Next.js, Spring Boot, FastAPI, according to your specialisation.
• Data and infrastructure: PostgreSQL, Redis, Docker, Kubernetes, AWS or GCP.
• Methods: Git, CI/CD, automated testing, code review, agile Scrum.

Golden rule: only include what you can defend in a technical interview. A list of thirty technologies at 'basic' level inspires less confidence than a list of ten mastered skills, with supporting evidence in your projects.

Projects and Achievements: The Heart of a Developer CV

In tech, your achievements matter more than your job descriptions. Describe each significant project using a mini-template: context, scope, stack, measurable result. A technical lead wants to know what you built, with what, and how it changed things for the business or users.

1. 1Context: refactoring the billing system for a 60-employee fintech.
2. 2Role: back-end developer, designing the API and data migrations.
3. 3Stack: Node.js, PostgreSQL, Redis, Kubernetes deployment.
4. 4Result: processing time reduced by three-fold, zero major incidents since production.

For junior profiles, personal projects, open source contributions and academic projects legitimately occupy this space: two well-documented projects are better than a summer job described in administrative tasks.

GitHub, Portfolio and External Proof

A GitHub link catches technical recruiters' attention, for better or worse. Before adding it, check what it shows: organised repositories, READMEs explaining the why and how, a pinned profile with your three best projects. An empty account or one filled with forks without contributions works against you. If your professional work is private, create a clean personal project that demonstrates your coding approach: tests, regular commits, documentation.

The Format ATS and Recruiters Expect

For presentation, stay simple: one column, clear headings, no skill assessment charts that ATS systems can't read. Découvrez comment rendre votre CV compatible avec les systèmes ATS. Use keywords from the job description when they match your experience: if the ad mentions CI/CD, Kubernetes and TypeScript, these terms must appear in your CV, phrased exactly as written. Apprenez à repérer et placer les mots-clés d'une offre d'emploi dans votre CV. A clear job title at the top of the document, such as full-stack TypeScript developer, helps the recruiter categorise you immediately and effortlessly.

A compelling tech CV doesn't claim to know everything: it proves, with three technologies and three projects, that you know how to deliver production-ready software. Pour éviter les erreurs de CV qui font fuir les recruteurs, suivez ces recommandations.