Skills to put on a resume: what actually matters to recruiters

The skills section of your resume looks simple. It's usually a short block of text near the top or bottom of the page — a few rows of words separated by commas or bullet points. Because it looks simple, most people treat it as an afterthought. They list whatever comes to mind, copy a few terms from a generic "best skills for resume" article, and move on.

That's a mistake. Your skills section is one of the hardest-working parts of your resume. It serves two audiences simultaneously: the applicant tracking system that's scanning for keyword matches, and the human recruiter who's spending six to eight seconds deciding whether to keep reading. When it's done right, the skills section tells both audiences the same thing: this person has the specific competencies this role requires.

When it's done wrong — padded with generic terms, cluttered with irrelevant tools, or missing the keywords the job actually calls for — it either fails the ATS screen or fails to impress the human who reads it. Either way, you don't get the interview.

This guide covers what to put in your skills section, what to leave out, how to organize it, and how to tailor it for every application. No filler, no lists of "top 100 resume skills" that apply to nobody in particular. Just a practical framework for building a skills section that does its job.

What the skills section is really for

Before you can build an effective skills section, you need to understand what it's actually doing on your resume. It serves two distinct functions, and most people only think about one of them.

Function one: ATS keyword matching. When you submit your resume through an online application, it almost always passes through an applicant tracking system before a human sees it. The ATS parses your resume into structured data — name, contact info, work history, education, and skills. It then compares your skills against the job requirements. If you're missing key terms, your resume may never reach a recruiter. The skills section is the most direct place to ensure those terms appear on your resume. It's a keyword index, essentially — a concentrated block of searchable terms that the ATS can match against the job description.

Function two: the human quick-scan. Recruiters don't read resumes top to bottom. They scan. Eye-tracking studies consistently show that recruiters spend a disproportionate amount of their brief review on the skills section, job titles, and company names. Your skills section gives the recruiter a fast answer to their most pressing question: does this person have the technical foundation for this role? If a hiring manager needs someone who knows Salesforce, Python, and SQL, they want to confirm those three words exist on your resume within seconds. The skills section is where they look first.

This dual purpose — machine-readable keyword matching and human-readable quick confirmation — shapes everything about how you should build the section. It needs to contain the right terms (for the ATS), organized clearly (for the human), and tailored to the specific job (for both). A generic skills section that never changes between applications is working at half capacity at best.

One thing the skills section is not for: proving you have a skill. Listing "data analysis" in your skills section tells a recruiter you claim to know data analysis. What proves it is the bullet point under your last job that says "Built automated reporting dashboards in Tableau, reducing weekly reporting time from 4 hours to 20 minutes." The skills section flags the competency. Your experience section proves it. They work together.

Hard skills vs. soft skills: what belongs where

This is where most resume advice gets muddled. You'll see articles telling you to list a mix of hard skills and soft skills in your skills section. That advice is technically correct and practically useless. Yes, employers value both types. But they belong in different places on your resume, and mixing them in the skills section weakens it.

Hard skills belong in the skills section

Hard skills are specific, teachable, and verifiable. They include programming languages, software platforms, methodologies, tools, frameworks, certifications, and technical competencies. "Python" is a hard skill. "Tableau" is a hard skill. "GAAP accounting" is a hard skill. "Agile methodology" is a hard skill. These terms are concrete. A recruiter can look at them and immediately understand what you know how to do. An ATS can match them against job requirements. They are the backbone of an effective skills section.

Hard skills also have a useful property: they are searchable. When a recruiter uses an ATS to search their database for candidates, they search for hard skills. Nobody searches "communication" in an ATS. They search "Salesforce" or "financial modeling" or "AWS." If you want your resume to surface in those searches, your hard skills need to be explicitly listed.

Soft skills belong in your bullet points

Soft skills — leadership, communication, problem-solving, teamwork, adaptability — are important. Nobody disputes that. But listing them in your skills section accomplishes almost nothing. Here's why: soft skills are self-assessed and unverifiable in a skills list. Anyone can write "leadership" on a resume. It costs nothing and proves nothing. A recruiter seeing "leadership" in your skills section doesn't think "great, this person is a leader." They think nothing, because they've seen it on every resume they've read today.

Soft skills become convincing when they're demonstrated through action. "Led a 12-person cross-functional team through a 6-month product launch" demonstrates leadership. "Presented quarterly financial results to the board of directors" demonstrates communication. "Redesigned the onboarding process after identifying a 40% drop-off in the first week" demonstrates problem-solving. These are bullet points that show impact, not labels that claim a trait.

