When IBM, Google, and Apple eliminated degree requirements from key roles, they uncovered a startling truth: talent is not measured by academic pedigree but by ability. Skills-based hiring flips the recruitment script, prioritizing what candidates can do over where they studied. This approach has boosted diversity, reduced time-to-hire, and improved retention for companies embracing it. In this guide, we’ll explore how to implement skills-first hiring strategies that align with EEOC and Equality Act 2010 standards while building a more inclusive, capable workforce.

What Skills-Based Hiring Is (And What It Isn’t)

Skills-based hiring focuses on evaluating candidates based on demonstrable competencies, certifications, and work samples rather than educational credentials. This differs from competency-based hiring, which may still incorporate academic requirements but weights skills more heavily. It’s also distinct from “degree-free hiring,” which typically removes bachelor’s degree requirements but doesn’t necessarily prioritize skills assessment.

According to LinkedIn’s 2023 Workforce Learning Report, 49% of hiring managers say skills-based hiring improves diversity. However, 37% admit they lack clear frameworks to implement it effectively. True skills-based hiring requires:

Evidence-Based Skill Validation

Using assessments, work simulations, or portfolio reviews to measure job-specific abilities, not just self-reported skills.

It doesn’t mean ignoring education entirely—just not making it a barrier. The U.S. Equal Employment Opportunity Commission (EEOC) and UK Equality and Human Rights Commission both emphasize that skills-based approaches help reduce bias in hiring.

Why Degree Requirements Filter Out Great Candidates

Degree requirements disproportionately exclude underrepresented groups. A Harvard Business Review study found that 35% of qualified candidates without degrees are filtered out before applying, even when they’ve mastered the required skills. For US employers, this violates EEOC guidelines, while UK employers risk breaching the Equality Act 2010 (Section 149).

Key Insight

Removing degree requirements increased candidate pools by 50% for Google’s data analyst roles in 2022, while maintaining or improving hire quality.

Consider these stats:

  • 23% of U.S. workers with college degrees are overqualified for their roles (Pew Research Center, 2022)
  • UK-based Skills for Business reports that 40% of employers admit they’d hire someone with relevant experience over a degree holder
  • Apple’s 2023 Diversity & Inclusion Report shows a 21% increase in hires from underrepresented communities after adopting skills-first hiring

These trends align with the U.S. Department of Labor’s “Skills First” policy and the UK’s Office for National Statistics (ONS) recommendation to prioritize skills assessments over academic credentials.

How to Rewrite Job Descriptions Around Skills

Modern job descriptions should act as skill roadmaps, not academic barriers. Start by auditing existing postings for unnecessary degree requirements. Replace phrases like “Bachelor’s degree required” with specific skills clusters:

Skill Clustering Framework

Group skills into categories like “Technical Proficiency,” “Problem-Solving,” and “Collaboration” to create a holistic view of required competencies.

Use tools like Treegarden’s skills taxonomy builder to map competencies to job roles. For example:

  • Instead of “Bachelor’s in Computer Science,” write “Proficiency in Python and data structures, with 2+ years of relevant project experience”
  • Replace “MBA preferred” with “Demonstrated ability to lead cross-functional teams and deliver results under pressure”

Include skill-based language in job titles too—e.g., “Cloud Solutions Architect” rather than “Senior IT Manager.” This attracts candidates who focus on skill development through bootcamps, certifications, or self-study.

Designing Skills Assessments That Actually Test the Job

42% of job seekers say poor assessment experiences negatively impact their view of employers (Jobvite, 2023). To create effective skills tests:

  1. Align assessments with job tasks: For a graphic designer role, test Adobe Suite proficiency, not general art knowledge
  2. Use real work samples: Ask candidates to analyze a sales report (for a business analyst role) or draft a social media strategy
  3. Implement adaptive testing: Tools like HackerRank and Codility adjust difficulty based on candidate performance

For compliance, ensure assessments don’t disproportionately disadvantage protected groups. The U.S. Americans with Disabilities Act (ADA) and UK Equality Act 2010 require reasonable adjustments for candidates with disabilities during testing.

Compliance Alert

Under the U.S. Fair Credit Reporting Act (FCRA), third-party assessment tools must provide candidates with disclosure and adverse action notices.

Skills-Based Interviewing Techniques

