Resume Skills Section Examples: Choose Relevant Skills You Can Support

A resume skills section gives readers a compact view of relevant tools, methods and capabilities. It works best when it agrees with the evidence elsewhere in the resume and the work you can discuss in an interview.

The 15 examples below are illustrative lists, not current demand rankings or qualifications every person in a job title needs. Use them to organize your own experience. Tailoring means selecting accurate information; it never means changing the name of a tool you used into one the vacancy requests.

A short list can make information easier to find, but it cannot establish proficiency by itself. “SQL” names a skill; an experience or project entry can explain whether you wrote reporting queries, designed a schema or completed a course exercise.

Some recruiting systems support keyword search or extract information into fields. Features and employer practices vary, so the skills section is not a universal ranking checklist. It also is not necessarily the highest-value part of every application: a required qualification or a clear account of relevant work may matter more.

Start with the role’s responsibilities and your evidence. Keep terms that help the reader understand your fit and remove irrelevant detail when it obscures that information.

There is no universal 80/20 ratio, eight-skill minimum or 15-skill maximum. Technical and interpersonal skills can both be learned and demonstrated. A technical applicant may need communication evidence; a service applicant may need specialized software or process knowledge.

Use a skills section for concise labels and add examples elsewhere for important claims. A relevant interpersonal skill can be named, but “collaboration” becomes more informative when an experience entry explains the shared work. Technical terms need evidence too.

Select a length that is readable and relevant. Do not pad the list to reach a quota or remove useful information solely to meet one. The hard-versus-soft-skills guide explains how the categories overlap.

Each list below describes a hypothetical candidate. It is not a checklist to copy in full. Include only skills you actually have, at a level you can accurately explain, and distinguish study or personal projects from professional use.

• Languages: Python, TypeScript, SQL
• Applications: React, Node.js, FastAPI
• Development tools: Git, Docker, GitHub Actions

Adaptation check: Choose languages and tools relevant to the role from your actual work. If a vacancy requests GCP and your experience is with AWS, describe AWS accurately. You can explain related cloud experience without relabeling it as GCP.

SQL, Python, Tableau, Excel, cohort analysis, data validation, reporting

Adaptation check: If the role emphasizes Looker, include it only if you have used it. A Tableau project may still illustrate transferable reporting skills, but the products are not interchangeable claims. Identify whether A/B-testing work involved design, analysis or simply reporting results.

• Infrastructure: AWS, Terraform
• Delivery: Docker, Kubernetes, GitHub Actions
• Operations: Linux, Bash, monitoring, incident response

Adaptation check: Name services and practices you actually used. A lab deployment is useful experience when labeled as such, but does not establish production on-call ownership or expertise across an entire cloud provider.

Google Analytics 4, Google Search Console, email campaign planning, paid social, marketing reporting

Adaptation check: Specify platforms and channels only where your experience supports them. Separate writing campaign copy from managing budgets or attribution. No tool must remain on every marketing resume regardless of the target role.

Editorial planning, keyword research, content briefs, WordPress, copy editing, performance reporting

Adaptation check: For a role involving video scripts, include scriptwriting if you have relevant work. Do not add it simply because the posting names it. If AI-assisted drafting is relevant, describe your fact-checking and editing responsibilities.

Product discovery, roadmapping, user research, requirements writing, prioritization, stakeholder communication

Adaptation check: Select methods and tools used in your actual product work. Using an analytics dashboard does not automatically mean you designed experiments. Add SQL or a named analytics platform only at the level you can support.

Risk tracking, schedule coordination, budget monitoring, resource planning, stakeholder communication, vendor coordination

Adaptation check: Name Agile, Scrum or other methods where you actually used them, with relevant context elsewhere. A certification is a separate credential, not a synonym for a methodology. Our project-management skills guide gives more examples.

Salesforce, prospect research, discovery calls, pipeline reporting, negotiation, account planning

Adaptation check: Distinguish owning a pipeline from helping maintain it, and include a sales methodology only if you understand and have used it. Do not rename Salesforce experience as HubSpot to match an advertisement.

Zendesk, ticket triage, live-chat support, knowledge-base writing, escalation handling

Adaptation check: Describe the channels and responsibilities you handled. Customer satisfaction improvement is an outcome claim, not merely a skill label; support it with reliable evidence if you include it in a bullet. Do not imply authority to grant refunds or change policy if you escalated those requests.

