What skills-based hiring actually means
Skills-based hiring is the practice of evaluating candidates on demonstrated abilities and competencies — rather than using a university degree as a proxy for competence. Instead of filtering CVs based on where someone studied or whether they hold a specific qualification, skills-first organisations define what the role actually requires and assess candidates directly against those criteria.
The shift sounds straightforward but requires a deliberate rethink of how job descriptions are written, how candidates are screened, and how hiring decisions are justified. It is not about lowering standards — it is about measuring the right things.
The scale of adoption is significant. According to a 2023 analysis by the Harvard Business School and Burning Glass Institute, approximately 65% of job postings that previously required a bachelor's degree had removed or softened that requirement over a five-year period. The trend accelerated markedly after 2020 as organisations faced talent shortages and recognised that degree requirements were eliminating viable candidates from the pipeline.
The Degree as a Proxy Problem
Degrees were never designed as hiring filters. They signal that someone completed a structured learning programme — not that they can perform a specific job. When a degree becomes a gatekeeping requirement rather than a relevant qualification, it functions as a socioeconomic filter that systematically excludes capable candidates from underrepresented groups, non-traditional career paths and self-taught disciplines.
Why major employers are leading the transition
The organisations abandoning degree requirements are not doing so out of goodwill alone. There is a clear business logic. Google removed degree requirements for most software roles, citing internal data showing that academic credentials were poor predictors of on-the-job performance. IBM eliminated requirements for roughly half its US job openings and reported accessing a substantially larger and more diverse candidate pool. Apple, Tesla, Accenture, Bank of America and many others have followed similar paths.
The business case rests on three observable effects:
Pool expansion. In the United States, only about 38% of adults hold a bachelor's degree. In the United Kingdom, the figure is around 43%. Removing a degree requirement immediately makes the remaining 57-62% of the population eligible to apply — a dramatic increase in addressable talent. For roles in technology, data analysis, project management, sales and many operational functions, this expanded pool contains extraordinary talent that credential-first screening would have eliminated before a human ever reviewed the application.
Diversity improvement. Educational attainment is strongly correlated with socioeconomic background, race and geography. Degree requirements embed these correlations into hiring pipelines, producing candidate shortlists that systematically skew towards particular demographic groups — not because those groups are more capable, but because they had better access to higher education. Skills-based approaches evaluate what candidates can actually do, breaking this inherited correlation.
Retention improvement. Research from the Burning Glass Institute found that workers hired without degree requirements into roles that previously mandated them showed comparable or better performance and stayed longer than credentialled counterparts. One hypothesis is that skills-based hires have often pursued their competencies with deliberate intent rather than credential accumulation, resulting in stronger intrinsic motivation and domain commitment.
Skills-First Hiring at Scale
Treegarden's AI Match Score evaluates candidates against the specific skills and competencies you define in the job description — not credentials. By weighting demonstrated experience and skills over degree signals, the score surfaces candidates who may have been invisible in a traditional screening process. Each candidate receives a match percentage tied to role requirements, giving recruiters a structured, defensible basis for shortlisting decisions.
What to replace degree requirements with
The question most HR teams face is practical: if not a degree, what do we screen for? The answer requires articulating what the role actually demands — a discipline that produces better job descriptions regardless of whether degree requirements exist.
Demonstrated experience. For most professional roles, what candidates have done is more predictive than where they studied. Defining specific experience requirements — "has built and maintained a CRM integration", "has managed a team of four or more through a product launch" — captures genuine capability rather than credential proximity to it.
Portfolio and work samples. For creative, technical and analytical roles, asking candidates to submit relevant work samples, case studies or portfolio items directly demonstrates the capability in question. A self-taught developer who has shipped five production applications is a stronger candidate than a computer science graduate with no deployed code.
Skills assessments. Standardised, role-relevant assessments — coding challenges, writing tests, analytical exercises — evaluate whether a candidate can actually perform the core functions of the role. When validated and administered consistently, these assessments have substantially higher predictive validity than degree screening.
Structured competency interviews. Behavioural and situational interview questions tied to specific competencies produce reliable, comparable data across candidates. A structured interview asking all candidates the same problem-solving and communication questions yields more predictive hiring decisions than an unstructured conversation that varies by candidate.
Rewriting Job Descriptions for Skills-First
The most immediate practical step is rewriting job descriptions. Replace "Bachelor's degree in a relevant field" with the specific knowledge, skills and experience the role genuinely requires. If communication skills matter, say what kind and in what context. If analytical thinking is essential, describe the problems the person will solve. This specificity attracts better-matched candidates and discourages candidates who would not succeed — without the blunt instrument of a degree filter.
Building a skills taxonomy for your organisation
Effective skills-based hiring requires more than removing a line from job postings. It requires knowing — with some precision — which skills matter for which roles and how to assess them consistently. This is where most organisations need to invest structured thinking.
A skills taxonomy organises the competencies your organisation cares about into a coherent framework. It distinguishes between technical skills (programming languages, data analysis, financial modelling), transferable skills (project management, communication, analytical reasoning) and behavioural competencies (adaptability, initiative, collaboration style). For each role family, the taxonomy specifies which skills are required, which are preferred, and which can be developed on the job.
This taxonomy then drives everything downstream: how job descriptions are written, what screening questions are asked, how interviews are structured, and how hiring decisions are evaluated and documented. Without this foundation, skills-based hiring becomes an informal judgement call rather than a rigorous system — and informal judgement calls reintroduce the biases that skills-based approaches are meant to eliminate.
Customisable Screening Questions in Treegarden
Treegarden's application forms support custom screening questions that can be configured per role. For skills-based hiring, this means asking candidates directly about specific competencies — "describe a project where you managed conflicting stakeholder priorities", "show us a data analysis you completed independently" — rather than relying on degree fields as proxies. Candidate responses are stored alongside CVs and AI scores for structured comparison.
How skills-based hiring reduces bias in practice
One of the strongest arguments for skills-first recruitment is its effect on hiring equity. Unconscious bias in traditional hiring operates through multiple channels: name-based discrimination, institutional prestige effects (preferring graduates from certain universities), and the tendency to favour candidates whose backgrounds resemble existing team members. Skills-based frameworks interrupt several of these channels simultaneously.
When evaluation is anchored to defined competencies assessed through standardised instruments, the space for subjective bias narrows significantly. A coding assessment does not know the candidate's name or university. A structured interview with behavioural anchors and standardised scoring requires evaluators to justify each score against observable evidence rather than "gut feel."
This does not eliminate bias entirely — skills assessments can themselves carry cultural bias if poorly designed, and structured interviews still involve human evaluators who carry their own assumptions. But the bias surface is substantially smaller than in credential-and-impression-based hiring, and the trail of documented evidence makes it possible to audit decisions for consistency and fairness.
GDPR and EU equal treatment directives add a compliance dimension for European employers. When a hiring decision is challenged, having documented skills assessment scores and structured interview ratings provides a defensible basis for the decision. A note in a hiring manager's notebook that says "good vibe" does not.
What your ATS needs to support skills-based hiring
A traditional ATS optimised for credential screening will actively undermine skills-based hiring if you try to run the new approach through the same workflows. The tools must match the method.
Several ATS capabilities are essential for skills-first recruiting to function at scale. First, flexible job description templates that prompt for competency-based requirements rather than defaulting to credential fields. Second, custom application forms that can capture work samples, portfolio links and competency-specific responses. Third, a matching algorithm that weights skills and demonstrated experience rather than treating degree attainment as a positive signal. Fourth, structured interview frameworks that are linked to the competencies defined in the job description. Fifth, centralised candidate evaluation records that document how each hiring decision was reached.
Kanban Pipeline Tied to Competency Stages
Treegarden's Kanban recruitment pipeline can be configured with custom stages that reflect skills-based hiring workflows — for example, adding a "Skills Assessment" stage between application and first interview. Each candidate card carries their AI Match Score, custom screening responses and recruiter notes, giving the whole team visibility into where each candidate stands against defined competency criteria.
A practical roadmap for the transition
Switching from credential-first to skills-first hiring does not happen overnight, but organisations that take a phased approach see meaningful results within two or three hiring cycles.
Phase 1: Audit current job descriptions. Review all open and frequently recurring roles. Identify degree requirements that are not legally or technically mandated. For each, ask: what capability does this requirement proxy? Then define that capability directly and remove the degree filter.
Phase 2: Build assessment infrastructure. For roles where skills can be assessed directly, develop or source appropriate instruments — technical assessments, work sample exercises, structured interview guides tied to defined competencies. Pilot these on a small number of roles before rolling out broadly.
Phase 3: Train hiring managers. Skills-based hiring requires hiring managers to shift their evaluation frame. Instead of asking "where did they study?", they ask "what have they built, solved or delivered?" This shift requires deliberate training and clear guidance on what evidence is and is not relevant to hiring decisions.
Phase 4: Measure outcomes. Track the diversity of your shortlists, the source distribution of hires, 90-day and 12-month performance ratings, and regrettable attrition. Skills-based hiring should produce measurable improvements on all of these metrics over time. If it does not, the assessment instruments or evaluation criteria need refinement.
What Skills-Based Hiring Does Not Mean
Skills-first recruitment is not credential-blind. For roles where a specific qualification is genuinely required — licensed professions, regulated industries, technical specialisations where a degree indicates essential foundational knowledge — maintaining that requirement is appropriate and defensible. The question is always whether the requirement is genuinely predictive of job performance or functioning as an arbitrary filter. Most roles land clearly in one category or the other when examined honestly.
Frequently asked questions about skills-based hiring
What is skills-based hiring?
Skills-based hiring is a recruitment approach that evaluates candidates based on demonstrated abilities and competencies rather than educational credentials or years of experience. It focuses on what candidates can do rather than what qualifications they hold on paper.
Which companies have dropped degree requirements?
Google, Apple, IBM, Tesla, Bank of America, Accenture, Dell and many mid-sized employers have removed degree requirements for the majority of their roles. They now evaluate candidates on demonstrated skills, portfolio work and assessed competencies rather than academic credentials.
How does an ATS support skills-based hiring?
A modern ATS like Treegarden supports skills-based hiring by enabling custom screening questions focused on competencies, structured interview frameworks organised around specific skills, and AI match scores that weight demonstrated abilities rather than credential proxies.
Does removing degree requirements lower hiring quality?
Evidence consistently shows the opposite. When organisations replace degree screening with skills assessments, they find a larger pool of qualified candidates, lower regrettable turnover, and stronger on-the-job performance compared to credential-first approaches.