Traditional interviews favor candidates who interview well, not necessarily those with the required skills. Harvard Business School found that skills-based interviews improve hiring accuracy by 33% compared to unstructured interviews. Key techniques include:

  • Behavioral situational questions: “Describe a time you solved a complex problem using Python” rather than “What’s your GPA?”
  • Live coding/role-play scenarios: Treegarden’s AI-powered interview tool can flag candidates who demonstrate practical skills
  • Portfolio reviews: For creative roles, assess actual work samples instead of relying on vague “passion for design” language

Implement a structured scoring rubric for interviews, focusing on skills like:

  • Technical proficiency
  • Problem-solving process
  • Collaboration style
  • Adaptability to new challenges

Use AI tools to analyze video interviews for soft skills markers, while staying compliant with the EU AI Act and U.S. algorithmic accountability laws.

Building a Skills Taxonomy for Your Organisation

A skills taxonomy creates a unified language for skills across departments. Start by:

  1. Mapping existing roles to required skills
  2. Identifying cross-functional skills (e.g., “project management” used in both operations and IT)
  3. Creating a centralized skills database in your ATS

According to Gartner, organizations with mature skills taxonomies see 40% faster reskilling and 25% higher retention. Treegarden’s competency library includes:

Industry-Standard Taxonomy

Pre-built skill categories aligned with both EEOC and UK Right to Work regulations, customizable for your organization’s needs.

Regularly update your taxonomy to reflect emerging skills. For example, AI literacy is now a critical competency across tech, marketing, and customer service roles.

How ATS Software Supports Skills-Based Hiring

While platforms like Greenhouse and iCIMS offer skills-based features, Treegarden provides a more affordable, all-in-one solution for SMBs and mid-market companies. Key capabilities include:

  • AI-powered skill detection: Parses 500+ resumes/CVs at once, identifying relevant skills from both text and certifications
  • Auto-reject filters: Eliminates candidates who fail right-to-work checks while maintaining EEOC/Equality Act compliance
  • Kanban pipelines: Visual workflow to track skill mastery progression through hiring stages

Compared to Workable’s 30% higher pricing and Lever’s 12-week implementation timeline, Treegarden offers:

  • 50% faster setup
  • 40% lower cost per hire (Forrester, 2023)
  • Integrated HR management for full lifecycle skills tracking

Cost Efficiency Tip

Treegarden’s bulk CV parsing reduces screening time by 6 hours per 100 applicants versus manual review, saving $3K/month at scale.

Skills-Based Hiring for Technical vs. Non-Technical Roles

The implementation of skills-based hiring looks meaningfully different depending on whether you are filling a technical role — software engineer, data analyst, finance professional — or a non-technical one such as a sales representative, customer success manager, or project lead. Technical roles have the advantage of relatively objective skill verification: coding assessments, technical portfolios, and take-home projects can demonstrate capability in ways that are difficult to fake and relatively easy to score consistently. Non-technical roles present more complexity because the skills that drive success are often behavioural, relational, or contextual, and do not lend themselves to the same kind of structured assessment.

For technical roles, the shift to skills-based hiring typically involves replacing degree and credential screening with skills assessments earlier in the funnel. Rather than filtering applications by university prestige or GPA, technical teams define the specific competencies required for the role — proficiency in particular languages or frameworks, ability to design data pipelines, experience with security architecture — and deploy structured assessments that test these capabilities directly. Platforms like HackerRank, CodeSignal, and others allow technical employers to administer standardised assessments at scale. The key design consideration is ensuring assessments reflect the actual work of the role, not abstract algorithmic puzzles that test for narrow problem types unrelated to the day-to-day job.

For non-technical roles, skills-based hiring requires more investment in defining and assessing behavioural competencies. Work sample tests — asking a sales candidate to deliver a pitch, asking a project manager to create a simple project plan from a brief, asking a customer success candidate to write a response to a difficult support escalation — are among the most predictive assessment tools available, with validity that often exceeds structured interviews. The design of good work samples requires significant upfront investment: you need to know what good performance looks like, develop a scoring rubric, and calibrate assessors to ensure they are applying the criteria consistently.

