Resume Skills Section Examples: What to Keep and What to Swap

Recruiters scan a skills section to confirm a match. Applicant tracking systems (ATS) parse it to rank one. Most job seekers write theirs once and never touch it again, which is exactly backwards, because the skills section is the easiest part of a resume to tailor and the part where tailoring pays off fastest.

This guide gives you 15 example skills sections by industry, each with a note on what to keep across every version of your resume and what to swap per posting. It also answers the format questions that come up in every search, from the right hard-to-soft ratio to whether labeled categories beat a flat list.

Your skills section has two readers, and they want the same thing at different speeds. The ATS parses your resume into structured data so a recruiter can search and filter candidates by keyword. The recruiter then scans the parsed result, or the PDF itself, looking for a handful of terms from the job description. For both readers, the section works as a checklist. It either confirms you have what the posting asks for or it doesn't.

That is a narrower job than most people give it. The skills section is not where you show personality, and it is not an inventory of everything you have ever done. Its purpose is to surface the specific, searchable terms that connect your experience to this posting, fast enough that a scan measured in seconds still finds them.

It also has one property no other section shares. Rewriting a work-experience bullet takes real thought. Swapping four skills to match a posting takes under a minute. That makes the skills section the highest-return edit in per-job tailoring, which is why the second half of this article is about changing it and only the first half is about writing it.

Hard skills carry the section. A hard skill is teachable and testable, like SQL, Figma, financial modeling, or IV therapy. A soft skill describes how you work, like communication or adaptability. Both matter in hiring, and they belong in different places on the page.

For most roles, aim for roughly 80 percent hard skills in the section itself. For engineering and data roles, make it 100 percent. The reason is mechanical rather than philosophical. Recruiters run keyword searches on hard skills because hard skills are unambiguous; nobody types team player into a candidate filter. A soft skill sitting in a skills list is a claim without evidence, and recruiters have learned to skim past it.

Soft skills earn their place in your bullets instead, attached to an outcome. "Conflict resolution" as a list item is noise. "Cut escalated tickets in half after introducing a de-escalation script for the support team" proves the same skill and gives the interviewer something concrete to ask about. For a fuller breakdown of where each type belongs, see our guide to hard skills vs. soft skills on a resume.

Keep the section small. Eight to fifteen skills is the working range. Below eight you look thin, and past fifteen you dilute the terms that matter. Every skill on the list should be one you could discuss for ten minutes in an interview without sweating.

The examples below are realistic, current skills sections you can adapt. Treat the tool names as placeholders for your actual stack, and never list a skill you have not used. Each example ends with a keep-versus-swap note, because the right list for one posting is the wrong list for the next.

• Languages · Python, TypeScript, SQL
• Frameworks · React, Node.js, FastAPI
• Infrastructure · Docker, Kubernetes, AWS, Terraform, GitHub Actions

Keep the languages line stable across versions. Swap the framework and infrastructure lines to mirror each posting, since a team on GCP will search for GCP and skip a resume that only says AWS.

SQL, Python, Tableau, BigQuery, dbt, Excel, A/B testing, cohort analysis, stakeholder reporting

SQL and Excel stay on every version. The business intelligence tool is the classic swap; a team that lives in Looker searches for Looker, and Tableau alone won't surface you.

• Cloud · AWS (EC2, EKS, Lambda), Terraform
• Containers and CI/CD · Docker, Kubernetes, GitHub Actions, Helm
• Operations · Linux, Bash, Python, Datadog, incident response

Keep the containers line and your scripting languages. Swap the cloud provider and the monitoring tool to match the posting exactly, because those are the terms recruiters filter on first.

SEO, Google Analytics 4, Google Search Console, HubSpot, paid social (Meta, LinkedIn), email automation, conversion rate optimization, marketing attribution

SEO and GA4 rarely leave the list. The automation platform and the paid channels rotate; a posting built around SEMrush and paid search wants those exact words, in that exact form.

SEO writing, editorial planning, WordPress, Google Search Console, keyword research, content briefs, AI-assisted drafting, performance reporting

The writing and SEO core stays. Swap the CMS and analytics tools per posting, and if the job description names a specific content type, video scripts for example, put it on the list.

Product roadmapping, user research, A/B testing, SQL, Jira, Amplitude, PRD writing, stakeholder management, go-to-market planning

Roadmapping and user research stay put. Swap the analytics stack and the delivery tooling; a posting that says Mixpanel and Linear is telling you exactly what its recruiter will search for.

Agile, Scrum, risk management, budget tracking, resource planning, Asana, stakeholder communication, vendor management

Methodology terms do the heavy lifting here, so match them to the posting; a Waterfall shop asking for PMP certification wants different words than a Scrum team. Our breakdown of the skills project management postings actually ask for goes deeper on which terms recur.

Salesforce, pipeline management, outbound prospecting, discovery calls, negotiation, forecasting, MEDDIC, contract renewal

Pipeline management and negotiation travel everywhere. The CRM and the sales methodology are the swaps; if the posting says HubSpot and Challenger, mirror both.

Zendesk, live chat support, ticket triage, de-escalation, knowledge base writing, CSAT improvement, SLA management

De-escalation and ticket triage stay. Swap the help desk platform per posting, and add the industry's tools when the posting names them, like a POS system for retail-adjacent support roles.

