What's the difference between hard skills and soft skills?
Hard skills are teachable, job-specific abilities you can test or show, like writing SQL, building a CAD model, or running a paid search campaign. Soft skills are the habits and people skills that shape how you do the work, like explaining a trade-off, taking feedback, or keeping a project moving when plans change. Put simply, hard skills show you can do the job. Soft skills show you can do it well, with other people, when things get messy.
That's the short answer. The real world is a little less tidy. A developer's code review is part technical judgment, part tact. A product manager's roadmap is part data analysis, part negotiation. And employers don't judge both skill types at the same moment in the hiring process, which changes how you should present them.
This guide covers the full picture: a side-by-side comparison, 60 examples for software developers, product managers, engineers, and marketers, the hybrid skills that sit in between, what employers weigh at each hiring stage, and how to prove both kinds of skills on your resume and in interviews.
Hard skills vs soft skills: a side-by-side comparison
Here's how the two skill types differ across the things that actually matter in a job search.
Hard skills | Soft skills | |
|---|---|---|
What they are | Specific technical or job-related abilities | Behaviors and people skills that shape how you work |
How you learn them | Courses, degrees, certifications, documentation, hands-on practice | Experience, feedback, mentoring, and deliberate practice over time |
How employers check them | Coding tests, case studies, portfolios, certifications, work samples | Behavioral interviews, references, how you handle the interview itself |
Where they show on a resume | Skills section, certifications, tool names inside bullets | Experience bullets and results, summary, cover letter |
How quickly they change | Fast. Tools, platforms, and versions get replaced | Slowly. They build on themselves for your whole career |
How well they transfer | Often tied to a role or industry | Useful in almost any role or industry |
Developer example | Python, REST APIs, Kubernetes | Explaining a design trade-off to a non-technical stakeholder |
Marketer example | GA4, SEO, marketing automation | Persuading leadership to fund a new channel |
What are hard skills?
Hard skills are the specific, teachable abilities a job requires. You can usually prove them with something concrete: a passing test score, a certification, a GitHub repo, a campaign dashboard, or a drawing set. That's why they appear so often in the requirements section of a job posting and why screening software looks for them first.
Hard skills have one trait people rarely talk about: they expire. Tools get replaced, frameworks fall out of favor, and platforms change. Marketers learned this when Google stopped processing data in Universal Analytics in 2023 and teams had to move to GA4. A hard skill on your resume is only as strong as its most recent use, so keeping them current is part of the job.
Common types of hard skills
- Programming and technical skills: languages, frameworks, cloud platforms, and system design.
- Data and analytics: SQL, statistics, dashboards, experimentation, and modeling.
- Tools and software: Jira, Figma, Salesforce, SolidWorks, HubSpot, and similar platforms.
- Methods and frameworks: Agile, A/B testing, root cause analysis, and lean manufacturing.
- Domain knowledge: industry rules and standards such as HIPAA, GAAP, or building codes.
- Credentials and licenses: a PE license, AWS certifications, or a PMP.
- Languages: spoken and written language fluency, which counts as a hard skill because it can be tested.
What are soft skills?
Soft skills are the behaviors that decide how well you use your hard skills with other people. They include how you communicate, solve problems, handle pressure, work on a team, and lead. You can't prove them with a certificate. You prove them through what you've done and how you act.
Where hard skills expire, soft skills build up. The way you run a tough meeting or deliver bad news gets better with every rep, and it goes with you to every job you'll ever have. Employers treat them as core job requirements, not extras. The National Association of Colleges and Employers (NACE) defines career readiness through eight competencies, and seven of them are soft skills: communication, critical thinking, teamwork, leadership, professionalism, equity and inclusion, and career and self-development. Technology is the only purely technical one.
You'll often hear "soft skills" and "interpersonal skills" used as if they're the same thing. Interpersonal skills are actually one part of soft skills, the part about working with other people. For a closer look, see our guide on what interpersonal skills are.
Common types of soft skills
- Communication: writing clearly, presenting, listening, and adjusting your message to your audience.
- Collaboration: teamwork, giving and receiving feedback, and handling conflict.
- Problem-solving and critical thinking: breaking down messy problems and making sound judgment calls.
- Self-management: time management, adaptability, reliability, and staying calm under pressure.
- Leadership and influence: mentoring, persuading others, and owning outcomes without being told to.
60 hard skills and soft skills examples by role
Generic skill lists don't help much, because "communication" means something different for a backend developer than it does for a brand marketer. Here are 60 examples, 15 for each role, split into hard and soft skills.
Role | 8 hard skills | 7 soft skills |
|---|---|---|
Software developer | Python or Java, JavaScript/TypeScript, SQL, REST and GraphQL APIs, Git, Docker and Kubernetes, AWS or GCP, automated testing | Explaining technical trade-offs, constructive code review, debugging under pressure, asking good questions, estimating honestly, mentoring junior developers, written documentation |
Product manager | Product analytics (Amplitude, Mixpanel), SQL, A/B test design, roadmapping tools, writing PRDs, user research methods, pricing analysis, Jira | Prioritizing and saying no, stakeholder alignment, storytelling with data, customer empathy, facilitating decisions, negotiating scope, staying calm when plans change |
Engineer | CAD (SolidWorks, AutoCAD), GD&T, finite element analysis, MATLAB, design for manufacturing, tolerance analysis, codes and standards, project scheduling | Cross-team communication with manufacturing, technical writing for non-engineers, safety-first judgment, structured problem-solving, accountability for errors, teaching field crews, adapting to site changes |
Marketer | SEO, GA4 and attribution, paid search and social, marketing automation (HubSpot, Marketo), email marketing, copywriting, content management systems, landing page testing | Creativity, persuading leadership, audience empathy, juggling deadlines, giving creative feedback, learning new channels quickly, telling the story behind the numbers |
The pairing that sets each role apart
In each of these roles, plenty of candidates have the hard skills. What tends to stand out is one specific hard skill paired with one specific soft skill:
- Software developer: system design plus the ability to explain why you chose one design over another. Senior engineers are hired for judgment they can explain, not just code that runs.
- Product manager: SQL and analytics plus the confidence to say no. Data turns "I don't think we should build that" into a decision the team can accept.
- Engineer: CAD and tolerance analysis plus clear communication with the shop floor. A perfect drawing that manufacturing can't build is an expensive mistake.
- Marketer: attribution and GA4 plus storytelling. Budgets go to the marketer who can explain what the numbers mean, not just report them.
Hybrid skills: when a skill is both hard and soft
Some of the most valuable skills don't fit neatly in either box. They have a technical side you can test and a human side people notice. Hiring managers often care most about these, because they're the skills that turn individual expertise into team results.
Hybrid skill | The hard side (testable) | The soft side (what people notice) |
|---|---|---|
Project management | Scheduling, critical path, Jira, budgeting | Keeping people aligned, flagging risks early |
Data storytelling | SQL, Tableau or Looker, statistics | Framing results for executives, picking the one number that matters |
Technical writing | Structuring docs, API references, diagrams | Writing for the reader's level, cutting jargon |
Stakeholder management | Roadmaps, RACI charts, status reporting | Building trust, negotiating, managing expectations |
Code review | Reading code, standards, security checks | Giving feedback that helps instead of hurts |
Customer research | Interview scripts, survey design, synthesis | Listening, empathy, spotting what users don't say |
How to use this on a resume: put the hard side in your skills section, where it can be scanned and matched, and prove the soft side in your experience bullets. "Project management" in a skills list is a claim. "Kept 3 teams aligned through a 6-month migration with zero missed launch dates" is proof.
Which matters more: hard skills or soft skills?
Both, but not at the same moment. Hiring teams say soft skills matter at least as much as technical ones. In LinkedIn's Global Talent Trends research, 92% of talent professionals and hiring managers said soft skills matter as much as or more than hard skills, and 89% said bad hires usually lack soft skills.
That doesn't mean hard skills matter less. It means they do a different job. Hard skills get you through the door: they're what screening software and recruiters check first. Soft skills decide what happens once you're in the room, and later, who gets promoted.
What employers check at each hiring stage
Hiring stage | What's being checked | Mostly | What to do |
|---|---|---|---|
Resume screening software | Keywords, job titles, required tools | Hard | Use the posting's exact skill terms where they're accurate |
Recruiter review | Relevant experience, clear results | Hard + soft | Show results in bullets, not just duties |
Technical or skills assessment | Coding, case study, portfolio, take-home task | Hard | Practice the format; think out loud |
Hiring manager interview | Depth, judgment, how you approach problems | Both | Explain why you made decisions, not just what you did |
Behavioral and team interviews | Collaboration, conflict, ownership | Soft | Prepare 4 to 5 stories with real outcomes |
Reference checks | Reliability, teamwork, integrity | Soft | Choose references who saw you work with others |
How the balance shifts as your career grows
Career stage | What tends to carry the most weight |
|---|---|
Entry-level | Solid core hard skills, plus coachability and reliability. Nobody expects mastery, but they do expect you to learn fast. |
Mid-level | Deep hard skills in your area, plus ownership: you finish things without being chased. |
Senior individual contributor | Judgment and influence. You're hired to make good calls and help others make them too. |
Manager or lead | Mostly soft skills: hiring, coaching, prioritizing, and communicating up and down. Hard skills keep you credible with the team. |
How to show hard skills and soft skills on your resume
The two skill types need different treatment on the page. Hard skills should be easy to find. Soft skills should be easy to believe. For the full rundown on picking and listing skills, see our guide to good resume skills.
Hard skills: name them exactly
List your most relevant hard skills in a clearly labeled skills section and use the same terms the job posting uses, as long as they're accurate. If the posting says "Kubernetes," write "Kubernetes," not just "container orchestration." Name versions or platforms when they matter, and back up anything you can't prove with a project or a credential, such as the ones covered in our guide to certifications on a resume. Matching the posting's language also helps your resume get past applicant tracking systems.
Soft skills: let your bullets do the talking
Skip one-word labels like "communication" or "team player" in your skills section. Every candidate claims them, so they don't tell the reader anything. Instead, show the soft skill in action inside your experience bullets, with a specific situation and result. If you want a word or two in your summary, pick ones you can back up. Our list of adjectives to describe yourself shows how to prove each one.
Write pairing bullets: hard skill + soft skill + result
The bullets recruiters remember usually show both skill types at once. Use this formula: what you built or analyzed (hard skill) + how you got people on board (soft skill) + the measurable result. Here's what that looks like by role:
All names and numbers in these examples are illustrative. Use your real metrics.
Your resume summary can do a quick version of the same thing: one or two core hard skills, one soft skill you can prove, and one standout result.
How hard skills and soft skills are tested in interviews
Most interview processes test hard skills with a practical exercise and soft skills with behavioral questions. Here's what that usually looks like:
Role | How hard skills are tested | How soft skills are tested |
|---|---|---|
Software developer | Live coding, take-home project, system design round | "Tell me about a time you disagreed with a technical decision." |
Product manager | Product sense case, metrics or SQL questions, prioritization exercise | "Tell me about a time you had to say no to a senior stakeholder." |
Engineer | Technical problem-solving, walkthrough of a past design, calculations | "Tell me about a design that failed and what you did next." |
Marketer | Portfolio review, campaign case study, analytics exercise | "Tell me about a campaign that underperformed. How did you explain it?" |
Technical rounds test soft skills too, quietly. Interviewers notice whether you ask clarifying questions, explain your thinking as you go, and respond well when they push back. A candidate who solves 80% of a problem while communicating clearly often beats one who solves it all in silence.
For behavioral questions, the STAR method (situation, task, action, result) keeps your answers focused. Our guide to strengths and weaknesses has full sample answers for each of these four roles, and your cover letter is a good place to tell one short version of your strongest story. Not sure what goes where? See cover letter vs resume.
How to find and close your skill gaps
Run a quick skills audit
Pull up a job posting you want and sort every skill it mentions into hard or soft. Then, for each one, write down where you've already proven it. Anything with an empty proof column is a gap, either in your experience or in how your resume describes it. Here's an example for a product manager:
Skill from the posting | Type | Where I've proven it | Next step |
|---|---|---|---|
SQL | Hard | Built weekly retention queries in my current role | Add it to a bullet with the result |
A/B testing | Hard | Ran 2 pricing-page tests | Name the tool and the lift |
Stakeholder management | Hybrid | Led monthly roadmap reviews with sales | Write a pairing bullet |
Comfort with ambiguity | Soft | Launched an MVP with no prior data | Prepare it as a STAR story |
Figma | Hard | No proof yet | Build one prototype or leave it off |
Repeat this for each application and you'll also know exactly how to tailor your resume to the job description.
How to build hard skills
- Learn by building something real. A deployed side project, a marketing teardown, or a redesign proves more than a finished course.
- Get certified where your field expects it, such as cloud certifications for developers or a PE license for engineers.
- Volunteer for the stretch task at work, like the first migration to a new tool. It gives you a real bullet, not just a course.
How to build soft skills
- Pick one skill and get practice on purpose. Want to present better? Volunteer for the sprint demo every two weeks.
- Ask for specific feedback. "How clear was my update on the timeline?" gets a more useful answer than "How did I do?"
- Write the follow-up nobody wants to write, like the post-mortem, the decision memo, or the onboarding doc. It builds communication and ownership at the same time.
For a step-by-step plan focused on people skills, see our 30-day practice plan on what are interpersonal skills.
Common mistakes when presenting hard and soft skills
Mistake | Why it hurts | Fix |
|---|---|---|
Listing soft skills as one-word labels | Every candidate claims them, so they're ignored | Prove them in bullets with a situation and result |
Listing tools you've barely used | A technical round can expose it in minutes | Keep only skills you'd be happy to be tested on |
Vague hard skills like "coding" or "digital marketing" | Software and recruiters search for specific terms | Name the language, platform, or channel |
Ignoring soft skills in technical roles | Your resume reads like a tool list with no judgment behind it | Add at least two pairing bullets |
Using different terms than the posting | Matching tools may miss you | Mirror the posting's wording where it's accurate |
Claims and bullets that don't match | "Strong leader" with no bullet showing leadership raises doubts | Make sure every claim in your summary is backed up below |
Final thoughts
The hard skills vs soft skills debate is a bit of a false choice. Hard skills prove you can do the work, and they're what gets your resume shortlisted. Soft skills prove you can do the work with other people, and they're what wins the offer and the promotion after it. The candidates who stand out don't pick one. They show both in the same bullet, the same story, and the same interview answer.
Start with the skills audit above, rewrite your two or three strongest bullets as pairing bullets, and make sure every skill you list is one you could happily be tested on. If you're building your resume from scratch, our step-by-step guide on how to write a resume walks you through every section.
Philip Russell is the Co-Founder of Jobsuit.ai, an AI-powered career platform serving over 500,000 users worldwide. Passionate about AI, technology, and career development, he shares insights on job searching, resume optimization, and the evolving hiring landscape to help job seekers land their dream jobs.