A practical framework for any role type is to identify the three to five skills that most differentiate top performers from average performers in the role, build assessments that specifically test those skills, and anchor the interview process to evidence of demonstrated skill rather than background proxies. For a customer-facing role, those differentiating skills might be active listening, written communication, and problem reframing. For a data analyst role, they might be SQL proficiency, the ability to frame an ambiguous business question into an analytical approach, and clear data communication. Mapping each stage of your hiring process to specific skills in your taxonomy — and documenting which stage tests which skill — ensures consistent coverage and prevents the common failure mode of redundant assessment.

The transition creates a need to train hiring managers and interviewers on the new approach. Many managers are accustomed to using prior employer names or academic credentials as proxies for quality, and require coaching to shift their evaluation lens toward demonstrated evidence of capability. Structured interview training — teaching interviewers to ask behavioural questions, probe for specific examples, and avoid confirmatory bias — is a foundational investment that makes skills-based hiring work in practice, not just in theory.

Building a Skills Taxonomy for Your Organisation

A skills taxonomy is a structured, hierarchical catalogue of the skills that matter for performance across your organisation's roles. It is the infrastructure that makes skills-based hiring scalable: without a shared vocabulary for skills, every hiring manager defines competencies slightly differently, assessments are inconsistently designed, and the data collected across your hiring process cannot be aggregated or compared. Building a skills taxonomy is a meaningful upfront investment, but it pays dividends across recruiting, learning and development, internal mobility, and succession planning.

Start with your highest-volume and highest-impact role families. If you hire significant numbers of software engineers, customer success managers, and sales representatives, build your initial taxonomy around those three role families rather than attempting to cover your entire organisation from the outset. For each role family, identify three tiers of skills: foundational skills required at hire for entry-level roles, core skills that differentiate strong performers at the mid-level, and advanced skills associated with senior or lead positions. This tiered structure makes the taxonomy directly usable for designing job descriptions, structuring assessment stages, and defining progression criteria for performance reviews.

The taxonomy should distinguish between types of skills: technical skills (specific knowledge and tool proficiency), domain skills (industry or functional knowledge), and behavioural skills (the working styles, communication approaches, and problem-solving patterns that predict performance across contexts). Technical and domain skills are relatively straightforward to catalogue; behavioural skills require more careful definition to avoid vagueness. "Strong communication skills" is not a skill — it is a category. "Ability to translate technical concepts for non-technical stakeholders in written and verbal formats" is a skill that can be assessed and evidenced.

Maintaining the taxonomy requires ongoing discipline. Skills evolve as technology changes, as your products and markets develop, and as you learn more about what actually predicts performance in your organisation. Build a quarterly review cycle into your HR calendar to assess whether the skills in the taxonomy still reflect the realities of each role family, whether new skills have become relevant that are not yet captured, and whether any skills have become less important as processes or technologies have changed. ATS platforms that support custom skills tagging and searchable candidate profiles allow you to leverage the taxonomy not just in hiring but in talent pool management — identifying internal candidates who possess skills needed for open roles, or proactively sourcing from your database when hiring needs arise.

Free Calculators for This Topic

Save time with these free HR calculators — no sign-up required:

Related Reading Helpful Calculators

Frequently Asked Questions

What’s the difference between skills-based and competency-based hiring?

Skills-based hiring focuses on demonstrable abilities (e.g., Python programming), while competency-based hiring includes both skills and behavioral traits (e.g., leadership style). Both approaches are more inclusive than degree-first hiring.

Is removing degree requirements legal in the UK and US?

Yes—under the EEOC and Equality Act 2010, degree requirements are only permissible if they’re a genuine occupational qualification (GOQ) for the role. Most non-STEM roles don’t meet this threshold.

How do I convince hiring managers to shift to skills-based hiring?

Showcase data: 68% of employees hired through skills-based processes report higher job satisfaction (McKinsey, 2024). Share case studies from IBM and Google, and offer free trials of Treegarden’s skills assessment tools.

Can skills-based hiring improve retention?

Absolutely. Skills-aligned roles see 27% lower turnover than mismatched roles (Gartner, 2023). When employees feel their skills are utilized, they’re more engaged and less likely to leave.

Skills-based hiring isn’t just a trend—it’s a strategic shift that aligns with modern workforce needs and legal standards. By focusing on what candidates can do rather than where they studied, your organization can build a more diverse, capable, and inclusive team. Treegarden’s affordable, GDPR/EEOC-compliant platform makes it easier than ever to implement these strategies. Start your free demo today and transform your hiring process into a skills-first system.