Hard Skills vs. Soft Skills on a Resume: Examples and Evidence
Understand hard and soft skills, choose relevant examples and support both with real work. Includes fictional before-and-after bullets and a job-posting checklist.
On this page
Hard skills usually describe specific tools, methods or knowledge; soft skills describe aspects of how you work, communicate and solve problems. Both can matter in a role, and both benefit from evidence. There is no reliable rule that one category gets you past software while the other wins an offer.
Use this guide to choose relevant skills, decide where to put them and write examples from your actual experience. The sample bullets are fictional illustrations, not achievements to copy or evidence of hiring results.
What the distinction means, and where it overlaps
Hard skills is a common label for task-specific knowledge and techniques, such as writing SQL queries, building a financial model or using a particular application. Naming a tool is useful, but it does not establish your level of competence.
Soft skills commonly refers to interpersonal and working skills, such as communication, collaboration or adaptability. They can be learned and assessed too; they are not simply personality traits. Some work combines both categories, such as technical writing or managing a complex project.
The labels are shorthand rather than a universal taxonomy. O*NET’s transferable-skills framework separates categories such as social and technical skills, while its software-skills resource identifies applications used for work. For a resume, the important question is what the role needs and what you can support.
A quick reference list
These are examples, not rankings of current demand or a checklist for every application. Some skills cross the two columns depending on the task.
| Task-specific examples | Interpersonal or working-skill examples |
|---|---|
| SQL queries or Python programming | Explaining an analysis to another team |
| Using a CRM platform | Coordinating a customer handoff |
| Financial modeling | Discussing assumptions and uncertainty |
| Campaign measurement | Working through feedback |
| Cloud infrastructure configuration | Coordinating incident response |
| Spreadsheet analysis | Planning and prioritizing work |
| Technical documentation | Adapting information for an audience |
| Project scheduling or a planning tool | Facilitating decisions and resolving disagreements |
Choose skills by responsibility, not a fixed ratio
There is no universal hard-to-soft skill ratio or ideal number of terms. Read the vacancy for actual responsibilities and required qualifications, then select the evidence most relevant to them. A technical role may still need clear communication, and a customer-facing role may require specialized systems knowledge.
A compact skills section can make tools and methods easy to find. Experience or project bullets can explain how you used them and worked with others. You can name a relevant interpersonal skill in a summary or skills section when useful, but avoid a long unsupported list.
| Role area | Possible task evidence | Possible working-skill evidence |
|---|---|---|
| Software engineering | A system, feature or test you implemented | How you reviewed changes or coordinated a handoff. |
| Data analysis | A query, model or dashboard you built and checked | How you explained assumptions and limitations to the audience. |
| Marketing | A campaign or content deliverable with your contribution | How you incorporated feedback or coordinated contributors. |
| Sales | Accurate account or pipeline responsibilities | How you clarified needs and handled an objection. |
| Project or product work | A plan, decision record or relevant tool workflow | How you coordinated dependencies and escalated risks. |
| Healthcare | Relevant qualifications and work within your actual scope | How you communicated or coordinated care without disclosing patient details. |
Use the table to generate examples, not to infer what every employer values most. Repetition in a posting can draw your attention, but it does not establish a hidden weight or make a preference a mandatory qualification. Read the stated requirements in context.
What keywords can and cannot tell you about screening
Recruiting systems have different features and configurations. Greenhouse documents full-text Boolean search, including ways to search variations of text. This supports using clear, recognizable terms, but it does not establish that all ATS products use an identical exact-match gate or ignore interpersonal skills.
If you used Python, naming Python is clearer than saying only “scripting.” If you used another language, do not rename it to match the vacancy. Expand an unfamiliar acronym when it helps understanding, without repeating every phrase purely to raise a score.
A keyword or match report is a review aid, not proof of a recruiter’s selection rules. See our keyword guide for ways to connect terms to actual work.
Support both kinds of skill with specific work
A useful bullet explains an action and enough context for the reader to understand your contribution. That may include a tool, the people involved, a decision or an outcome. A measurable result is helpful when accurate, but it is not required in every bullet.
Try action + relevant context + result or deliverable, if known. Do not claim that a sentence proves competence conclusively. It gives an employer evidence to explore further.
Fictional before-and-after examples
- Vague: “Excellent communicator and team player.”
- More specific: “Coordinated weekly reviews with engineering, design and support, recorded decisions and tracked unresolved questions for the feature launch.”
- Vague: “Strong problem-solving skills.”
- More specific: “Reproduced a checkout error in a test environment, traced it to input handling and added a regression test with the fix.”
- Vague: “Adaptable under pressure.”
- More specific: “Revised the campaign schedule after the budget changed, confirmed priorities with the lead and documented which activities were deferred.”
These examples add observable work without inventing revenue gains or percentages. For a real application, use your own task and responsibility. “Coordinated” should not replace “assisted” if you did not lead the coordination.
If you have a measured outcome, state what changed, over which period and how your contribution relates to it. A team’s increased revenue is not automatically the result of your model or campaign. If causation is unclear, describe the deliverable and the observed result separately.
A technical skill also benefits from context: “Built a dashboard in Power BI using reviewed source data” is more informative than naming the product alone. Include a work sample only when you have permission to share it.
Examples of technical skills to check against a vacancy
The lists below illustrate categories you might encounter. They are not a survey of the most requested skills, and you should not add them all. Select tools and methods you actually know and can explain.
Technical-role examples
- Programming languages you have used, such as Python, JavaScript, Java, Go or TypeScript.
- Cloud or infrastructure platforms and tools, with your actual deployment or configuration responsibilities.
- Data work such as SQL queries, data modeling, pipelines or reporting.
- Version control, automated delivery or infrastructure-as-code work you can describe.
- An API or framework used in a specific project, rather than a list of names from a tutorial.
- Testing and monitoring methods, with the checks or investigations you performed.
Marketing-role examples
- Analytics or measurement tools, with the reports or questions you worked on.
- Paid-campaign platforms, with your actual setup, review or reporting role.
- Keyword research, editing or other content tasks you have performed.
- Email or automation workflows, distinguishing design, setup and monitoring responsibilities.
- CRM segmentation or lifecycle work based on your actual access and duties.
- Spreadsheet or dashboard reporting, including how you checked the data.
Projects and repositories can provide additional context when relevant and shareable. Describe your own contribution, including whether the work was professional, academic or self-directed. See coding-project guidance and GitHub-link guidance. Do not publish employer code or confidential data to create a sample.
Find evidence for interpersonal skills
Start from events rather than adjectives. For collaboration, recall a handoff or shared decision. For communication, identify an audience and something you made easier to understand. For adaptability, describe a change and how you revised your work.
Choose examples that relate to the target role. You do not need one bullet for every trait or a claim that a particular skill is “most wanted” across the whole labor market.
Map your skills directly to the job description
The job description gives useful information, but it is not a complete answer key to the employer’s decision. Separate what it explicitly requires from preferences and general descriptive language.
Use this repeatable review:
- List the relevant responsibilities, qualifications, tools and working skills from the posting.
- Mark which are explicitly required and which are preferred; do not assign importance solely by word count or position.
- For each item you possess, identify a real example or qualification that supports it.
- Write clear, accurate terms into the appropriate section and distinguish training from professional use.
- Review relevance, factual consistency and readability, then inspect the actual export and any populated application fields.
Place information where it is easy to find without imposing a universal section order. A required license might deserve an early section, while a project can carry several skill examples together. The section-order guide discusses these choices.
Follow the requested file format. PDF can preserve visual layout, but it does not guarantee that keywords or reading order survive every parsing system. Keep a verified base and save the submitted copy separately; the tailoring guide explains the workflow.
Use suggestions as prompts for review
Roleframe is our product. You can use it to organize a resume and review suggested changes, but check the suggestions against your own experience. A score cannot certify a skill or reveal an employer’s private evaluation criteria.
Remove invented results, tools and responsibilities. If a suggested skill is missing because you do not have it, leave it out rather than disguising the gap. For several target roles, the multiple-resume guide explains how to change emphasis while keeping the facts consistent.
Frequently asked questions
- Should hard and soft skills have separate sections?
Not necessarily. A skills section can group relevant tools and methods, while experience or projects show how you used them and worked with others. Name interpersonal skills where useful, but support important claims with context rather than long adjective lists.
- What is the ideal ratio?
There is no universal ratio or required number of skills. Let the vacancy and your actual evidence guide the selection. Both technical and interpersonal work can matter in the same role.
- Do soft skills help with ATS screening?
Screening features and employer choices vary. Do not assume systems consider only technical terms or that one skill category automatically passes a filter. Use accurate, recognizable wording and relevant evidence for both categories.
Ready to start your new resume?
Writing a resume takes time, and even a polished one can miss what a hiring manager is looking for. Roleframe helps you build a clear, ATS-safe resume in minutes and tailor it to the job you want.