There are a few exceptions. Some soft skills have become semi-technical terms in certain industries. "Cross-functional collaboration" in product management, "stakeholder management" in consulting, "client relationship management" in sales — these are specific enough to function as hard skills in context. If the job description explicitly lists them as requirements, include them. But "communication skills" and "team player" should never appear in your skills section. They are resume filler, and recruiters know it.

The rule of thumb: if a skill can be tested, certified, or verified in an interview through a technical question, it belongs in the skills section. If it can only be demonstrated through examples of your work, it belongs in your bullet points.

Not sure which skills match your target role?

Notch analyzes your resume against any job description and identifies the specific skills gaps — so you know exactly what to add.

Try Notch free

How to extract the right skills from a job description

Your skills section should never be static. It should change — at least partially — for every job you apply to. The source material for those changes is the job description itself. Here's how to mine it systematically.

Start with the requirements section. Most job descriptions have a "Requirements," "Qualifications," or "What you'll need" section. This is the highest-value source of skills keywords. Everything listed here is something the employer has decided is necessary for the role. Read it line by line and extract every specific skill, tool, platform, methodology, or credential mentioned. If the requirements say "proficiency in SQL, Python, and R," those three terms need to appear on your resume — assuming you actually know them.

Check the responsibilities section for implied skills. The "Responsibilities" or "What you'll do" section often contains skills that aren't explicitly named but are clearly required. "Build and maintain ETL pipelines" implies skills in data engineering, SQL, and likely a tool like Airflow or dbt. "Manage paid advertising campaigns across Google and Meta platforms" implies Google Ads, Meta Ads Manager, and likely Google Analytics. Read responsibilities as skill requirements in disguise, because that's what they are.

Note the exact language the employer uses. If the job description says "project management," don't list "program management." If it says "customer success," don't write "client services." ATS systems are literal. They match strings, not concepts. Use the employer's exact terminology wherever it honestly applies to your experience. This isn't about gaming the system — it's about speaking the same language as the people who wrote the job description.

Look at similar job postings from the same company or competitors. If the company has posted similar roles, compare the skills they list. Terms that appear across multiple postings are core competencies for that type of role at that company. This is especially useful for identifying skills you might have overlooked or for understanding which of your many skills to prioritize for this particular application.

Separate the negotiable from the non-negotiable. Required skills are non-negotiable — you need to list them if you have them. Preferred or "nice to have" skills are your opportunity to differentiate. If you happen to have two of the five preferred skills, listing them signals that you bring more to the table than the minimum. But don't stretch the truth to claim preferred skills you don't actually have. They'll come up in the interview, and "I listed it because it was in the job description" is not a defensible answer.

Organizing your skills section

A pile of 15 skills separated by commas is harder to scan than 15 skills organized into three or four labeled categories. Organization matters because it respects the recruiter's time and makes your competencies easier to parse at a glance.

Organize by category, not alphabetically

The most effective skills sections group related skills under descriptive subheadings. This does two things: it makes the section scannable, and it provides context that individual skill names sometimes lack. "Pandas" on its own could mean anything to a non-technical recruiter. "Pandas" under a heading labeled "Data Analysis & Visualization" immediately communicates what you use it for.

Common category labels include:

Your categories should reflect your industry and the role you're targeting. A software engineer's categories will look different from a marketing manager's, which will look different from a financial analyst's. Don't use generic categories if specific ones are more accurate.

Lead with your strongest category

The first category in your skills section gets the most attention. Make it the one most relevant to the job. If you're applying for a data science role, lead with "Programming & Machine Learning," not "Project Management Tools." If you're applying for a marketing role, lead with "Marketing Platforms & Analytics," not "Microsoft Office." The order of your categories is a signal about your priorities and your fit for the role.

Consider the format

There are a few common formats for the skills section, and the best choice depends on how many skills you're listing and your resume's overall layout:

Avoid skill bars, star ratings, or percentage-based proficiency indicators. They look modern in templates, but they're meaningless. What does "Python: 4 out of 5 stars" mean? Compared to whom? Rated by whom? They add visual noise without adding information, and they can actually hurt you — a recruiter might wonder why you rated yourself 3 out of 5 on a required skill instead of just listing it.

Skills by industry

