What to put in the skills section of a resume, with examples

Put the skills the job posting asks for in your resume skills section, but only when they are true for you. Start with required tools, systems, methods, certifications, languages, and job-specific knowledge, then cut anything you cannot connect to a job, project, class, volunteer role, or portfolio example. The best skills section is not a keyword dump. It is a short map to proof elsewhere in your resume.

Start with the skills the posting asks for

The right skills to put on a resume are the ones that match the role you want next. Pull them from the posting first, not from an old resume template.

Hard skills usually carry this section because they are specific and searchable. Think SQL, QuickBooks, Salesforce CRM, Google Analytics, patient scheduling, financial reporting, Python, OSHA safety, Spanish, or PMP. Soft skills can belong too, but only when the posting names them and your experience section proves them.

Use the employer's wording when it is accurate. If the posting says SQL, do not list only database querying. If it says Salesforce CRM, do not hide that under customer database tools. That wording makes your fit easier to see because it matches the terms the employer chose.

Do not list a skill you cannot explain in an interview. If you cannot answer where you used it, what you did with it, and what kind of work it supported, leave it out or learn it before claiming it.

FitMyRole can compare your resume to one target posting, name missing keywords and requirements, and tailor your existing lines in the posting's words without adding experience you do not have.

Turn the job posting into your skills shortlist

Use the posting as your source document. You are not trying to add every possible skill in your field. You are trying to show fit for this job.

Start with this process:

1. Copy the posting into a working document.
2. Highlight required tools, systems, credentials, methods, and domain knowledge.
3. Mark repeated phrases, especially terms that appear in the job title, responsibilities, and qualifications.
4. Separate required skills from preferred skills.
5. Cross out anything you have not used.
6. Keep the skills you can prove in your work, projects, education, or volunteer experience.

Exact language matters when it is honest. If the posting says CRM and you used Salesforce, list Salesforce CRM. If it says marketing automation and your experience is in HubSpot workflows, list HubSpot marketing automation. This gives the employer's keyword and your specific tool in one clean phrase.

Synonyms are fine when they clarify. Do not swap in a different skill to look closer than you are. Tableau is not the same as Power BI. Bookkeeping is not the same as financial modeling. Scheduling is not the same as workforce planning. If the terms overlap, be precise about your version.

If the posting is thin, use it first anyway. Then check a neutral occupation source, such as O*NET OnLine, for common tasks, tools, and skills tied to that occupation. Treat that as a backup reference, not a replacement for the employer's own requirements.

For a deeper walkthrough of this step, use the guide to finding keywords in a job description. It will help you separate real requirements from filler language.

Group skills so a recruiter can scan them fast

A flat list is hard to read when it mixes tools, methods, and credentials. Group your skills by the way the role thinks.

There is no universal set of headings. A data role may need Analytics, Tools, and Programming. An operations role may need Scheduling, Customer operations, and Systems. A compliance-heavy role may need Regulatory knowledge, Documentation, and Audit support.

Mirror the posting when possible. If the posting has a section about Marketing automation, use that phrase as a group if it fits your experience. If it asks for Financial reporting, do not bury that under a generic Business skills label.

Avoid duplicate phrases. Do not list Excel, Microsoft Excel, and spreadsheets as separate skills unless the posting makes a meaningful distinction. Use the clearest version once, then prove it in a bullet.

For closer models, compare role-specific guides such as administrative assistant resume skills, software engineer resume skills, product manager resume skills, and resume examples by job title.

Use hard skills first and soft skills only with proof

Hard skills are tools, systems, methods, languages, credentials, and job-specific procedures. They usually deserve the most space in the skills section because they tell the employer what work you can do.

Soft skills are behaviors or ways of working: communication, collaboration, leadership, prioritization, problem solving, and adaptability. They matter, but they are weak when listed alone. A recruiter learns more from a line that shows what you led, clarified, fixed, trained, or coordinated.

Harvard's resume guidance recommends action verbs and accomplishment-focused bullets, which is a better place to show many soft skills than a crowded skills list from its resume guidance. If the posting explicitly asks for stakeholder communication, you can list it. Then make sure a bullet shows the setting.

Soft skills are not bad. Empty soft skills are the problem. If the job needs calm customer escalation, conflict resolution, or executive communication, name it only if your bullets show it.

Choose a tight list and cut anything you cannot prove

There is no single correct answer to how many skills to list on a resume. The right list is the shortest set that covers the posting's core requirements and fits cleanly on the page.

Use this editing rule: keep a skill if it appears in the posting, supports the job you want next, and can be proven elsewhere in the resume. If it fails one of those tests, cut it or move it out of the main skills section.

• Keep skills named in the posting that you have used.
• Keep tools, licenses, systems, and methods required for the role.
• Keep preferred skills when they strengthen your fit and you can prove them.
• Cut outdated software that does not matter to this job.
• Cut beginner-level tools unless the role asks for them or they support a career change.
• Cut personal interests unless they are directly relevant to the job.
• Cut generic traits such as hardworking, motivated, and fast learner.
• Cut skills from an old career path if they distract from the target role.

Resume length affects the section too. A shorter resume needs fewer, sharper groups. A longer resume can carry more specialized tools when they matter to the role, but it still should not read like an inventory.

If the skills section is forcing awkward formatting or pushing stronger experience out of view, read the guide on choosing whether your resume should be one page or two. The answer depends on relevance, not a rigid rule.

Prove the skills section inside your bullet points

The skills section gets the term onto the page. Your bullet points show where and how you used it.

Use this pattern:

Skill + task + context + result or scope

The result does not have to be a percentage. It can be scale, frequency, audience, volume, deadline, risk, or business purpose. If you do use a result, it must come from your actual record.

Do not add tools, clients, metrics, platforms, or outcomes that your original experience does not support. Honest tailoring means choosing the strongest true details, not upgrading your background on paper.

If you need more models, use these resume bullet point before-and-after examples. If you have scope but not clean metrics, read how to quantify resume bullets without numbers honestly.

Format the skills section so it stays readable

Use plain text skill names separated by commas, or short grouped lines like the examples above. Avoid icons, skill bars, dense columns, graphics, and decorative layouts that make the section harder to read.

Acronyms and full names can both matter when they are accurate. If the posting uses Search engine optimization and SEO, write Search engine optimization (SEO). If it uses Customer relationship management, and you used Salesforce, write Salesforce CRM.

Avoid rating scales such as Excel: expert or Python: advanced unless the employer asks for a formal proficiency level. Ratings are subjective and take space away from proof. A bullet that shows what you built, analyzed, scheduled, tested, or supported is stronger.

Use a single-column, text-based layout so the skill names stay in a normal reading order. Keep the section simple enough that a person can scan it quickly and an applicant tracking system can parse the words in the right order.

Before you submit, run through an ATS-friendly resume checklist and check that your file is readable, your keywords match the posting, and every listed skill is backed by real experience.

A strong resume skills section is narrow, honest, and tied to the posting. Choose the employer's language when it matches your record, group related skills so they scan fast, and use your bullets to prove the list.