Patient assessment, medication administration, Epic (EHR charting), IV therapy, telemetry, patient education, BLS, ACLS

Clinical skills and certifications are the stable core. The electronic health record system is the swap; a hospital on Cerner searches for Cerner, and your specialty skills should match the unit in the posting.

Financial modeling, forecasting, variance analysis, Excel (advanced), SQL, Power BI, GAAP, month-end close

Modeling and Excel never leave. Swap the reporting tool and any framework the posting names, such as IFRS instead of GAAP for international employers.

Workday (HRIS), onboarding, employee relations, benefits administration, performance review cycles, HR compliance, ATS administration

Employee relations and onboarding stay. The HRIS is the highest-value swap on an HR resume; postings name these systems precisely because recruiters filter on them.

Figma, user research, wireframing, prototyping, usability testing, design systems, accessibility (WCAG)

Figma and your research methods hold steady. Swap in whatever handoff or research tools the posting names, and keep accessibility on the list; it shows up in postings more often than most designers expect.

Calendar management, travel coordination, Microsoft 365, expense reporting, meeting minutes, vendor coordination, document management

The coordination skills stay. Swap the office suite and any named systems, like Concur for expenses or a specific scheduling tool, whenever the posting mentions them.

POS systems, cash handling, inventory management, upselling, opening and closing procedures, shift scheduling, customer complaint resolution

Cash handling and complaint resolution are universal. Name the exact POS or reservation system when you know it from the posting or the brand, since managers scan for the system they already run.

Two postings with the same job title rarely ask for the same skills. This is the pattern we see every day inside Roleframe's tailoring engine, which reads job descriptions the way a recruiter does before matching them against a resume. One Marketing Manager posting is built around HubSpot and lifecycle email; the next is built around paid acquisition and GA4. A static skills section fits one of them and quietly fails the other.

The swap rule fixes this. Split your skills into a stable core and variable slots. The core, roughly two thirds of the list, is your professional identity, the skills every posting in your target role expects to see. The remaining slots exist to be swapped, per application, with the exact terms the posting uses.

The practical setup is a base resume that holds your full skill inventory, more than you would ever show at once, plus tailored versions that select from it per job. You never rewrite the master; you spin off a version for each application. We cover the mechanics in our guide to building a master resume.

One boundary keeps all of this honest. Swapping means selecting and rewording skills you genuinely have. It never means adding a skill because the posting wants it. If the posting asks for Kubernetes and you have never touched it, that gap is real, and the interview will find it.

An ATS does less magic than the horror stories suggest. When you apply, the system parses your resume into structured fields, name here, employer there, skills in their own bucket. Recruiters then search and filter that database by keyword, or the system scores your parsed text against terms pulled from the job description. Your resume is rarely auto-rejected by a robot. It is far more often never found by a human search.

Exact wording decides whether you are found. Many systems match terms literally, so "Google Analytics 4" and "GA4" can behave as different keywords, and "search engine optimization" may not match a filter set to "SEO." Using the posting's precise terms beats using your preferred synonym, every time.

For the full playbook on choosing which terms to target, see our guide to ATS resume keywords.

The keyword dump is the forty-skill wall of text, every tool the candidate has ever opened, crammed into one block. It usually comes from good intentions, an attempt to cover every possible search. It backfires with both readers.

Recruiters read a dump as a lack of self-awareness. When Photoshop sits next to Kubernetes next to Microsoft Word, the list says the candidate cannot tell which skills matter for this job, so the recruiter has to guess, and guessing takes longer than the scan allows. The dump also buries your genuine strengths; the six skills that would win you the role are camouflaged by thirty that won't.

It creates interview risk too. Every listed skill is fair game for questions, and one shaky answer about a skill you listed damages trust in the skills you actually own. The filter is simple. If you would be uncomfortable spending ten minutes of an interview on a skill, it comes off the list.

Format matters less than content, but three patterns cover nearly every case, and one common pattern actively hurts.

Labeled categories are the current default for technical resumes, typically clusters for languages, frameworks, and tooling, because a recruiter searching for one term can see its neighbors and infer depth. For everyone else, a flat list under a plain "Skills" heading does the job. Place the section high on the page, just under your summary, when skills are your strongest match signal, and lower when your work history is stronger; our guide to resume section order walks through the logic by experience level.

Manual matching works. Open the posting, highlight every skill and tool it names, compare that against your inventory, swap what needs swapping, reword what needs rewording. Budget around 20 minutes per application. The problem is arithmetic; at twenty applications a week, manual matching is where tailoring discipline goes to die, and most people quietly fall back to one static resume.

This is the specific problem Roleframe was built for. Paste a job posting into your role workspace and a pipeline of AI agents reads it like a recruiter, extracts the exact keywords its filters will scan for, checks which ones your resume already covers, and proposes swaps and rewrites for the gaps. You approve every change before it saves, your base resume stays untouched, and the export is a clean PDF that matches the editor exactly.

Whatever tool you use, hold it to two standards. It must use the posting's exact terms rather than paraphrases, and it must never invent experience to close a gap. Generic AI rewrites fail the first test constantly, which is why so many AI-touched resumes read alike; we wrote about the fix in why your AI resume sounds generic.