Job Description Skills Examples: How to List Skills That Attract the Right Candidates
Listing skills in a job description is not about dumping every possible tool and technology into a bullet point. It is about identifying the capabilities that are genuinely necessary for the role and presenting them in a way that helps candidates assess fit. This guide shows how to categorize skills, separate required from preferred, and avoid the mistakes that filter out qualified applicants.
All resources Job Description Skills Examples
Categorize skills clearly
Candidates scan skill lists to assess fit quickly. Grouping skills by category makes this easier and prevents the list from becoming an overwhelming wall of text. Common categories include technical skills, tools and platforms, domain knowledge, certifications, and soft skills. Each category should be labeled and contain 2-4 specific items.
- Technical skills — programming languages, frameworks, methodologies
- Tools and platforms — specific software, SaaS products, or systems
- Domain knowledge — industry expertise, regulatory knowledge, market understanding
- Certifications — professional certifications or licenses if required
- Soft skills — communication, leadership, problem-solving (use sparingly)
Separate required from preferred skills
This distinction is critical. Required skills are the ones a candidate must have on day one to perform the role. Preferred skills are ones that strengthen candidacy but can be learned. Conflating the two is one of the most common reasons qualified candidates self-select out. Research shows women are significantly less likely to apply when they do not meet 100% of listed skills. Be honest about what is truly mandatory.
- Required: skills without which the person cannot do the job
- Preferred: skills that differentiate candidates at the same baseline
- Required: limit to 5-7 items that are truly non-negotiable
- Preferred: include skills that would accelerate onboarding
- If a skill can be learned in the first month, it is not required
Be specific about tools and technologies
Vague skill listings like “proficient in modern web technologies” tell candidates nothing. List specific tools, versions, and frameworks. Instead of “experience with cloud platforms,” write “Hands-on experience with AWS (EC2, S3, Lambda) or equivalent.” Specificity helps candidates self-assess accurately and reduces the volume of mismatched applications.
- Name specific tools and platforms (not just categories)
- Include version or complexity level where relevant
- Specify depth of experience expected (daily use vs. familiarity)
- List actual programming languages, not “multiple languages”
- Mention integration or architecture context where applicable
Use soft skills sparingly and specifically
Soft skills are harder to verify and easier to claim, so listing too many weakens your requirements section. Focus on 2-3 soft skills that are genuinely critical to the role. Instead of generic “excellent communication skills,” specify what communication looks like in this role: “Present technical proposals to non-technical stakeholders weekly” or “Write detailed technical documentation for a distributed engineering team.”
Examples of effective skill listings
Here is how different categories of roles typically structure their skills sections. Each example separates required from preferred and uses specific language.
- Software Engineer: “Required: Python, PostgreSQL, REST APIs. Preferred: Kubernetes, Terraform, CI/CD experience.”
- Marketing Manager: “Required: Google Analytics, HubSpot, campaign management. Preferred: SQL, A/B testing tools, Salesforce.”
- Sales Representative: “Required: CRM experience (Salesforce or HubSpot), B2B sales. Preferred: SaaS sales, enterprise account management.”
- HR Manager: “Required: HRIS systems, employment law knowledge. Preferred: Workday, BambooHR, SHRM certification.”
Related resources
Related job descriptions
Frequently asked questions
How many skills should I list in a job description?
List 5-7 required skills and 3-5 preferred skills. This is enough to specify what you need without creating an intimidating wall of text. Each additional required skill filters out more candidates, so be selective about what is truly mandatory.
Should I list soft skills in the requirements?
Use soft skills sparingly. Focus on 2-3 that are genuinely critical to the role, and describe them in context rather than as abstract qualities. Instead of “excellent communication,” describe what communication the role requires: presenting to stakeholders, writing documentation, or leading meetings.
What if my role requires skills that are hard to find?
Be specific about the skill but flexible about how it was acquired. Candidates may have the skill from side projects, open-source contributions, bootcamps, or non-traditional experience. List the skill as required but avoid specifying it must come from a particular degree or company.
Use InstantJD to create your job description
Generate a scored, editable, hiring-ready job description in minutes — free for verified employers.