How to List Skills on a Resume (Format, Placement, Order)

We've covered which skills to put on your resume and which to cut. This one is about the part everyone gets wrong even when they've picked the right skills: how to actually lay them out. Where the section goes, how to group it, what order to use, and the formatting rules that decide whether an applicant tracking system can even read it.

Because here's the thing — a perfect list of skills, formatted wrong, gets parsed into garbage. Two columns become one scrambled line. A skills graphic becomes nothing at all. So let's get the mechanics right.

(If you haven't sorted out what belongs in the section yet, start with what skills to put on your resume and the 8 skills to cut — this post assumes you've already got the right 10-15.)

Where the skills section goes

Placement isn't a matter of taste — it follows from what your strongest selling point is.

Below your experience if you're mid-career or senior. Your work history is the headline; recruiters want to see where you've worked before they scan your toolkit. The skills section is a fast reference index, not the lead.

Above your experience if you're early-career, switching fields, or applying for a heavily technical role. When your skills are more compelling than your job history — a bootcamp grad with a strong stack, a career-changer whose new skills matter more than the old title — put them where the six-second scan lands first.

One rule regardless of placement: the skills section gets its own clearly-labeled block. Don't scatter skills into your summary and bury the rest in job bullets and hope it adds up. Recruiters and ATS parsers both look for a dedicated, labeled section.

How to group them

Below about ten entries, a single clean line or two works fine. Past ten, group into categories — it reads faster and signals organized thinking.

The categories should match your field. A few schemes that work:

• Technical roles: Languages · Frameworks · Infrastructure · Databases · Tools
• Marketing: Channels · Platforms · Analytics · Content
• Finance: Modeling · Systems · Reporting Standards
• Operations: Systems · Process · Data · Project Tools
• General / mixed: Technical Skills · Tools & Platforms · Certifications · Languages

The point of categories isn't decoration — it's that a recruiter scanning for "the database experience" can jump straight to the Databases line instead of reading your whole list. Group by how someone would look for a skill, not by what looks tidy.

What order to use

Within the section, and within each category, order by relevance to the job you're applying for — not alphabetically, not by how good you are at each.

That means the order changes per application. If the posting leads with "SQL and data modeling," those move to the front of your list even if Python is your favorite. The first few skills in each line get read; the last ones get skimmed. Put the job's must-haves where the eye lands.

This is the same JD-driven logic as the rest of your resume: mirror the posting's priorities. If you want the posting's exact must-have skills ranked for you, paste your resume and the job description into the free Job Match tool — it returns the missing and matching keywords by importance, which is your ordering cheat sheet. (And here's the deeper ATS keyword method if you want the full version.)

“Your skills section order should change with every application. The job's must-have skills go first — the front of the line gets read, the back gets skimmed. Alphabetical order is a wasted opportunity.”

Share on X→

The formatting rules that keep it ATS-readable

This is where good skills sections go to die. Applicant tracking systems parse your resume into plain text and fields; anything that isn't simple text is a gamble. The rules:

No tables or multi-column layouts for skills. This is the big one. A two- or three-column skills grid looks efficient to you and reads as scrambled word-salad to many parsers — they read left-to-right across columns, turning "Python | Agile | SQL | Scrum" into "Python Agile SQL Scrum" or worse. Use a single column, or comma-separated lines within categories.

No graphics, icons, or skill bars. More on the bars below, but anything image-based is invisible to an ATS. If a skill only exists as a filled-in dot or a logo, it doesn't exist as far as keyword matching is concerned.

Plain separators. Commas or simple bullet points between skills. Skip the pipes, slashes, and decorative dividers that can confuse parsers.

Standard section heading, standard fonts, real text — not text baked into an image or a header/footer (many ATS parsers ignore headers and footers entirely, so nothing important goes there).

Match the posting's exact phrasing. If the job says "CI/CD" and you wrote "continuous integration," an older ATS may not connect them. Use their string.

The skill-bar mistake

Those little progress bars, five-star ratings, and filled-in dots next to each skill — "JavaScript ●●●●○" — feel like a clever way to show proficiency. Cut every one of them. Two reasons:

They're invisible to ATS. A bar is a graphic. The parser sees the word "JavaScript" if you're lucky and nothing at all if the label is baked into the image.

They're meaningless to humans. Your "4 out of 5" in Excel and mine are calibrated to completely different scales. A rating you assigned yourself, with no rubric, tells a recruiter nothing except that you like resume templates with skill bars. If proficiency matters, show it with evidence in your bullets — "built the team's reporting automation in Excel" beats "Excel ●●●●●."

The one place a proficiency label earns its keep is languages, where there's a shared vocabulary: "Spanish (professional working proficiency)," "French (conversational)." Use the real, recognized levels — and never inflate them, because it's the single easiest claim on your resume to test in an interview.

Dedicated section vs. woven into bullets

You'll do both, on purpose. Hard skills — the tools, languages, and technical competencies — live in the dedicated skills section where the ATS indexes them. Soft skills don't belong in the list at all; they get proven in your experience bullets as evidence. That split is worth understanding in full, because getting it wrong is what makes a skills section look amateur: hard skills vs. soft skills, and where each goes.

The best resumes do a third thing too: the most important hard skills appear in both places — named in the skills section for the keyword match, and demonstrated in a bullet ("migrated the analytics stack to BigQuery") for the proof. Named where it's scannable, shown where it's believable.

What a clean skills section actually looks like

A mid-level marketer, grouped and single-column:

Skills Channels: Paid social, SEO, lifecycle email, ABM Platforms: Google Ads, Meta Ads Manager, HubSpot, GA4 Analytics: A/B testing, attribution modeling, SQL (reporting)

A software engineer:

Skills Languages: TypeScript, Python, Go Frameworks: React, Next.js, Node Infrastructure: AWS, Docker, Kubernetes, Terraform Databases: PostgreSQL, Redis

Notice what both do: standard "Skills" header, category labels, single column, comma-separated, exact tool names, no bars, no graphics, most-relevant skills first. Plain, scannable, parseable. That's the whole target.

The formatting checklist

Before you call the section done, run it:

1. Single column or comma-separated lines — no tables, no multi-column grids
2. Standard "Skills" heading, not a creative synonym
3. Categories if you have more than ~10 entries, labeled by how someone would search for a skill
4. Most job-relevant skills first, reordered per application
5. No skill bars, star ratings, dots, or icons
6. Exact phrasing from the posting for anything the ATS will match on
7. Nothing important in the header or footer (ATS often skips them)
8. Languages with real proficiency levels; no self-assigned ratings anywhere else

Everything on that list is mechanical — no judgment calls, just formatting that keeps a good list of skills from being wrecked on the way through the parser.

Want to see how your skills section reads to a stranger — human and machine? The free roast grades your resume in about 30 seconds, scores the skills section on its own, and flags formatting that would trip an ATS. It's the fastest way to catch a scrambled column or a stray skill bar before a recruiter's software does.