The best skills for your resume depend entirely on your industry and target role. Here's a practical reference for five common fields. These aren't exhaustive lists — they're starting points to help you identify what's expected for roles in each area.

Technology

Tech roles are the most skill-section-dependent resumes you'll encounter. Hiring managers and technical recruiters scan for specific languages, frameworks, and tools — and they know exactly what they're looking for.

Marketing

Marketing has shifted heavily toward tools and platforms. A modern marketing resume needs to show both strategic thinking and technical execution capability.

Finance

Finance resumes lean heavily on tools, methodologies, and regulatory knowledge. Certifications carry significant weight here and should be prominently listed.

Healthcare

Healthcare resumes must balance clinical competencies, regulatory knowledge, and systems proficiency. Certifications and licensure often carry as much weight as the skills section itself.

Operations

Operations roles span industries, but they share a common thread: efficiency, process, and measurable outcomes. The skills section should reflect systems thinking and the tools you use to execute it.

See which skills your resume is missing

Paste your resume and a job description into Notch. You'll get a match score and a clear breakdown of which skills to add, reorder, or demonstrate more effectively.

Try Notch free

Skills you should almost never list

Some skills appear on resumes so frequently and add so little value that they've become invisible to recruiters. Worse, they can actively work against you by signaling that you're padding your resume or don't understand what the role actually requires.

Microsoft Office. Unless the job description specifically asks for it — and even then, only if the role centers on it — listing "Microsoft Office" or "Microsoft Word" on your resume is a waste of space. It's like listing "email" or "typing." It's assumed. Every office worker uses Word and Outlook. The exception is advanced Excel skills (VBA, macros, complex modeling) for finance or analytics roles, which is genuinely worth listing because "Excel" at that level is a different skill than basic spreadsheet use.

"Communication skills." This is the single most overused, least meaningful term on resumes. Every candidate lists it. No recruiter has ever shortlisted someone because they wrote "excellent communication skills" in their skills section. Your communication ability is demonstrated by how you write your resume, how you structure your bullet points, and what you describe doing in your past roles. If your resume is well-written, you've already proved it. If it isn't, claiming the skill won't help.

"Team player" / "works well with others." This falls into the same category as communication skills. It's expected of anyone who works in an organization. It's not a differentiator, and listing it suggests you couldn't think of something more specific to include. If collaboration is genuinely central to the role, demonstrate it: "Coordinated a 15-person launch across four departments" says more than "team player" ever could.

"Detail-oriented." Another resume cliche that communicates nothing. In fact, a resume that claims to be detail-oriented but has a typo or inconsistent formatting actively undermines the claim. Show attention to detail through the quality of your resume itself and through specific examples in your bullets, not through a label.

Social media (generic). If you're applying for a marketing or social media role, list the specific platforms and tools: "Meta Business Suite, LinkedIn Campaign Manager, TikTok Ads, Sprout Social." If you're not applying for a marketing role, listing "social media" is irrelevant. Having a personal Instagram account is not a professional skill.

Outdated technologies. If you're a developer listing jQuery, ColdFusion, or Flash in 2026, you're signaling that your skills haven't kept up. If a legacy role specifically requires outdated tech, list it. Otherwise, focus on current tools. The same principle applies to any industry: listing a software platform that was sunset five years ago raises questions about how current your knowledge is.

How many skills to include

There's a tension between listing enough skills to pass ATS screening and listing so many that the section becomes a wall of text nobody reads. The sweet spot for most resumes is 8 to 15 skills, organized into 2 to 4 categories.

The case for enough. If the job description lists 12 required technical skills and you only mention 4 of them, you're leaving keyword matches on the table. ATS systems that score candidates on keyword density will rank you lower than someone who matched 10 out of 12. And a recruiter scanning your skills section will notice the gaps. You want to cover the major requirements of the role.

The case against too many. Diminishing returns set in quickly. Listing 25 or 30 skills doesn't make you look more qualified — it makes you look unfocused. A recruiter seeing a massive skills block will wonder whether you're genuinely proficient in all of them or just listing everything you've ever touched. It also dilutes the impact of your strongest skills. When "Python" is one of 8 skills, it stands out. When it's one of 30, it blends in.

There's also a credibility issue. If you list 30 skills, a hiring manager is going to pick the most advanced ones and ask you about them in the interview. If your knowledge is surface-level because you only used the tool once in a workshop, that becomes obvious. Every skill on your resume should be something you can discuss confidently for at least two to three minutes in an interview — what you used it for, what you built or accomplished with it, and what you'd do differently next time.

