A useful skills section gives the reader a quick inventory of relevant capabilities. The rest of the resume explains where and how you used them. This guide focuses on writing US-English job-application resumes; follow the posting's instructions where they differ.
About the examples
All candidate profiles, sections and evidence bullets in this guide are constructed illustrations. They are not real candidate results or a list of qualifications every employer requires. Copy an arrangement only after replacing its content with your own supported skills.
Choose skills by comparing requirements with evidence
Read the posting for named tools, methods, responsibilities and qualifications. Then identify which you actually meet. A course, project, volunteer role or job can supply evidence, but those experiences are not interchangeable: describe the setting and level accurately. See the worked tailoring process for the wider resume edit.
- 1Mark the important requirements and distinguish required qualifications from preferences.
- 2For each skill you can claim, name a task or project where you used it and what you personally did.
- 3Choose wording that a reader will understand. Use the posting's term when it accurately names your capability.
- 4Group related items under short labels such as Office systems, Data analysis or Languages.
- 5Add an experience or project bullet for important skills that need context; leave unmet requirements as gaps.
UConn's resume-section guidance gives category examples such as computer skills, languages, laboratory techniques and industry software. UC San Diego's current resume guide recommends putting relevant technical skills first and using specific, position-focused professional skills. Those are useful organizing principles, not a mandatory list for every occupation.
Example 1: Administrative assistant skills
Illustrative candidate facts: an office coordinator used Outlook to arrange meetings, maintained an Excel invoice log with sorting and filters, and wrote shared filing instructions. This example emphasizes office-support work rather than executive responsibility.
Illustrative skills section — administrative assistant
Office systems: Microsoft Outlook; Excel sorting and filters; Word document formatting. Administration: Meeting coordination; invoice tracking; document filing. Written communication: Internal filing instructions; meeting agendas.
| Listed skill | Illustrative evidence bullet | Why this wording fits |
|---|---|---|
| Meeting coordination / Outlook | Coordinated meeting invitations and room bookings in Outlook, checking attendee availability before sending agendas. | Names the actual coordination task without claiming responsibility for an executive's whole calendar. |
| Excel sorting and filters / invoice tracking | Maintained an invoice log in Excel and used sorting and filters to identify items awaiting follow-up. | States the spreadsheet functions used instead of calling every Excel capability advanced. |
| Internal filing instructions | Wrote shared filing instructions for recurring office documents and updated them when the process changed. | Shows a specific writing task instead of an unsupported communication rating. |
See the administrative assistant resume examples for how the skills section fits into a full resume. Replace the software and scope if your experience differs.
Example 2: Executive assistant skills
Illustrative candidate facts: an assistant supported two executives, resolved calendar conflicts, prepared multi-city itineraries and reconciled expenses using Concur. This is a different scope from general office administration, without implying that every executive-assistant opening uses these tools.
Illustrative skills section — executive assistant
Executive support: Calendar-conflict resolution; travel itinerary preparation; meeting materials. Systems: Microsoft Outlook; Excel expense tracking; SAP Concur expense reporting. Coordination: Stakeholder scheduling; confidential meeting-document handling.
| Listed skill | Illustrative evidence bullet | Why this wording fits |
|---|---|---|
| Calendar-conflict resolution | Managed scheduling requests for two executives and resolved conflicts by confirming meeting priorities and attendee availability. | Gives the support scope and action; it does not turn scheduling into an invented revenue result. |
| Travel itineraries / Concur | Prepared multi-city itineraries and reconciled travel receipts with expense reports in Concur. | Connects the named system to a task the candidate actually performed. |
| Confidential document handling | Prepared meeting packets and shared restricted materials with authorized attendees using the team's access procedures. | Describes the practice without revealing private business information or inventing a security qualification. |
Use the executive assistant resume examples to review complete sample structures. Keep confidential details out of any example you adapt.
Example 3: Data analyst skills
Illustrative candidate facts: an analyst queried a reporting database with SQL joins, cleaned CSV data in Python with pandas, built a Tableau dashboard and tracked project changes with Git. Each named tool has a corresponding piece of work.
Illustrative skills section — data analyst
Data querying: SQL joins, aggregation and data checks. Analysis: Python; pandas; CSV cleaning. Reporting: Tableau dashboards; metric definitions. Version control: Git.
| Listed skill | Illustrative evidence bullet | Why this wording fits |
|---|---|---|
| SQL joins and data checks | Joined order and product tables in SQL and checked duplicate records before preparing the monthly reporting dataset. | Names techniques used and the purpose of the checks without claiming all SQL expertise. |
| Python / pandas | Used pandas to clean CSV extracts, document missing-value handling and reproduce the same preparation steps for the next reporting period. | Gives context for the programming skill rather than listing a language without an application. |
| Tableau / metric definitions | Built a Tableau dashboard and documented the calculation and source field behind each displayed metric. | Demonstrates reporting work; it does not invent downstream business impact. |
The University of Florida's technical resume guide recommends logical technical-skill groupings and project or experience evidence showing how the tools were applied. For a complete role sample, see the data analyst resume example.
Example 4: Career changer moving from retail to office support
Illustrative candidate facts: a retail shift lead coordinated shift schedules, recorded stock counts, handled customer returns and tracked unresolved requests. The candidate used Excel sorting and filters and a point-of-sale system, but has not used Salesforce or managed an executive's calendar.
Illustrative skills section — career changer
Coordination: Shift scheduling; follow-up tracking; stock-count records. Customer support: Returns processing; request escalation. Systems: Excel sorting and filters; point-of-sale transaction records.
| Relevant capability | Illustrative evidence bullet | What stays out |
|---|---|---|
| Scheduling | Coordinated shift changes and communicated the revised schedule to the store team. | Do not relabel this as executive calendar management if that work was not performed. |
| Records and follow-up | Recorded stock counts in Excel and maintained a follow-up list for unresolved customer requests. | Do not add database administration or an unfamiliar CRM simply because the new posting names it. |
| Customer support | Processed returns under store policy and escalated exceptions to the appropriate manager. | Do not change the official job title to Administrative Assistant to conceal the career change. |
For the wider story, see writing a career-change resume. Transferable skills can be relevant without being identical to every requirement of the target job.
A selection-and-evidence worksheet for your own resume
Work through this table before writing the final list. The first row is illustrative; use the remaining prompts for your own evidence. If you cannot support a requirement, record the gap rather than filling it with plausible wording.
| Posting requirement | Your actual evidence | Truthful skills wording | Where to show context |
|---|---|---|---|
| Illustration: Excel reporting | Maintained an invoice log using sorting and filters. | Excel sorting and filters; invoice tracking. | An experience bullet describing the log and follow-up task. |
| Name a required tool or method. | Which job, project or course used it? What did you personally do? | Name the tool and techniques you can explain. | Choose the relevant job or project; identify coursework as coursework. |
| Name a communication or coordination task. | What did you write, present, schedule or resolve, and for whom? | Describe the specific capability instead of a broad personality label. | Use an experience bullet that shows the action and audience. |
| Name a requirement you do not yet meet. | Record the gap, or accurately describe training currently in progress. | Omit an unsupported skill; do not call planned learning proficiency. | Mention relevant completed learning only where it helps explain fit. |
Placement, proficiency and professional skills
Place a compact, relevant skills section where it helps the reader assess fit. A technical role may warrant an early Technical Skills section, while a more general inventory can follow experience and education. UC San Diego's guide explicitly distinguishes relevant technical skills from general skills placed later. This is a relevance decision, not a universal ATS ordering rule.
Explain proficiency with a task or context when it matters: “Excel: pivot tables and lookup formulas” is more interpretable than four stars, but only use that wording if it is true. A language level should reflect your actual ability. Years of exposure do not automatically establish expert proficiency, and a course project should not be presented as professional employment.
Professional skills are useful when they describe the work. Replace a broad label such as “communication” with a relevant capability such as writing operating instructions or presenting findings to a nontechnical audience, then support it in a bullet. You do not need a separate list of personal qualities simply because another resume includes one.
Check the section before submitting
- ▸Can you explain each listed skill using a task, project or completed learning experience?
- ▸Are the most relevant skills visible, without an exhaustive list of everything you have encountered?
- ▸Do important claims have context in an experience, education or project section?
- ▸Do labels, spelling and abbreviations help the reader understand the tools and methods?
- ▸Have you removed unsupported skills, unexplained ratings and copied job-description text?
For terminology, read how to use resume keywords; for document layout, use the formatting checklist. The ATS resume guide hub organizes the wider workflow. Resume Leap can suggest wording and compare keywords, but its scores are editing aids, not verification that you possess a skill.