Skip to content
FreeNo sign-up

Resume Skills Generator

Enter a job title and get a grouped list of hard skills, tools, and soft skills employers in that role look for.

Free, no sign-up. Press ⌘ Enter to submit.

Skills to consider

Your drafts will appear here
Fill in the form and press suggest skills. The more specific you are, the better the result.

About the resume skills generator

The skills section is one of the most scanned parts of a resume, and one of the easiest to get wrong. Some people list everything they have ever touched. Others write "communication, teamwork, Microsoft Office" and stop. This resume skills generator gives you a starting list for a specific job title, grouped into technical skills, tools, and interpersonal skills, so you can pick the ones that are true for you.

If you paste a job posting, the list leans toward the terms that posting uses, which helps both recruiters and keyword searches find the match. Treat the output as a menu, not a finished section. The guide below shows how many skills to list, how to group them, and why every skill you keep should also appear somewhere in your experience.

How to use it

  1. 1

    Enter your target job title

    Use the title you are applying for, such as "accounts payable specialist" or "front-end developer." Add seniority if it matters, because a senior role calls for different skills than an entry-level one.

  2. 2

    Paste the job posting if you have one

    A posting lets the generator weight the skills that employer actually names. Without one, you get a broader list based on what the role usually requires.

  3. 3

    Keep only what you can prove

    Go through the list and select the skills you have used at work, in school, or in a project. Remove anything you could not discuss confidently for two minutes in an interview.

  4. 4

    Group, order, and paste

    Arrange your chosen skills into two to four labeled groups, put the posting's must-haves first, and add the section to your resume. Then check your bullets to back up each skill.

Hard skills, soft skills, and where each belongs

Hard skills are teachable and testable: software, programming languages, equipment, methods, regulations, languages, and certifications. Soft skills are the ways you work with people and problems: leadership, negotiation, conflict resolution, adaptability. Both matter, but they belong in different places on a resume.

Put hard skills in your skills section, because a recruiter can verify them at a glance and keyword searches match them directly. Show soft skills in your experience bullets, where you can prove them. "Strong communicator" in a list is a claim. "Presented quarterly results to a 40-person leadership group" is evidence. If a posting names a soft skill repeatedly, such as stakeholder management, it is fine to list it, but make sure a bullet backs it up.

A quick test: if you could take a course or exam in it, it is a hard skill. If you could only demonstrate it through how you handled a situation, it is a soft skill.

How many skills to list and how to group them

Most resumes need 8 to 15 skills in the skills section. Fewer than that can look thin for a technical role. Many more than that usually means the list includes basics or skills you barely used, which dilutes the ones that matter.

Grouping makes a long list readable. Use two to four labels that fit your field, then list skills in order of relevance to the job. Put the posting's required skills first within each group.

  • Technical roles: Languages | Frameworks | Cloud and DevOps | Data.
  • Healthcare: Clinical Skills | Systems (EHR) | Certifications.
  • Business and operations: Tools | Analysis | Process and Compliance.
  • Creative roles: Design Software | Production | Collaboration.
  • Skip proficiency bars and star ratings. They are hard for software to parse and invite questions about why you rated yourself a 3 out of 5. If level matters, use words: "Spanish (professional working proficiency)."

Where to find the right skills for a role

The best source is the job posting itself. Highlight every skill, tool, and certification it mentions, then note which appear more than once or sit under "requirements" rather than "nice to have." Those go first. Reading three or four postings for the same title shows you which skills are standard for the role and which are specific to one employer.

For a broader view, O*NET OnLine, sponsored by the U.S. Department of Labor, lists the tasks, software, and skills associated with hundreds of occupations. It is useful when you are entering a new field and do not yet know its vocabulary. Professional association job boards and the profiles of people currently in the role are good sources too.

Match the employer's exact wording when it is accurate for you. If the posting says "Microsoft Dynamics 365" and you wrote "ERP software," use their term. Spell out an acronym once if it might be searched both ways, for example "search engine optimization (SEO)."

Skills to cut from almost every resume

Some skills take up space without helping. Remove them unless the posting specifically asks for them.

After cutting, reread the list against the job post. Every remaining skill should either match a requirement or support your case for the role. If a skill does neither, it is taking space a stronger one could use.

  • Basics everyone is assumed to have, such as email, internet research, or typing, unless the role is data entry with a speed requirement.
  • "Microsoft Office" on its own. Name the specific tool and level instead: "Excel (pivot tables, XLOOKUP, Power Query)."
  • Outdated software that has been replaced in your field, unless the employer still runs it.
  • Vague traits like "hard-working" or "detail-oriented" with no proof nearby.
  • Skills you used once, years ago. If you cannot answer a follow-up question, leave it off.

Examples

Accounts payable specialist

Accounting and AP: Three-way matching, vendor reconciliation, 1099 reporting, month-end accruals, GAAP basics

Systems: NetSuite, SAP Concur, Bill.com, Excel (pivot tables, XLOOKUP)

Working style: Vendor communication, invoice dispute resolution, process documentation

Front-end developer

Languages: TypeScript, JavaScript, HTML, CSS

Frameworks and libraries: React, Next.js, Tailwind CSS, React Testing Library

Tools and practices: Git, GitHub Actions, Figma handoff, web accessibility (WCAG 2.2), Core Web Vitals performance tuning

Collaboration: Code review, design system contribution, agile sprint planning

Medical assistant

Clinical: Vital signs, phlebotomy, EKG, injections, specimen collection, sterilization

Administrative: Patient intake, insurance verification, scheduling, HIPAA compliance

Systems: Epic, athenahealth

Certifications: CMA (AAMA), BLS

Tips for better results

  • Put your skills section near the top if you are changing careers or applying for technical roles, and lower if your experience already shows the match.
  • Back every listed skill with at least one bullet, project, or credential elsewhere on the resume.
  • Use the same spelling and capitalization as the employer, such as "JavaScript" not "Javascript."
  • Update the order of your skills for each application so the posting's must-haves appear first.
  • List certifications in their own section if you have more than two, and keep only the skill names in the skills list.

Frequently asked questions

Most people should list 8 to 15 skills in a dedicated section, grouped into two to four categories. Technical roles often sit at the higher end because tools and languages add up quickly. If your list runs past 20, cut basics and anything you have not used recently, and keep the skills the posting asks for.

Include a soft skill when the job posting names it and you can back it up in a bullet. Otherwise, show soft skills through your experience instead of listing them. A bullet about leading a 10-person team through a system migration proves leadership far better than the word "leadership" in a list.

Applicant tracking systems parse the full text of your resume, including the skills section, and recruiters often search or filter candidates by skill terms. A clean, text-based skills list with standard names makes that matching easier. Avoid graphics, rating bars, and tables for skills, which some systems read poorly.

Yes, if you label them honestly. Add context such as "Python (intermediate, 2 personal projects)" or put the skill under a "Currently learning" line. Do not list a skill at the same level as ones you use daily if you could not handle a basic interview question about it.

Place it after your summary for technical roles, career changes, or when the posting is skill-heavy. Place it after your experience when your job titles and results already make your fit clear. In a two-column layout, a skills sidebar works if your template exports as readable text.

The list is built for the title you enter, and it becomes more specific when you paste a job posting. It is a starting point, so some suggestions will not apply to you. Keep the skills you genuinely have, remove the rest, and add any specialized tools your role uses that the list missed.