Skills to put on a resume: examples by role and experience

Choose skills from the work you need to do

A skills section is easier to write after you have read the job description and listed examples of your own work. Circle the tasks that matter to the role, then name the tools, methods or knowledge you have actually used for them. A requirement you have not used stays a learning goal or a gap.

The following fictional applicant, Alex Chen, is applying for an operations coordinator role. Alex has made weekly Excel pivot-table reports, checked duplicate CRM contacts and maintained a handover list with sales. Alex has never written SQL or configured a CRM. These facts determine what goes on the resume.

Skills examples for different jobs

Use the examples below to decide how specific your wording needs to be. Each row describes a separate fictional person who has done the stated task. It is not a list of requirements for every job in that field. Pick the terms that fit both your evidence and the particular posting.

UC Davis distinguishes knowledge-based skills from transferable skills. Tools and job-specific methods often work well as short entries; abilities such as collaboration become more convincing when an experience bullet shows what you did.

Describe your level with a task you can explain

“Advanced” and “proficient” can mean different things to different readers. Add a short task or setting when the level would otherwise be unclear. If you use a level word, be ready to explain what you can do independently and where you still need help.

Five stars or “Python 85%” give the reader little context unless there is a defined assessment behind them. A short description of actual use is easier to discuss. Keep course experience labelled as course experience; list a certificate by its actual name and issuer if it is relevant.

A complete skills-section rewrite

Alex’s draft initially copied attractive phrases from the posting. The revised section keeps only supported entries. Coordination appears in an experience bullet, where the reader can see the work involved.

An accompanying bullet could read: “Maintained a shared handover list with the sales team, recording the owner and next action for open customer requests.” This describes collaboration without claiming Alex managed the sales team.

Place the section where it helps the reader

Use a heading such as Skills or Technical Skills and group related entries when that makes them easier to scan. CareerOneStop treats the section and its position as choices, rather than a fixed requirement. A short technical list can appear near the top when it is central to the role; stronger project or work evidence may deserve that space instead.

In Evarlio, edit the skills in your resume content, then inspect the result in Resume Studio. For example, place Alex’s short section in #002 Clarity and check it beside the work history. Keep useful descriptions readable instead of shrinking the type to fit a longer list. Export the PDF and check the reading order and any fields filled by the application portal.

Questions about resume skills

How many skills should I include? Use the space needed for relevant, distinct skills you can support. There is no number that guarantees a better application. Remove duplicates and terms that add no useful information before adding another line.

Can I include a skill I am learning? Describe the current scope, such as a course or a small project, when it is relevant. “Learning SQL” does not satisfy a job’s requirement for independent SQL work. Leave it out if it distracts from stronger evidence.

Should soft skills be listed? Choose a small number that matter to the role and support them with actions in your work or projects. A list of “teamwork, leadership, communication” alone does not explain what you contributed.

Should every keyword in the posting appear? Include a term where it accurately names your knowledge or work. The skills section should agree with the rest of the resume and with what you can explain in an interview.