Skills in a resume often look like a short list of words: Excel, communication, Python, responsibility, CRM, teamwork. The problem is that such a list proves almost nothing. It is important for an employer not just to see the name of a skill, but to understand if the candidate can actually apply it to their work.
Hard skills and soft skills perform different functions. Hard skills show what a person can do technically or professionally. Soft skills show how they work: how they communicate, make decisions, react to changes, collaborate with a team, or explain complex things in simple terms. In a modern resume, these two types of skills should not compete with each other. They should complement one another.
The European ESCO classification describes a skill as the ability to apply knowledge and know-how to perform tasks and solve problems; ESCO also distinguishes skills/competences from knowledge concepts in its classification of skills. This is important for a resume: a skill is not just a word, but the ability to perform a specific action in a specific context.
What are hard skills
Hard skills are professional, technical, or subject-specific skills that can be relatively clearly described, taught, verified, and applied to a specific task. These include programming languages, analytics tools, accounting standards, CRM systems, research methods, foreign languages, working with equipment, legal procedures, medical protocols, or design software.
For example, for a developer, hard skills might be TypeScript, Git, PostgreSQL, Docker, Next.js, or automated testing. For a marketer — Google Analytics, Meta Ads Manager, SQL, A/B testing, or reporting. For an accountant — Excel, SAP, tax reporting, financial analysis, or XBRL.
The main feature of a hard skill is that it can be verified through action. If a candidate writes that they know SQL, they can be given a data retrieval task. If they specify Figma, one can look at a file or portfolio. If they indicate English at a B2 level, this can be verified through an interview or a certificate.
What are soft skills
Soft skills are behavioral, communication, and interpersonal skills. They show how a person works with other people, information, conflicts, changes, and responsibility. These include communication, critical thinking, adaptability, teamwork, leadership, empathy, independence, attention to detail, time management, and decision-making.
UNESCO-UNEVOC describes soft skills as non-cognitive, interpersonal, and personal skills that help a person act effectively in a professional and social environment. ESCO also separately distinguishes transversal skills as part of the skill classification, meaning skills that can be useful in different professions and contexts.
Soft skills are harder to verify with a simple test. If a candidate writes "communicative," this proves nothing. But if they write "conducted demos for clients, coordinated requirements between sales and product teams, reduced the number of revisions in technical specifications," then the soft skill becomes visible through action.
How to quickly distinguish hard skills from soft skills
The simplest rule is: if a skill can be called a tool, technology, language, method, standard, certification, or specific operation — it is most likely a hard skill. If a skill manifests through behavior, work style, interaction, thinking, or decision-making — it is a soft skill.
"Excel" — hard skill. "Attention to detail" — soft skill. "Salesforce CRM" — hard skill. "Ability to build trust with a client" — soft skill. "Python" — hard skill. "Critical thinking" — soft skill. "English B2" — hard skill, because the language level can be verified. "Ability to explain complex things simply" — soft skill, because it is visible through communication.
But the line is not always perfect. For example, "project management" can contain hard skills — Jira, Scrum, sprint planning, budgeting — and soft skills: facilitation, negotiations, conflict management. Therefore, in a resume, it is better not to write a general "project management," but to break it down into specific actions and results.
Why a simple list of skills does not work
A list of skills without context does not show the level of proficiency. Two candidates can write "Excel," but one only knows how to make simple tables, while the other works with pivot tables, Power Query, XLOOKUP, and financial models. The same goes for soft skills: "teamwork" can mean anything from participating in daily meetings to coordinating several teams in a complex project.
Work.ua in its resume recommendations advises to specify skills and not to write vague formulations like "confident PC user," but to indicate specific programs and tools. This rule works not only for the Ukrainian market. For ATS and recruiter searches, it is important to use the same keywords as those in the job description: names of technologies, programs, methods, languages, and professional processes.
Bad: "responsible, communicative, fast learner."
Better: "coordinated communication between the client and the development team, prepared short status updates, and helped reduce the number of repeat clarifications for tasks."
Bad: "knowledge of CRM."
Better: "Salesforce CRM: managed client base, updated deal statuses, prepared pipeline reports."
Bad: "analytical thinking."
Better: "analyzed campaign data in Google Analytics and Looker Studio, found pages with high drop-off, and prepared recommendations to improve conversion."
How to evaluate your hard skills before writing a resume
Before adding a hard skill to a resume, you should answer three questions. First: have you used this skill in a real task? Second: can you explain your level of proficiency with the tool or method? Third: is there a result that confirms the application of this skill?
For example, do not write "Python" if you have only completed a few lessons and cannot write a simple script on your own. It is better to write "basic Python: CSV processing, simple scripts for automation." This is more honest and accurate.
For hard skills, it works well to use a gradation by level: basic, working, confident, advanced. But these levels must be explained by action. "Confident Excel" sounds weaker than "Excel: pivot tables, Power Query, XLOOKUP, financial reports." "Intermediate SQL" sounds weaker than "SQL: JOIN, GROUP BY, CTE, data filtering and aggregation for reports."
How to evaluate your soft skills
Soft skills should be evaluated not by how you see yourself, but by how these skills manifested in your work. If you want to write "communication," recall situations where you explained something, coordinated, presented, resolved a conflict, or helped others understand complex information.
If you want to write "leadership," show not a status, but an action: trained newcomers, coordinated a team, took responsibility for results, moderated meetings, helped make decisions. If you want to write "adaptability," show a change of context: a new market, a new tool, an urgent launch, changing requirements, a transition to a different role.
Soft skills are better presented through examples in your experience rather than a separate long list. In the "Skills" section, you can leave a few most relevant soft skills, but the main proof should be in the experience description.
How employers verify hard skills
Hard skills are most often verified through test tasks, technical interviews, portfolios, certificates, work examples, or work samples. OPM describes work sample tests as tasks in which the candidate performs work activities similar to those performed in the position.
For a developer, this can be a coding task or live coding. For a designer — a portfolio and explanation of solutions. For a marketer — campaign analysis or creating a report structure. For an accountant — a case with financial data. For customer support — a response to a complex client request.
This is why hard skills in a resume should be formulated so that they can be verified. Not "know analytics," but "Google Analytics 4, Looker Studio, UTM-tagging, analysis of traffic channels." Not "able to work with documents," but "contractual documentation, invoices, acts, primary accounting."
How employers verify soft skills
Soft skills are usually verified through structured interviews, behavioral questions, situational cases, assessment centers, role-playing exercises, and references. OPM notes that structured interviews use rules for obtaining, observing, and evaluating answers, and a higher level of structure is associated with higher validity, reliability of assessors, and less dependence on subjectivity.
A structured interview differs from "just talking." In it, all candidates are asked the same or comparable questions, and answers are evaluated against pre-defined criteria. OPM also describes a structured interview as a method of assessing job-related competencies through questions about past experience or hypothetical work situations.
For example, to verify communication, they might ask to describe a situation where the candidate explained a complex topic to a non-technical audience. To verify conflict management, they might ask about a case of disagreement within a team. To verify critical thinking, they might provide an ambiguous case with incomplete data.
How to properly present hard skills in a resume
Hard skills should be presented as concretely as possible. In the "Skills" section, you can group them by categories: programming languages, tools, analytics, CRM, design, management, languages, certifications. But there is no need to turn the resume into a warehouse of 40–60 keywords. Better 8–15 relevant skills that directly correspond to the vacancy.
For an IT role, this might look like: "TypeScript, React, Next.js, Node.js, PostgreSQL, Git, Docker, REST API." For a marketer: "Google Analytics 4, Google Ads, Meta Ads, Looker Studio, A/B testing, SEO basics, CRM." For a financier: "Excel, Power Query, SAP, financial reporting, budgeting, cash flow analysis."
Important: if a skill is critical for the vacancy, it should be not only in the "Skills" section but also in your experience. An ATS might find the keyword, but a recruiter must see proof. For example, if the job requires Salesforce, do not limit yourself to the word "Salesforce" in the list. Add to your experience: "managed pipeline in Salesforce, updated deal statuses, and prepared weekly reports for the sales lead."
How to properly present soft skills in a resume
Soft skills should not be presented as a set of abstract adjectives. "Responsible," "stress-resistant," "communicative," "punctual" — these are weak formulations if they have no proof. It is better to show soft skills through situations, actions, and results.
Instead of "communicative," write: "conducted product presentations for clients and passed their requirements to the development team." Instead of "leadership qualities" — "mentored two junior specialists and helped them pass code reviews without repeat errors." Instead of "stress-resistant" — "worked with urgent client requests during peak periods and adhered to SLAs."
Soft skills work best in bullet points under your experience. There, they do not look like self-promotion, but become part of a professional result.
The formula for a strong formulation
For most skills, a simple formula works: skill plus context plus action plus result.
For example: "SQL: created queries to analyze user behavior and helped the team find pages with the highest bounce rate."
Or: "Communication with clients: conducted onboarding calls, explained product functionality, and reduced the number of repeat inquiries to support."
Or: "Excel and Power Query: automated the monthly report, reducing manual preparation from several hours to one data update."
Such a formulation is better than a dry list because it immediately answers the employer's question: where exactly did the candidate apply the skill and what did it yield.
Typical mistakes in describing skills
The first mistake is writing too generally. "PC," "CRM," "analytics," "marketing," "communication" do not provide enough information. You need specific names of tools, methods, and tasks.
The second mistake is adding irrelevant skills. If the vacancy does not require Photoshop, you shouldn't put it in the first place just because you once used it. The resume must correspond to a specific role.
The third mistake is exaggerating your level. If a skill is easy to verify, an exaggeration will quickly become a problem during a test task or interview.
The fourth mistake is writing only hard skills. Such a resume might look technically strong but does not show how the candidate works with people, deadlines, changes, and responsibility.
The fifth mistake is writing only soft skills. Such a resume might sound pleasant, but it does not show professional suitability for a specific role.
How to adapt skills to a vacancy
Before updating your resume, you need to read the vacancy carefully and write down repetitive requirements. Separately, you should mark tools, technologies, methods, languages, types of tasks, and behavioral expectations. Then these words should be matched with your actual experience.
If the vacancy says "Google Analytics 4," it is better to write exactly "Google Analytics 4" rather than just "web analytics." If "customer support," "Zendesk," and "written communication" are specified, your resume should contain these relevant formulations if they correspond to real experience.
You don't need to mechanically copy the entire job description. You need to take those key skills that are actually in your experience and confirm them with examples.
Conclusion
Hard skills answer the question "what can you do." Soft skills answer the question "how do you do it." A strong resume shows both types of skills, but not in the form of an empty list, rather through specific tools, tasks, context, and result.
The best strategy is to first analyze the vacancy, then select relevant hard and soft skills, and after that, add proof to your experience. If a skill is important, it should not only be named but also confirmed by action. That is how a resume becomes not a set of beautiful words, but an argument in favor of the candidate.