What is the difference

A hard skill is a thing you can demonstrate on request: a language, a tool, a certification, a procedure. A soft skill is a pattern in how you work, which only shows in an account of something you did.

Should soft skills go in the list

One or two at most, and only where they are genuinely part of the trade. A list of eight character adjectives crowds out the tools and tells a reader nothing they can check.

Where does teamwork go

In a line about a piece of work that needed it. Mentoring three engineers through their first release is teamwork with a fact attached.

Does the checker distinguish the two

No. It counts entries under a recognised skills heading and it cannot tell a programming language from an adjective. The distinction matters to the person reading, and that is reason enough.

What about languages I speak

Those are hard skills with a level attached, and the builder gives them their own section so the level stays beside the language.

Guide · Résumé

Hard skills and soft skills on a résumé

One kind of skill can be listed and checked. The other has to be shown. Here is where each belongs on the page, and why a list of adjectives persuades nobody.

ConxfolioPublished 2026-09-12

— show the soft ones, do not claim them.

The distinction is simpler than the debate around it. A hard skill can be demonstrated on request. A soft skill can only be inferred from something you did. That difference decides where each one belongs on the page.

Hard skills go in the list

Tools, languages, systems, equipment, procedures, regulations, certifications. They are checkable, which is what makes them worth listing: a reader scanning for one word can find it, and an interviewer can ask you to prove it. The skills section guide covers how many to list and how to separate them so a parser reads them as entries.

Soft skills go in the evidence

"Communication" as a list item is a claim about yourself. "Wrote the on-call runbook the team still uses" is the same claim with something behind it. "Leadership" is an adjective. "Led the migration of fourteen services from a shared monolith to independent deployments" is the thing itself.

A reader who has seen four hundred résumés has seen "team player" four hundred times and has never once been able to check it. The sentence about the runbook they remember, because it describes an event.

Why the list of adjectives persists

Because job postings ask for those words, and it feels safer to mirror the posting than to trust the evidence. The trouble is that everyone mirrors it, so the mirroring carries no signal. Where a posting asks for collaboration, the strongest answer is a line in your experience section where collaboration visibly happened, and the second strongest is a cover letter paragraph that quotes it.

What a parser can see

Nothing about this distinction. The ATS checker counts entries under a recognised skills heading and passes the check at three. It cannot tell PostgreSQL from "detail-oriented", and it makes no attempt to. The check measures whether the structure and the evidence are readable, which is a different question from whether the list is any good.

That limit is worth stating plainly, because a great deal of advice implies that some hidden system is grading your skill words. Here, nothing is. The reason to drop the adjectives is that a person will read the page.

The exception

In some trades a so-called soft skill is the trade. Negotiation for a buyer, de-escalation for a support lead, safeguarding for a teacher, bedside handover for a nurse. Name it, then attach the setting and the volume, and it stops being an adjective and becomes scope.

Sorting it in the builder

Open the résumé builder and read your list. Move anything that describes your character into a line in the experience section where it actually happened, and delete it if no such line exists. Languages and certifications have their own sections under Add content, so they do not have to compete for room on the main list. What remains is a list of things you could be tested on, which is the only kind of list worth printing.

Translating an adjective into evidence

The practical move is mechanical. Take each character word on your list and ask when it was last true in a way somebody else noticed. "Organised" becomes the rota you rebuilt. "Resilient" becomes the quarter you covered two roles. "Analytical" becomes the report that changed a decision. Write that line in the experience section, then delete the adjective. The page gets shorter and gains a fact.

Where no such moment comes to mind, the adjective was decoration, and deleting it costs you nothing at all. That is worth saying plainly, because the fear of deleting these words is what keeps them on the page.

What the letter can carry that the list cannot

Some of this belongs in a letter rather than on a résumé. The cover letter builder reads your résumé and the posting together and builds each paragraph out of sentences your own document already contains, carrying every one with the line it came from. Where the posting asks for something your evidence does not support, it lists that as a gap instead of asserting it. So the way to answer a posting that asks for collaboration is to have the collaborative work written down as work, where both the letter and the reader can find it.

Skills the posting names that you half have

Where you have used something once or shallowly, say so with a word rather than listing it flat or leaving it out. "Terraform, on two projects" is accurate, it is checkable, and it is a better opening for an interview than a flat entry you have to qualify under questioning.

Sort them in the editor

The skills section holds the list. The experience section holds the proof for everything a list cannot carry.

Open the résumé builder See the skills guide

Questions

What is the difference: A hard skill is a thing you can demonstrate on request: a language, a tool, a certification, a procedure. A soft skill is a pattern in how you work, which only shows in an account of something you did.
Should soft skills go in the list: One or two at most, and only where they are genuinely part of the trade. A list of eight character adjectives crowds out the tools and tells a reader nothing they can check.
Where does teamwork go: In a line about a piece of work that needed it. Mentoring three engineers through their first release is teamwork with a fact attached.
Does the checker distinguish the two: No. It counts entries under a recognised skills heading and it cannot tell a programming language from an adjective. The distinction matters to the person reading, and that is reason enough.
What about languages I speak: Those are hard skills with a level attached, and the builder gives them their own section so the level stays beside the language.

Conxfolio is a free set of four career tools: a résumé builder with 37 rendered layouts, an ATS résumé checker that prints its own arithmetic, a cover letter builder that traces every proof paragraph back to the line it came from, and a portfolio builder with 20 authored designs. There is no account to create, nothing is held back for a paid plan, and no language model is used anywhere in the product, so the readers, the score and the letter are deterministic code you can check.