The resume skills section is the short block, usually headed Skills, that lists the tools, techniques and languages you can use. It does two jobs. It lets a person scanning your resume confirm in a few seconds that you have what the posting asks for, and it puts the posting's searchable terms on the page in plain text, where a recruiter's keyword search can find them. Getting it right comes down to four decisions: where it goes, what belongs in it, what order the items run in, and which items you can honestly defend. This post takes them one at a time, with an invented posting worked through at the end.
What the skills section is for
Start with the reader. MIT's career advising office describes the skills section as "a quick way for many readers to quickly identify if you have the skills needed for the role". That is the human job: a recruiter who has the posting open checks the list against it before reading anything else.
The second job is search. Greenhouse, one of the most widely used applicant tracking systems, documents a Full Text Search that recruiters switch on to find candidates matching their terms, with a snippet under each name showing how the terms appear in the profile. Greenhouse also tells candidates that its AI suggests keywords from the job description to recruiters, and that "when recruiters search for these terms, they'll find exact matches in candidates' applications." The skills section is the densest place on the page for those exact matches.
Neither job is helped by length for its own sake. A list of forty tools makes the recruiter hunt for the five that matter, and every item on it is a claim somebody may ask you about. The skills block is one section among several, and our guide to what to put on a resume shows where it sits in the full order.
Where to put it
There is no single correct position, and career offices do not agree on one. The useful question is what the job is defined by.
| If the role is defined by | Put the skills section | Why |
|---|---|---|
| Tools and techniques (engineering, data, design, IT, finance systems) | Near the top, under your name or summary | The first scan is a tool check, so give it the answer in the first lines |
| Experience and results (sales, management, operations leadership) | After experience, near the bottom | The first scan is for titles, employers and outcomes; skills support them |
| A career change or a first job | Near the top, often with projects next to it | Your titles do not yet say what you can do, so the skills and projects have to |
Two placement rules hold whichever you choose. Use a conventional heading such as Skills or Technical Skills, because Greenhouse lists resumes "without clear sections" among the causes of an unsuccessful parse. And keep it in the main body as real text, not in a sidebar column or a graphic. Our post on ATS friendly resume format covers why a two column layout can scramble the order a parser reads.
Hard skills, soft skills and tools
Most advice splits skills in two. A more useful split has three parts.
- Tools. Named software, platforms, languages and equipment: Salesforce, Python, AutoCAD, Epic, a forklift license. These are the most searchable words you own, because they are spelled the same way in every posting.
- Hard skills. Techniques that are not products: financial modeling, A/B testing, regression analysis, root cause analysis, contract negotiation. They are searchable too, though spelled less consistently.
- Soft skills. Teamwork, communication, problem solving, leadership.
Employers care about all three. In NACE's Job Outlook 2026 Spring Update, the top attributes employers seek on college students' resumes were the ability to work in a team, problem solve and communicate, and 85% of employers said they look for teamwork on the resume. (The survey had 185 respondents, ran from 12 February to 17 March 2026, and was sponsored by Jobscan.) But NACE's Shawn VanDerziel put the catch plainly in the accompanying release: "It is not enough for candidates to simply list their skills: Employers want to see examples."
That is why MIT's office advises keeping the list to "technical, procedural, language, or laboratory skills" and showing interpersonal skills in your experience bullets, where they have context. "Communication" on a skills line is unverifiable. "Ran the weekly status call for a 12 person launch team" is a piece of evidence. Put tools and hard skills in the skills section, and let the bullets carry the soft skills.
Resume scanners rank the categories the same way. Jobscan, which sells a resume match score, says on its homepage that its match rate weighs hard skills first, then education (only when the posting asks for an advanced degree), then job title, then soft skills, then other keywords. That is one vendor's scoring model rather than how any employer's system works, but it points the same way as the recruiter's habit: the named, checkable items carry the most weight.
Order by the posting
A skills section written once and sent everywhere is in the wrong order for almost every job. The fix is cheap: for each posting, put the tools it names first, in the posting's own spelling.
Order matters for the human reader more than for search. A keyword search finds "Looker" whether it is the first item or the fourteenth. A recruiter skimming the line reads the first few items and infers the rest. If the posting is built around Salesforce and your line opens with Photoshop, you have told the reader the wrong thing about yourself before they get to the part that fits.
Three ordering rules cover most cases:
- Required before preferred. If the posting separates them, follow its split.
- Repeated terms first. A tool the posting names in three places matters more than one it names once.
- Group by kind, then order inside each group. Labeled groups such as Languages, Data, Platforms keep a long list scannable, and MIT's guide suggests sub-sections when the list is long. Order the groups by relevance too, so the group the posting cares about leads.
Spelling counts here. Greenhouse's Boolean search help describes OR for alternatives and quotation marks for exact phrases, and does not describe automatic synonym matching. If the posting says "Google Analytics 4" and you wrote "GA", a recruiter has to think of your abbreviation to find you. Use the posting's form, and add the short form in parentheses if both are common. Our post on resume keywords goes further into exact phrases versus synonyms.
A worked example
Here is an invented posting and an invented candidate. Every name and detail is made up.
Marketing Operations Specialist, Fernhill Outdoor
Own our HubSpot instance: workflows, lead scoring and list hygiene. Keep HubSpot and Salesforce in sync. Build campaign reporting in Looker. Run A/B tests on email and landing pages. SQL is a plus.
The candidate's general skills section, written once:
Skills: Photoshop, Canva, Google Analytics, Mailchimp, HubSpot, Salesforce, Excel, SQL, WordPress, A/B testing, social media, communication, teamwork
Tailored for Fernhill:
Marketing automation: HubSpot (workflows, lead scoring), Salesforce, Mailchimp Data and reporting: Looker, SQL, Google Analytics, Excel Testing and web: A/B testing (email, landing pages), WordPress
What changed, and what did not:
| Change | Reason |
|---|---|
| HubSpot moved from fifth to first, with the posting's two named tasks after it | The posting names it twice and builds the job around it |
| Salesforce moved next to HubSpot | The posting's sync task joins them |
| Looker added | Only because, in this invented history, the candidate built Looker dashboards at a previous job and had left it off. If they had not, it would stay off |
| Photoshop, Canva and social media removed | Real skills, irrelevant to this posting; they bury the relevant ones |
| Communication and teamwork removed | They belong in bullets as evidence, not on a list |
| Employers, titles, dates and numbers elsewhere on the page | Untouched. Reordering skills never changes the facts |
The tailored version is shorter and runs in the posting's order. Every item on it is something the posting asked for and the candidate can talk about.
How many skills to list
Nobody has published a credible study of the ideal number, so treat any figure you read as somebody's preference. Two constraints do the work instead.
The posting sets the ceiling of what is relevant. NACE found that more than half of employers named ten or more skills they want, so a posting may well list a dozen items, and covering the ones you have is reasonable.
Your interview sets the ceiling of what is defensible. Every item is an invitation to a question. A useful working shape is two to four grouped lines on a one page resume. Past that, the list starts to read as padding, and the strongest items lose their position at the front.
Proficiency labels are optional. Words like "advanced" or "expert" are claims about level, and an interviewer may test them. If you use labels, keep them for spoken languages, where levels such as native, fluent or conversational are common and expected.
Skills you are still learning
A tool you used in a course, a bootcamp or a weekend project is a real skill at a small size. List it at that size:
- Put it with a qualifier: "Tableau (coursework)", or a separate line headed "Familiar with".
- Better, show it in a project bullet that says what you built: "Built a Tableau dashboard of city bike share usage from open data". A bullet answers the question an interviewer would ask.
- Leave off anything you have only read about. The test for every item is the same: could you talk about it for two minutes with someone who uses it daily? If not, it comes off.
This matters more when software is writing the list for you. ApplyEze, for example, writes a resume for every posting. It brings the posting's named skills and tools onto your skills line, even when your own record does not list them. That is a deliberate choice. There is no step to remove one before a live run, so use a dry run to see what it writes, and be ready to discuss anything on the page. A certification the posting asks for is not added unless you hold it. Your employers, job titles, dates, schools, degrees and certifications come from your own record, and code rejects a rewrite that adds a figure, employer, school or credential your record does not hold. Whatever tool you use, read the tailored resume before it goes out. Our guide to how to tailor a resume walks through the same checks by hand.