Skills for a Resume: What to List, by Role and Level

Most skills sections are written in the wrong direction. The writer lists everything they know, then hopes some of it matches the job. Recruiters and applicant tracking systems (ATS) read the other way around. They start from the posting's requirements and check whether your resume covers them, so the skills worth listing are the ones that survive that comparison.

This guide works role by role. You get hard skills by job family in the wording postings use, rules for which soft skills to state and which to prove, counts and placement for the skills block, and field-by-field lists so you can go straight to your own role.

Before a skill earns a line on your resume, run it through three checks. Each one removes a different kind of dead weight.

The second filter is the one most resumes fail, and it has a fast self-test. Go through your skills block one entry at a time and find the bullet that proves each one. Any skill with no supporting bullet gets one of two treatments. Write the bullet, or cut the skill. Interviewers run the same test out loud, and 'it's on my resume but I haven't used it in a while' is a bad minute to have in a phone screen.

Postings name tools and methods, not categories. 'Spreadsheets' matches nothing in a recruiter's keyword search; 'Excel' and 'pivot tables' do. The table below lists the hard skills employers write into requirements sections, family by family, in the phrasing they use.

When a field has both a category term and a product name, list both. A nursing posting may say 'EHR' while the hospital runs Epic, so 'EHR (Epic)' covers both searches. The same logic applies to 'CRM (Salesforce)' and 'cloud (AWS)'.

One shift worth acting on now is that AI tool skills have moved into postings well outside engineering. Marketing, operations and finance postings increasingly name them. If prompt-based tools are part of your actual workflow, write the tool and what it produced; 'used AI' proves nothing, while 'built a prompt workflow that drafted campaign variants, then A/B tested the winners' proves a skill.

The rule is simple. State a soft skill when the posting uses it as a screening phrase. Prove it in a bullet when it's a trait. 'Cross-functional collaboration' is a phrase recruiters actually search; 'hard worker' is a self-assessment nobody has ever typed into a filter.

For a deeper breakdown of the two categories and how hiring teams actually weigh them, see hard skills vs. soft skills on your resume.

Eight to twelve entries is the working range for a dedicated skills block. Fewer than eight looks thin on a mid-career resume. More than twelve and nothing stands out, because a list of twenty skills reads as a list of zero priorities, and recruiters treat long skill walls as padding.

Skills live in three places on a strong resume, and each place does a different job.

Placement depends on your stage. A career changer or a student puts the skills block high on the page, right under the summary, because it's the strongest section they have. An experienced hire staying in the same field lets experience lead and places skills after it. The full logic is in our guide to resume section order by experience level, and for worked before-and-after versions of the block itself, these skills section examples show what to keep and what to swap.

Technical resumes get more room by grouping. A labeled line for languages, another for cloud platforms, another for data tools. Grouped entries fit more terms without the wall-of-tags effect, and parsers read them fine as long as the section keeps a conventional 'Skills' heading.

Delete the rating bars. Four dots out of five tells a recruiter nothing they can verify, and to an ATS parser a graphic is either invisible or noise. Text labels like 'expert' and 'proficient' fail the same way; they're self-grades with no scale behind them, and nearly every candidate marks themselves four out of five anyway.

Context does the job the bars pretend to do. Instead of 'Python, expert', write a bullet where the scale is visible, such as 'Built and maintained a Python service handling 40,000 requests a day'. The reader now knows more than any dot rating could tell them, and the claim is defensible in an interview.

Years belong where the posting asks for them. If the requirement says '5+ years of B2B sales', put 'six years of B2B SaaS sales' in your summary sentence rather than appending '(6 yrs)' to a skills-block entry. The one exception is spoken languages, where standard proficiency levels exist and readers expect them. 'Spanish (professional working proficiency)' is information; 'Excel (advanced)' is a shrug.

Open the posting and read only the requirements and responsibilities sections. Highlight every noun that names a tool, a method or a certification, and every phrase that repeats. Those are the screening terms, and they go onto your resume in the employer's wording, never a synonym. If the posting writes 'search engine optimization (SEO)', mirror the full form once and the acronym elsewhere; recruiter filters are literal, and you can't know which form was typed into the search box.

Two rules keep this honest. Every borrowed term needs a spot on your resume where it's true, and no term appears more often than a natural sentence allows. Keyword stuffing survives the software and dies with the human who reads the shortlist. The step-by-step version of this process is in how to pull resume keywords from a job description.

Across a dozen applications, running this comparison by hand gets tedious fast. Roleframe automates the reading half. Duplicate your base resume for a job and the fit report lists the keywords that posting screens for and marks which ones are gaps on your resume, along with an ATS score for that specific job. The edits stay yours. Remi, the career copilot, proposes rewrites bullet by bullet, and nothing changes until you approve it.

List the tools from coursework and projects, named precisely. A statistics course where you built models in R justifies 'R' in your skills block; the course title alone does not. Class projects, hackathons, a club treasurer role and campus jobs all generate real skills. At this stage the block usually sits high on the page, because it's your strongest section. Our student resume examples show the layout at each year of study.

You have more evidence than you think. Part-time and seasonal work produce skills postings actually name, such as point-of-sale (POS) systems, cash handling, scheduling software and inventory counts. Volunteering produces event coordination and fundraising outreach. What kills a no-experience resume is padding the block with traits like 'motivated' and 'fast learner'. A short list of concrete skills beats a long list of adjectives every time.

Specialize. By year six or seven, baseline tools like word processing earn no space, and the block should hold the ten or so terms that separate you from a generalist. If a skill was impressive at your first job and is assumed at your current level, cut it. The freed space goes to the platforms, methods and certifications your target postings keep repeating.

The block shifts from tools to scope. Budget ownership, hiring and team building, vendor negotiation, roadmap planning and cross-functional program delivery are the terms leadership postings screen for. Keep two or three hands-on skills for credibility, especially in technical management, where 'do you still read code' is a live interview question. At this level, the summary and the bullets carry more of the skills argument than the block does.

Retire the version numbers first. The skill is 'data migration', not the 2009 platform you happened to do it on; postings ask for the capability in current words, so translate yours. Then apply a simple test to everything older. If you haven't seen a posting ask for it recently, it's costing space a current term could use.

Two more categories deserve the cut. Skills you never want to use again, because listing a skill is an invitation to be handed that work. And duplicate eras, where three generations of the same tool collapse into the newest one you've used. A twenty-year career doesn't need twenty years of tooling on the page, the same way it doesn't need every job listed. Our guide on how far back a resume should go covers the cutoff logic for both.

The lists below are copy-ready starting points, one per field. Run every term through the three filters before it lands on your page, and keep the posting's phrasing wherever it differs from ours.