A practical framework: Start with the job description. List every skill you have that appears in the requirements or responsibilities. That's your baseline. Then add 2-3 skills that don't appear in the job description but strengthen your candidacy — tools or competencies that are clearly relevant to the role even if the employer didn't name them explicitly. If that gives you 8-15 skills, you're in good shape. If it gives you 20+, prioritize the most important ones and move the rest into your bullet points where they'll appear in context.

Certifications and tools: where they go

Certifications and tools are related to skills but serve different purposes on your resume. Where you place them depends on how central they are to the role.

Certifications

Major, industry-recognized certifications deserve their own section — usually titled "Certifications" or "Certifications & Licenses" and placed near your education section. This includes things like PMP, CPA, AWS Solutions Architect, Google Analytics Certified, Six Sigma Black Belt, CISSP, or any state-issued professional license. These are credentials with specific meaning, and they deserve prominent, standalone placement.

However, you should also mention the certification abbreviation in your skills section if it's directly relevant to the job. For example, if you have a PMP and you're applying for a project management role, "PMP" should appear in your skills section under a "Project Management" category and in your dedicated Certifications section. This gives you double visibility: the ATS picks it up in the skills section, and the human sees it in the certifications section.

Minor certifications — a one-hour LinkedIn Learning course, a free online assessment, or an internal company training — generally don't warrant a separate section. If they're relevant, mention them in your skills section. If they're not relevant, leave them off entirely. A recruiter who sees 15 micro-certifications alongside a few real credentials may question your judgment about what's meaningful.

Tools and platforms

Tools belong in your skills section, organized by category as described above. But there's a subtlety: listing a tool in your skills section and mentioning it in a bullet point accomplish different things. The skills-section listing ensures the keyword match. The bullet-point mention provides proof of use. The strongest approach is to do both.

For example: list "Salesforce" in your skills section under "CRM & Sales Tools," and also include a bullet point like "Managed a $4.2M pipeline in Salesforce, improving forecast accuracy by 18% through standardized opportunity staging." Now the ATS sees the keyword in the skills section, and the recruiter sees the proof in the bullet. That's a complete picture.

When listing tools, be specific about the product. "Adobe Creative Suite" is less useful than "Photoshop, Illustrator, InDesign" because recruiters and ATS systems often search for individual product names. Similarly, "Google Cloud Platform" is less searchable than "BigQuery, Cloud Storage, Compute Engine" if those are the specific services you've used.

Common mistakes

Beyond the generic skills discussed above, there are several structural and strategic mistakes that undermine otherwise good skills sections.

Listing skills you can't demonstrate

This is the most damaging mistake on this list. If you write "machine learning" in your skills section because you took an online course but have never built a model that went into production, you're setting a trap for yourself. A technical interviewer will ask you about it. "Tell me about a time you used machine learning to solve a business problem" is a standard question, and "I took a Coursera course" is not a sufficient answer.

Every skill on your resume should connect to real work you've done. That doesn't mean you need five years of experience with every tool — but you should be able to describe a specific project, task, or deliverable where you used it. If you can't, it shouldn't be listed. This is the core principle behind interview-defensible resumes: don't put anything on paper you can't back up in person.

Padding with buzzwords

"Strategic thinker." "Results-driven." "Innovative problem-solver." "Dynamic leader." These phrases appear on millions of resumes and communicate nothing specific. They're buzzwords — empty containers that sound impressive but contain no actual information. A recruiter reading "results-driven marketing professional" learns nothing about your skills. A recruiter reading "HubSpot, Google Analytics, SEO, paid media strategy" learns exactly what you can do.

If you're tempted to add a buzzword, ask yourself: can I replace this with something specific? "Strategic thinker" becomes "market analysis, competitive positioning, go-to-market strategy." "Results-driven" becomes a bullet point with an actual result in it. Specific always beats vague.

Never updating the section

Using the same skills section for every application is one of the most common mistakes job seekers make. It's also one of the easiest to fix. Each job description emphasizes different skills, uses different terminology, and prioritizes different competencies. Your skills section should reflect the specific role you're targeting, not a general-purpose list of everything you know.

This doesn't mean rewriting from scratch every time. Most people have a "master" skills list of 20-30 competencies, and they select and reorder from that list based on the job description. The core skills stay. The order, emphasis, and supplementary skills change. It takes ten minutes per application and materially improves your match rate.

