How to Customize Sections: Skills, Projects, and More
On this page
A strong CV is structured around signal: the fastest proof that you fit the role. This guide helps you decide which sections to include and how to keep them relevant.
Skills section: keep it curated
Good skills sections:
- match the job’s core requirements
- include only skills you can defend
- group logically (e.g., Languages, Data, Cloud, Tools)
Avoid:
- long keyword lists
- mixing advanced skills with “touched once” tools
Related: /docs/how-to-avoid-keyword-stuffing
Projects section: use it for proof
Projects are powerful when:
- you’re early-career and need more proof
- you’re switching role types and need bridging evidence
- you built something directly relevant to the role
A good project entry includes:
- what you built
- the tools you used
- the outcome or metric
Optional sections (use only if they add signal)
- Certifications (if relevant to the role)
- Publications (for research/academic roles)
- Languages (for global roles)
- Links (portfolio, GitHub, LinkedIn)
Section prioritization rule
Ask: “If someone only reads 20 seconds, what do I want them to see?”
Put those sections and bullets first.
Template considerations
Templates may place sections slightly differently. Choose a template that:
- keeps the most important sections near the top
- stays clean and readable
FAQ
Should I always include projects?
Not always. If your work experience already provides strong proof, projects can be optional.
Can I tailor skills without claiming new skills?
Yes—tailoring is about emphasis and ordering, not inventing skills.