I choose resume skills by asking one question: which abilities will help this candidate perform the target job, and where is the proof? A long list may look impressive, but it often makes the important skills harder to find.
I separate tools from working abilities
I usually divide skills into two groups in my notes. The first group contains technical or job-specific tools: Excel, Salesforce, SQL, AutoCAD, bookkeeping, payroll processing, or bilingual customer support. The second group contains broader abilities such as planning, negotiation, documentation, analysis, and stakeholder communication.
On the resume, I may combine them in one section, but I still keep the distinction clear in my thinking. A software tool can be tested directly. A broader skill needs an example in the experience section.
I start with the job description
I mark every skill that appears in the posting and sort it into required, preferred, and incidental. Then I compare that list with the candidate’s real experience. I prioritize the overlap.
If a posting repeatedly mentions scheduling, Excel reporting, and vendor communication, those three skills deserve more attention than a random list of twenty applications the candidate used once.
I keep only skills I can prove
I use a simple test: can the candidate answer, “When did you use this, and what did you do with it?” If not, I remove the skill or lower the claimed level. I would rather write “Excel: pivot tables, lookups, and monthly reporting” than “Advanced Excel” without context.
For communication, leadership, or problem-solving, I place the proof in bullets. The skills section can name the ability, but the experience section should demonstrate it.
I use the employer’s accurate terminology
Different industries use different names for similar work. I use the term from the posting when it honestly describes the candidate’s experience. For example, “client onboarding” may be more relevant than “new customer setup,” and “inventory reconciliation” may be clearer than “checking stock.”
I do not change the meaning to force a match. Accurate translation is useful; false equivalence is not.
I remove outdated and overly basic items
I usually remove skills such as email, internet, Microsoft Word, or typing unless the role has a specific requirement and the candidate can show a meaningful level. I also remove obsolete systems that no longer support the target role, unless they demonstrate relevant industry history.
A senior applicant does not need to list “teamwork” as a standalone skill when the resume already shows years of cross-functional leadership.
I avoid visual skill ratings
Stars, percentages, and progress bars create more questions than answers. What does 80% Excel mean? I prefer descriptive levels supported by tasks: basic formulas, pivot tables, dashboard creation, or VBA automation.
A practical narrowing exercise
I ask the candidate to write every possible skill, then reduce the list in three rounds. First, remove anything unrelated to the target. Second, remove anything that cannot be supported. Third, combine duplicates. “Communication,” “verbal communication,” and “interpersonal communication” may become one stronger skill with proof in the bullets.
My final skills section
A strong section may contain eight to fifteen focused items, depending on the role. I group related tools when it improves readability and keep the most important terms near the beginning.
The skills section should help the recruiter navigate the resume. It should not try to replace the experience section. Relevance and evidence matter more than volume.