Ignoring the job description's language

If the job description says "data visualization" and you write "data presentation," you may be describing the same skill but using the wrong words. ATS systems often cannot make that connection. Neither can a recruiter doing a quick scan. Use the exact language from the job description whenever it honestly describes your experience. This isn't about being inauthentic — it's about removing friction between your resume and the reader's expectations.

Placing the section where nobody looks

Some resume templates bury the skills section at the very bottom of the second page. By the time a recruiter gets there — if they get there — they've already formed an opinion about your candidacy. For most roles, the skills section should be visible on the first page, either near the top (below your summary) or in a sidebar. The exception is academic or research CVs, which follow a different convention. For industry resumes, accessibility matters.

Get our free pre-submit resume checklist

14 things to check before hitting "Apply" — from ATS formatting to interview-defensible bullets.

Putting it all together: a skills section that works

Let's walk through what a strong skills section looks like in practice. Imagine you're a mid-level data analyst applying for a senior analytics role at a fintech company. The job description emphasizes SQL, Python, Tableau, financial data analysis, and cross-functional collaboration with product teams.

A weak skills section might look like this:

Skills: Excel, PowerPoint, SQL, Python, Tableau, R, communication, teamwork, problem-solving, detail-oriented, Microsoft Office, data analysis, leadership, Google Sheets, Slack

This is a keyword dump. It mixes hard skills with meaningless soft skills, includes obvious tools (Slack, Google Sheets), and lists things in no particular order. A recruiter scanning this has to work to find what they're looking for.

A strong skills section for the same candidate:

Data Analysis & Modeling: SQL (advanced), Python (Pandas, NumPy, Scikit-learn), R, statistical modeling, A/B testing, regression analysis

Visualization & Reporting: Tableau, Power BI, Looker, executive dashboard design, financial reporting

Tools & Platforms: Git, Jupyter, dbt, Snowflake, BigQuery, Jira

This version is categorized, specific, and free of filler. Every item is a hard skill the recruiter can verify. The categories map to the core competencies of the role. "SQL (advanced)" signals depth, not just familiarity. The soft skills — cross-functional collaboration, communication — will appear in the bullet points where they can be demonstrated, not here where they'd just take up space.

The difference between these two versions is the difference between a skills section that works for you and one that works against you. Build yours like the second example and you'll clear both the ATS screen and the recruiter's quick scan.

Build a skills section that matches

Notch compares your resume's skills against the job description and shows you exactly what to add, remove, or reorganize. Takes 30 seconds.

Try Notch free

Frequently asked questions

How many skills should I put on a resume?

Most resumes benefit from 8 to 15 skills in a dedicated skills section, organized by category. The exact number depends on your industry and experience level. The key is relevance: every skill listed should connect to the job you're applying for. Listing 30 skills doesn't make you look more qualified — it makes it harder for the recruiter to find the ones that matter. Start with the skills the job description requires, add a few that strengthen your candidacy, and stop when you've covered the essentials.

Should I include soft skills in my resume skills section?

Generally, no. Soft skills like "communication" or "teamwork" belong in your bullet points, not your skills section. A recruiter won't believe you're a strong communicator because you listed it as a skill — they'll believe it when they read a bullet about presenting quarterly results to a C-suite audience or managing stakeholder alignment across three departments. The skills section is most effective when it contains verifiable, specific competencies that can be confirmed through a technical question or a tools-based assessment.

Should I tailor my skills section for every job application?

Yes. Your skills section should reflect the language and priorities of each job description. This doesn't mean fabricating skills — it means reordering them, adjusting category labels, and emphasizing the ones that match what the employer is asking for. A data analyst applying to a marketing analytics role should lead with marketing-adjacent tools like Google Analytics and Looker. The same person applying to a finance role should lead with financial modeling tools like Excel (advanced) and Bloomberg Terminal. The underlying skills are the same; the presentation changes to match the audience. This is one of the simplest and most effective ways to optimize your resume for each application.

Do ATS systems actually scan the skills section?

Yes. Most applicant tracking systems parse the skills section and match its contents against the job requirements. Some ATS platforms weight skills-section matches differently than in-context mentions, but having keywords in both places — your skills section and your bullet points — gives you the strongest chance of passing automated screening. The skills section serves as a quick-reference index for both software and human reviewers. Think of it as the table of contents for your resume's competencies: it tells the reader what's there and where to look for proof.

Related resources

← Back to All Resources