Hard skills are teachable, testable abilities tied to a type of work, such as charting in an electronic health record, writing SQL, or reading a wiring diagram. Soft skills are the ways you work with people and problems, such as listening, explaining, and planning, and they show up across almost every job. Most postings ask for both, and the practical difference is how you prove them: hard skills with credentials, tests, and work samples, soft skills with specific stories and results.
Soft skills and hard skills, side by side
The labels are shorthand, not a scientific divide. Still, the two groups behave differently when an employer tries to check them, and that is what matters when you write a resume or prepare for an interview.
| Hard skills | Soft skills | |
|---|---|---|
| What they are | Technical knowledge and tool use for a specific kind of task | Habits of communication, judgment, collaboration, and self-management |
| How people learn them | Courses, certifications, apprenticeships, on-the-job training | Practice, feedback, and repeated exposure to real situations |
| How employers check them | Licenses, skills tests, technical interviews, portfolios, trial tasks | Behavioral questions, references, how you act during the process itself |
| How fast they date | Specific tools can change within a few years | Change slowly, but the setting they are used in changes |
| How they transfer | Often specific to one field or tool family | Carry across most roles, though what "good" looks like varies |
| Weak way to claim them | "Proficient in Excel" | "Excellent communicator" |
| Strong way to claim them | "Built the monthly variance report in Excel with pivot tables and XLOOKUP" | "Rewrote the intake instructions after repeat calls; follow-up calls on that issue dropped" |
Where the line gets blurry
O*NET, the occupational database sponsored by the U.S. Department of Labor, does not sort skills into "hard" and "soft." It lists knowledge areas (such as Economics and Accounting), software and technology skills (such as QuickBooks or AutoCAD), and essential skills it groups as foundational areas (reading comprehension, writing, speaking, active listening, mathematics) and ways of working (critical thinking, active learning, monitoring).
That structure is useful because it shows how many "soft" skills are really core job skills. Active listening and critical thinking appear among the top essential skills O*NET lists for software developers, electricians, registered nurses, and accountants alike. For a nurse, listening carefully during a patient handoff is as much a safety skill as any procedure. So rather than asking "is this hard or soft?", ask "how would someone check that I can do this?"
A few skills sit in the middle and can be proven either way:
- Writing: soft when it means clear email, hard when it means grant writing, technical documentation, or legal drafting with a portfolio.
- Project management: soft as "keeps work moving," hard as a certification or a named method such as Scrum with sprint artifacts you can show.
- Data analysis: hard in the tools you use, soft in deciding which question is worth answering and explaining the result to people who do not read charts.
- Teaching or training: a soft skill in most offices and a licensed, assessed hard skill for classroom teachers.
What employers say they look for
The National Association of Colleges and Employers (NACE) defines eight career readiness competencies: career and self-development, communication, critical thinking, equity and inclusion, leadership, professionalism, teamwork, and technology. Most of these are what job seekers call soft skills, and one, technology, is closer to a hard skill. NACE describes them as competencies that can be shown through behavior, which is a helpful reminder that a list of adjectives proves nothing.
In NACE's Job Outlook 2026 Spring Update survey of 185 employer respondents, employers reviewing entry-level resumes said they want evidence of teamwork, problem-solving, and communication, and they also value technical skills, a strong work ethic, and analytical or quantitative skills. The key word is evidence. Employers in that survey were not asking for the words "team player"; they were asking candidates to show it.
Hard and soft skill examples by role
The hard skills column draws on the software and knowledge areas O*NET lists for each occupation. The soft skills column draws on O*NET's top essential skills for that occupation, translated into what they look like on the job. The last column shows one way to prove a soft skill in that role. Use the row closest to your target job, then check the real posting, because individual employers vary.
| Role (O*NET code) | Hard skills | Soft skills | A concrete way to prove the soft skill |
|---|---|---|---|
| Registered nurse (29-1141.00) | Electronic health records such as Epic or MEDITECH, medication references, clinical knowledge in medicine and psychology | Active listening, monitoring, speaking, critical thinking | A handoff or patient-education change you made and what it prevented |
| Software developer (15-1252.00) | Version control such as GitLab or Bitbucket, frameworks such as Spring Boot, analytical tools such as MATLAB | Critical thinking, active learning, reading comprehension, writing | A design document or code review comment thread that changed a decision |
| Electrician (47-2111.00) | Building and construction knowledge, AutoCAD, estimating software, PLC software | Active listening, monitoring, speaking, active learning | How you explained a code issue or change order to a customer or general contractor |
| Accountant or auditor (13-2011.00) | QuickBooks, Sage 50, Tableau or Alteryx, knowledge of economics, accounting, and law | Reading comprehension, critical thinking, writing, active listening | An audit finding you wrote up so a non-accountant could act on it |
| Customer service representative (43-4051.00) | Contact center software, accounting or billing tools, knowledge of customer service and sales | Active listening, speaking, monitoring, writing | A script or help article you rewrote and the effect on repeat contacts |
| Elementary school teacher (25-2021.00) | Learning platforms such as Schoology, assessment tools such as easyCBM, education and training knowledge | Learning strategies, speaking, active listening, monitoring | How you adjusted a lesson after seeing assessment results for a small group |
How to prove each kind of skill on a resume
Recruiters can verify a hard skill quickly, so make it easy to find. They cannot verify a soft skill from a label, so put it inside an accomplishment. A detailed walkthrough of choosing which skills to list is in how to choose and prove the skills you put on a resume. The short version by type:
Hard skills
- Name the exact tool or method the posting uses: "Epic," not "EHR experience," if you used Epic. Applicant tracking systems and human readers both look for the specific term.
- Add level or scale: "Built 40+ automated test cases in Cypress" says more than "Cypress."
- Give credentials their full name and status: license type, state, and number if the field expects it; "expected June 2027" for in-progress certifications.
- Link proof where the field allows it: a portfolio, GitHub, writing samples, a design case study.
Soft skills
- Do not list them alone. A skills section that reads "communication, teamwork, leadership" is skipped by most readers.
- Use a bullet that shows the behavior and the result: "Ran weekly 15-minute check-ins between warehouse and sales after shipping errors; mis-shipments fell over the next quarter."
- Let one bullet carry both kinds: "Trained six new hires on Salesforce and wrote the quick-start guide the team still uses" proves a tool and the ability to teach it.
- Mirror the posting's language when it is true for you. If the ad says "stakeholder communication," a bullet about updating stakeholders lands better than one about "liaising." See how to tailor a resume to a job description.
| Weak line | Stronger rewrite | What changed |
|---|---|---|
| Strong problem-solving skills | Traced a recurring billing error to a tax setting in QuickBooks and fixed it for 120 client accounts | Soft skill shown through a hard-skill task, with scale |
| Proficient in Microsoft Office | Built an Excel tracker that replaced three spreadsheets for scheduling 30 part-time staff | Specific tool use and a reason it mattered |
| Team player | Covered two colleagues' caseloads during leave and kept every deadline | Behavior you can be asked about in an interview |
| Detail-oriented | Caught a dosage unit error during double-check; reported it through the safety system | An observable action, not a trait |
The Resume Bullet Point Builder walks you through turning a task into a bullet with evidence.
How to prove each kind of skill in an interview
Interviews test hard skills directly and soft skills indirectly. Prepare for both.
Hard skills
- Expect a check. Depending on the field, that could be a coding exercise, a spreadsheet task, a clinical scenario, a writing test, or questions about how you would handle a specific job.
- Describe your process out loud. Interviewers often care more about how you approach a problem than whether you remember every function name.
- Be precise about your level. "I have used Tableau to build dashboards from a prepared data source, but I have not managed the server" is more credible than a vague "yes."
- Bring samples when they help. See how to make a portfolio for a job interview.
Soft skills
- Prepare stories, not adjectives. Behavioral questions such as "Tell me about a time you disagreed with a coworker" are how most interviewers test soft skills. Use the STAR method to keep each story to situation, task, action, and result.
- Match stories to the skills in the posting. If the ad stresses teamwork and problem-solving, have at least one story for each, ideally from recent work.
- Remember that the process is evidence too. Clear scheduling emails, being on time, listening to the full question, and a short follow-up note show communication and professionalism before anyone asks.
A 20-minute skills audit before you apply
- Copy the posting and highlight every skill it names. Mark each one H (someone could test it) or S (someone would need a story).
- For each H skill, write the exact tool or method name, your level, and one piece of proof.
- For each S skill, write one specific situation, what you did, and what changed.
- Cross out anything you cannot back up. An honest gap is easier to discuss than an inflated claim.
- Look for bullets that can carry one H and one S skill at once. Those are usually your strongest lines.
If you are changing careers or have little experience
Your soft skills usually transfer more directly than your hard skills, but they still need translating into the new field's language. A teacher's lesson planning can become "designed training for groups of 25"; a server's table management becomes "handled eight to ten concurrent customer requests during peak periods." For a full method, see how to prove transferable skills in a career change. Then close the hard-skill gap deliberately with one course, certificate, or small project that produces something you can show.
Common mistakes and fixes
| Mistake | Fix |
|---|---|
| Listing 25 tools, some used once | Keep the tools the job uses and that you could discuss for five minutes |
| Rating yourself with stars or bars | Replace with what you built or did with the tool |
| Separating soft skills into their own list | Move them into accomplishment bullets |
| Using a generic soft-skill story for every job | Pick the story that matches the posting's top two skills |
| Ignoring "foundational" skills like writing | Show them with a sample or a result, since many roles depend on them |
Skill descriptions on this page are guidance, not a guarantee of how any employer will screen or score candidates. Requirements differ by employer, industry, and state licensing rules, so the job posting and any licensing board in your field have the final word.