Patient assessment, patient education, medication administration, clinical documentation, handoff communication

Adaptation check: This hypothetical list is not permission to perform a procedure. Include clinical tasks only within your education, demonstrated competence and applicable scope. NCSBN’s scope framework considers these boundaries. List actual licenses and current credentials separately, with accurate status. Name the EHR you used rather than substituting the hospital’s requested system.

Financial modeling, forecasting, variance analysis, Excel, Power BI, management reporting

Adaptation check: Explain the models or reports you built and the functions you used instead of relying only on “advanced Excel.” GAAP and IFRS are distinct frameworks; do not exchange their names to match a posting unless your experience supports both.

Onboarding coordination, employee-record maintenance, benefits support, review-cycle administration, HRIS reporting

Adaptation check: Be clear about your role in sensitive matters. Supporting employee relations is different from independently deciding legal compliance. Name the HR system you actually used and the functions relevant to the vacancy.

Figma, wireframing, prototyping, usability testing, design-system work, accessibility evaluation

Adaptation check: A tool name does not show the depth of your design practice. Explain a research or design decision in a project entry. If naming WCAG experience, describe the work and version relevant to it rather than implying that all your work is certified compliant.

Calendar coordination, meeting materials, expense-report preparation, document management, Microsoft 365

Adaptation check: Clarify the applications and tasks you used. Preparing expense reports is different from approving them. If your experience is in Google Workspace, name that accurately rather than replacing it with a different office suite.

Customer service, point-of-sale transactions, stock checks, opening procedures, complaint escalation

Adaptation check: Select tasks from your actual setting. Cash handling and scheduling are not universal responsibilities. Name a point-of-sale or reservation system only when you have experience with it, not merely because the employer uses it.

Keep a private inventory of skills with a note on where, when and how you used each one. For an application, select the relevant subset and give important items context in experience or project entries. There is no fixed fraction of the list that should stay constant.

For example, a candidate who has used both Tableau and Power BI may emphasize the one relevant to a vacancy. A candidate who has used only Tableau should keep that fact accurate and decide whether the related experience still makes the role worth applying for.

Update the inventory when you learn something, correct an error or stop using a tool. Save an application copy so later edits do not overwrite what you submitted. The master-resume guide explains how to maintain this record.

Parsing, search and evaluation are different operations. Greenhouse describes parsing as extracting resume information into candidate fields and notes that formatting can interfere with it. A parsing error does not itself establish that an application was rejected.

Its Boolean-search documentation describes phrases, alternatives and word variations. This is one product’s behavior, not evidence that every ATS requires identical wording or ranks candidates by the same formula.

Use clear names and expand an acronym when it helps the reader. “Google Analytics 4 (GA4)” can clarify terminology if that is the product you used. Do not add a version number that does not match your experience.

Our ATS keyword guide explains how to connect terminology to real work without treating a keyword score as a hiring decision.

If the section is difficult to scan, ask what each item contributes. Does it connect to a responsibility in the vacancy? Is it already better explained elsewhere? Would grouping related items make the section clearer?

Do not remove a relevant skill solely because you are not an expert. Describe your level accurately. For example, a recent course project can support “Python: coursework in data analysis”; it should not become “production machine-learning engineering.”

Self-ratings such as four stars out of five are difficult to interpret because the scale is undefined. A brief qualifier or a project example usually gives the reader more useful information. Interview confidence is not a proficiency test: feeling nervous about a skill does not mean you lack it.

Use the structure that makes your relevant skills easiest to understand. Test the final exported document rather than assuming one layout works in every system.

Place the section where it supports the application’s main evidence. A technical project resume may benefit from early skill labels; an experienced applicant may lead with relevant work history. There is no placement that guarantees extraction or selection. See resume section order for ways to organize the whole document.

Compare the posting with your evidence in two columns: requested skill and where you used it. Mark a genuine gap as a gap. You can choose whether to apply with adjacent experience without pretending that the missing skill is present.

Roleframe is our product. If you use it or another writing assistant, check proposed changes against your inventory before adding them. A tool can suggest terminology, but it cannot know an employer’s hidden search settings or establish your proficiency from a keyword alone.

Keep the submitted version separately and check the export for missing text or layout problems. The guide to generic AI resume wording explains how to keep concrete details from your actual work.