Writing · 2026-08-10 · 13 min read
Hard Skills and Soft Skills on a CV: How to Balance and Prove Them
Learn which technical skills to list, how to prove soft skills through achievements, and how to satisfy ATS and recruiters.
A strong CV does not choose between hard and soft skills. It combines them so an employer understands what you can do and how you deliver results with other people. Hard skills enable verifiable tasks such as programming, analysing data, closing accounts, or operating machinery. Soft skills describe behaviours such as prioritising, communicating, leading, negotiating, and adapting. The problem begins when both become a list of unsupported labels.
The most useful rule is simple: list relevant technical capabilities and prove soft skills inside achievements. “SQL, Python, and Tableau” provides concrete terms an ATS can recognise. “Excellent communication and leadership” offers no evidence. By contrast, “presented a new forecasting model to executives and coordinated adoption across four teams” demonstrates communication, influence, and collaboration while keeping the professional outcome central.
What really separates a hard skill from a soft skill
A hard skill is generally learned through specific education or practice and can be checked through a test, qualification, portfolio, or output. Examples include programming languages, software, methods, languages, clinical techniques, legal rules, and industrial processes. Proficiency matters: writing JavaScript after modifying one tutorial is misleading. Indicate depth through projects, recent years of use, or particular functions, and avoid ambiguous progress bars.
A soft skill is a transferable behaviour affecting how you work. It is not less important or impossible to assess; it simply needs contextual evidence. Interviews explore how you resolved conflict, prioritised under pressure, or persuaded a stakeholder. On the CV, proof sits in the verb, situation, and result. Avoid presenting soft skills as permanent personality traits. “Introvert” or “extrovert” reveals much less than a relevant action.
How to select hard skills for the role
Start with the posting and group technical terms into mandatory tools, industry knowledge, methods, languages, and certifications. Compare them with your honest inventory. Use exact matches where naming is standard: “Amazon Web Services (AWS)” can appear once to cover the full name and acronym. Add transferable skills when they clarify readiness, but do not bury five central requirements below thirty technologies touched years ago.
- Data: SQL, Python, R, Power BI, Tableau, modelling, statistics, ETL, and data quality, limited to your genuine experience.
- Marketing and sales: Google Ads, GA4, SEO, HubSpot, Salesforce, automation, negotiation, and pipeline analysis.
- Product and design: discovery, user research, Figma, prototyping, roadmaps, product metrics, and accessibility.
- Finance and operations: IFRS, reconciliation, forecasting, SAP, procurement, Lean, inventory control, and process improvement.
- Technology: languages, frameworks, cloud, databases, testing, CI/CD, observability, cybersecurity, and architecture.
- Regulated professions and trades: current licences, clinical procedures, regulations, equipment, techniques, and safety.
Organise the list so it scans in seconds. “Technologies: Python, Django, PostgreSQL, Docker, AWS” is more useful than a tag cloud. Omit Microsoft Office when basic digital ability is assumed, unless the role requests advanced Excel and you can specify what that means. Remove obsolete tools that do not support your target. For languages, use recognisable standards such as C1 or advanced professional proficiency instead of visual stars an ATS cannot interpret.
Prove soft skills with action, context, and result
Choose a requested behaviour and find a real moment when it affected an outcome. Then write action, context, and consequence. For leadership: “Coordinated six Engineering and Support colleagues through a critical migration; completed the change without downtime and one week early.” For communication: “Translated technical analysis into a weekly executive dashboard, reducing review meetings from 90 to 30 minutes.”
Evidence does not require a management title. A junior candidate demonstrates initiative by finding an error, proposing an improvement, or documenting a process. A student can show collaboration through a project with roles, deadline, and deliverable. Someone returning to employment may use relevant volunteering or freelance work. The key is not claiming all the credit: state your contribution precisely and recognise the team context through verbs such as collaborated, facilitated, and coordinated.
- Leadership: show a decision, people coordination, obstacle removed, or colleague developed, not only team size.
- Communication: identify the audience, complexity translated, and change achieved, such as approval, adoption, or fewer errors.
- Teamwork: name the functions that collaborated and what they delivered together; “team player” alone means nothing.
- Adaptability: describe a transition, unexpected priority, or new tool and how you protected quality or schedule.
- Problem-solving: provide diagnosis, action, and root cause removed instead of the generic “resolved issues.”
- Organisation: prove volume, competing priorities, SLA performance, or fewer delays rather than writing “highly organised.”
Before and after: turn adjectives into evidence
Before: “Strong leadership, communication, creativity, and ability to work under pressure.” After: “Facilitated workshops with Sales, Product, and Legal to redesign onboarding; secured approval in two weeks and reduced early-stage abandonment by 18%.” The new statement demonstrates at least four soft skills without naming each one. It also supplies functions, scope, and outcome that give the recruiter useful interview questions.
Another example. Before: “Resourceful and adaptable professional.” After: “Rebuilt the supplier schedule after a stock shortage, secured alternatives within 48 hours, and maintained 96% on-time delivery.” You do not need to say you solve problems; the action demonstrates it. If exact numbers are unavailable, retain specificity: “prevented cancellation of the launch” or “delivered before the regulatory deadline” are understandable consequences.
What ATS systems and recruiters prefer
An ATS works best with concrete names and plain text. It may search for “project management,” “Agile,” “Scrum,” or “stakeholder management,” but it cannot independently establish whether you lead well. Include truthful job-ad keywords in context and maintain a readable skills section. Do not hide terms, repeat them twenty times, or rely on graphics as the only indication of level. Selectable text and standard headings improve extraction.
The recruiter looks for credibility and relevance. A list of twenty soft skills reads like self-rating; two well-chosen achievements provide observable signals. Recruiters also test consistency. If you claim attention to detail while the CV contains errors, the claim works against you. If you state executive communication, your summary should be clear. The document itself can reinforce or contradict the capabilities you declare.
Recommended balance by career stage and profession
In technology, data, finance, healthcare, and skilled trades, hard skills usually need a visible section because they act as filters. Soft skills appear mainly through achievements. Sales, management, HR, and customer success require a more even balance, but still need tools, methods, and metrics. Junior candidates can use projects and education to support technique while real activities prove collaboration and initiative. Executives should compress old technical lists and emphasise decisions, scale, and impact.
- Reserve one compact section for prioritised hard skills, commonly eight to fifteen relevant items.
- Distribute three to six important soft skills across the summary and achievements without creating a duplicate list.
- Adjust weight to the vacancy: a specialist needs technical depth; a manager must also demonstrate scale and influence.
- Connect skills to recency. A platform used this week carries more weight than one touched once ten years ago.
- Add a portfolio, GitHub profile, certification, or project when it verifies an important capability without crowding the CV.
Common mistakes and a ten-minute review
Avoid subjective levels such as five stars, percentages without a method, and buzzwords such as “ninja.” Do not list every tool you know or capabilities you do not want to use in your next job. Never send exactly the same list to every vacancy. Review the ad, mark six priority hard skills and three soft skills, check where each is proven, and remove any term you could not defend with a specific example.
ClarCV lets you upload a PDF or Word CV and use AI analysis to identify unclear skills, weak achievements, and structural issues. You can prepare English or Spanish versions with ATS-friendly templates. AI helps generate questions and wording alternatives; you confirm that every capability and result is true. Pro is transparently priced at €7 per month, useful when comparing versions without turning the CV into a generic keyword list.
Frequently asked questions about CV skills
FAQ
How many skills should I put on my CV?
There is no universal number, but eight to fifteen relevant hard skills is usually scannable. Prove three to six soft skills through achievements. Prioritise quality, fit, and recency over volume.
Should I create a separate soft-skills section?
Usually not. It may help on a form that explicitly asks for one, but a CV is more persuasive when those behaviours appear in the summary and experience. A standalone list provides little proof.
How should I show technical proficiency?
Use verifiable context: functions performed, projects, recent years, certifications, or features mastered. “Advanced Excel: Power Query and data models” communicates more than an 85% bar based on no defined standard.
What if the job requests a skill I am learning?
Be transparent. Place it under “Currently learning” or describe the practical project and expected completion date. Do not mix it with mastered capabilities. An honest transition may interest an employer; an inflated claim will fail a technical test.
Are languages hard skills?
Yes. They are learned and assessable capabilities. Give a recognised level and, when useful, professional context such as “English C1, weekly client negotiations.” Avoid “intermediate” when you can provide a clearer reference.