Most skills sections fail for the same reason. They look like a word cloud someone copied from the job ad, with no proof, no order, and no signal of what the candidate is actually good at. A recruiter spending six seconds on your CV gets nothing from that.
The fix is not adding more skills. The fix is treating the section as evidence, not inventory.
Why the skills section matters more than you think
Two readers look at this section, and they read it very differently. The ATS reads it as a keyword bank — if the job posting asks for Kubernetes and Terraform, those exact words need to appear somewhere parseable. The human recruiter, two minutes later, reads it as a self-assessment of seniority. "Lists 18 tools, knows three deeply" is a pattern they spot instantly.
You are writing for both. Get the keywords in so you pass the filter, and prioritise the ones that match the job so the human stops scanning.
What to actually put in there
Group by category, not by skill level. "Proficient / Intermediate / Beginner" reads as a guess and gives the reader nothing they can verify. Categories give structure and let you order by relevance.
A cleaner layout for a backend role:
- Languages: Python, Go, TypeScript
- Infrastructure: AWS (EC2, S3, Lambda), Docker, Terraform
- Data: PostgreSQL, Redis, ClickHouse
- Practices: CI/CD, code review, on-call rotation, incident response
Four categories, ten to fifteen items total. Each one a recruiter or hiring engineer can name in a follow-up question. If a skill is on your list and you would be uncomfortable being asked about it in an interview, it is not on your list.
Hard skills vs soft skills — where each belongs
Hard skills are tools, methods, languages, and certifications. They go in the skills section because they are scannable and keyword-matchable. "PostgreSQL" is a hard skill. "Mentoring junior engineers" is not — it is a soft skill, and it belongs in the experience bullets where you can show it doing real work.
The rule of thumb: if you cannot prove the skill with a bullet under a job, it has no business in the experience section. If it is not a keyword someone would search for, it has no business in the skills section.
Soft skills as a standalone list ("communication, leadership, teamwork") are filler. Every CV has them, none of them are differentiating, and a recruiter has stopped reading by item three.
Skills to put on a CV — the prioritisation rule
Open the job posting. Read the requirements section twice. The skills your CV needs are, in this order:
- Every required skill you actually have, named the way the posting names them. If they say "AWS", say "AWS". If they say "Amazon Web Services", say that.
- Two or three preferred-but-not-required skills you have, especially the ones that signal seniority.
- Two adjacent skills that show range without padding (a backend role posting that asks for Python can fairly mention you also work in Go).
Everything else gets cut. A skills section that matches the posting closely outperforms a longer, generic one — both for the ATS and the human.
Format that survives an ATS
The parsing rules here are not complicated. Plain text, in a single column, in the body of the document. No icons, no progress bars, no charts. The five-dot rating system that looks elegant in a Canva template is unparseable — it shows up in the recruiter's ATS as five black squares next to a word.
The Postulit team has parsed thousands of CVs into our LinkedIn-to-CV builder, and the pattern is consistent: clean text in categories beats anything visual. If you want to see how your current skills section parses, run it through any free ATS-check tool and look at the raw output.
Common mistakes to fix tonight
If your skills section ends with "and more", delete "and more". You are not selling kitchen knives.
A few patterns worth checking:
- Stuffing keywords you cannot defend — listing GraphQL because you read an article about it last week. Interviewers will catch this in twenty seconds.
- Skill levels with no calibration — your "advanced" Python is someone else's intermediate. Drop the labels and let the experience bullets do the calibrating.
- The same eight soft skills as every other CV — if you have to include them, weave them into bullets with proof.
- Tools nobody uses anymore — Flash, Silverlight, jQuery as a top-line skill in 2026. It dates the CV.
A working example
For a mid-level data analyst applying to a fintech role:
- Analysis & modelling: SQL (PostgreSQL, Snowflake), Python (pandas, scikit-learn), A/B testing
- Visualisation: Looker, Tableau, dbt
- Domain: payment fraud signals, KYC funnels, cohort retention
- Workflow: Git, dbt models in production, Airflow scheduling
Four categories, twelve items, every one defensible in interview. Each line maps to something you can imagine the candidate having done. That is what a strong skills section looks like.
Build the skills section last. Write the experience bullets first, then look at what you proved, then list the skills that those bullets back up. The order matters — written the other way around, the list always grows beyond what the experience can support.