You’ve probably stared at that blank space under the “Skills” section of your resume more times than you’d like to admit.

Should you list “Python” and “JavaScript” first? Or lead with “Team Leadership” and “Communication”? The whole soft skills vs. hard skills debate has been going on forever, and honestly? There’s still a ton of bad advice floating around.

Some people will tell you that hard skills get you the interview, soft skills get you the job. Others say technical abilities are all that matter in the first round of screening. Like most things, the truth is somewhere in the middle.

But here’s the thing—what you should list depends less on some universal rule and more on where you are in your career and what you’re applying for.

Hard Skills Are Your Ticket In

Let’s start with the obvious.

Hard skills are the concrete stuff. They’re teachable, measurable, and usually have some kind of certification or portfolio attached to them. Think:

  • Programming languages (C++, SQL, Rust)
  • Foreign languages (Mandarin, Spanish, Arabic)
  • Software proficiency (Salesforce, Figma, QuickBooks)
  • Data analysis (SPSS, Excel pivot tables, R)

If you’re applying for a technical role—developer, accountant, engineer—these are non-negotiable. Nobody cares how great your communication skills are if you can’t write clean code or balance a balance sheet. Recruiters use hard skills to filter. It’s just how it works.

Applicant Tracking Systems (ATS) scan for specific keywords. If the job description asks for “project management” and “Asana” and you’ve got neither listed? You’re probably not getting through.

But here’s where people mess up: they list every single hard skill they’ve ever touched. That Excel course you took in 2019 but haven’t used since? Leave it off. The beginner-level Python that you’d need three days to debug? Maybe not.

List what you can actually do right now, without Googling.

Soft Skills Are Harder to Prove

Soft skills are the messy ones. They’re personality-driven, harder to measure, and—let’s be real—easy to lie about on a resume.

Problem-solving. Adaptability. Emotional intelligence. Conflict resolution.

Everyone claims they have them. But how do you prove it?

You can’t exactly take a test and get a certificate in “being a team player.” (Well, you can, but most hiring managers see through that.)

The mistake people make is just listing them in a bullet point with zero context. Saying “excellent communication skills” doesn’t mean anything. It’s just noise.

But if you write something like “Led weekly client meetings to clarify project requirements and reduce revision requests by 30%”—now you’re showing communication in action.

Soft skills need evidence. They live in your achievements, not your skills list.

The Role Dictates the Mix

A senior software engineer and a restaurant manager are going to have very different resumes. Obvious, right?

But dig a little deeper.

For the engineer, hard skills dominate the first page. Languages, frameworks, tools. But if they’re applying for a lead role? Suddenly soft skills matter more. They’ll need to mentor juniors, push back on unrealistic deadlines, explain technical stuff to non-technical stakeholders.

For the restaurant manager, soft skills might be front and center. Customer service, team motivation, handling complaints. But hard skills still matter—inventory systems, scheduling software, food safety certifications.

The mix shifts depending on seniority and function.

Entry-level? Emphasize hard skills. Prove you can do the basic work.

Mid-career? Balance both. You’ve got technical chops and you’ve worked with people.

Executive? Soft skills often outweigh hard skills. You’re leading, not doing.

Where Soft Skills Actually Belong

Some career coaches will tell you to create a separate “Soft Skills” section on your resume.

I’m not a fan of this.

A standalone list of soft skills—“Communication, Leadership, Time Management, Critical Thinking”—looks like you copied it from a template. It doesn’t tell me anything about you.

Instead, weave them into your experience section. Show, don’t tell.

  • Instead of “Detail-oriented,” write “Caught a billing error that saved the company $12k annually.”
  • Instead of “Leadership,” write “Managed a team of 5 junior designers through a rebranding project delivered 2 weeks early.”

See the difference?

The only exception is if the job description explicitly asks for certain soft skills and you have limited space. Then you can cluster them at the bottom. But even then, try to back them up elsewhere.

The One Skill Everyone Forgets

There’s this weird gap people leave open—and it’s not exactly soft or hard.

It’s contextual knowledge.

Industry-specific know-how that doesn’t fit neatly into either category. Like knowing how healthcare billing works. Or understanding the seasonal cycles in retail. Or being familiar with how construction projects actually move through city permitting.

This stuff matters. A lot.

If you’re switching industries, you might not have it. And if you’re staying in the same field, it’s probably second nature to you. But don’t assume it’s obvious. If you understand the weird quirks of your industry, mention it. It sets you apart from people who technically know the tools but don’t get the bigger picture.

Practical Takeaway

Here’s the short version.

Hard skills get you past the robots. Soft skills help you connect with humans. Both matter, but they serve different purposes at different stages.

If you’re updating your resume this week, do this:

Look at every skill you’ve listed. Ask yourself: Can I prove this? If the answer is no, either delete it or rework it until you can.

And for the soft stuff, stop listing them like adjectives. Show me the last time you actually used them.

Want to create a professional resume? Try our free resume builder today.