The Hiring Funnel Is the Real Policy

This chapter follows skills-first hiring through the decisions that sit between a public job posting and an actual offer. The focus is practical: how an employer chooses a role, defines the capabilities needed for it, screens candidates and collects evidence that a manager can use. Tracing that sequence shows why a changed posting can affect hiring only when the organisation also changes the machinery that turns applications into a decision.

Start with the role, not the slogan

A firm does not need to redesign every job at once to begin. The OECD describes targeted pilots as a sensible way to experiment while building shared understanding and commitment. But “start small” is not the same as “choose arbitrarily.” The role selected for a pilot determines whether the organisation is testing a meaningful alternative to a degree filter or merely changing language where the old qualification was already irrelevant.

One useful starting point is a role with a real hiring problem: a shortage occupation, an entry-level position, or a job whose requirements are changing faster than formal curricula can adapt. Another is a role with a large gap between the degree prevalence in its postings and the educational attainment of people already doing the work. That gap suggests the credential may be an employer preference rather than a necessity. It does not prove that every candidate without a degree is ready, but it gives the employer a reason to ask whether the existing filter is excluding people who could succeed.

The boundary is especially important in regulated work. Health, education, law and other specialised fields may require qualifications or licences for legal and safety reasons. Removing such a requirement would not be a brave act of skills-first hiring; it could be a failure to respect the conditions of competent practice. A skills-first approach can still improve these roles by describing the skills underneath the qualification, making progression clearer and supporting recognition across jurisdictions. But a skills profile cannot override a statutory rule.

The role itself must then be taken apart. A job description often mixes several different things: tasks the employee performs, knowledge they need, behaviours the organisation prefers, credentials used as a shortcut and experience that may or may not transfer. A skills-first redesign asks which capabilities enable competent performance and which forms of evidence can show them. “Prepare monthly management accounts” describes a task in one workflow; financial reporting is a more portable capability that may also matter in another role. The goal is not to replace every sentence with a skill label. It is to make the relationship between the work and the capability explicit.

That translation requires choices about priority and proficiency. Some skills are essential; others are useful but teachable after hiring. A profile can distinguish basic, intermediate and advanced performance, provided those levels are tied to observable behaviour rather than to impressive-sounding adjectives. For an operations analyst, for example, a firm might need the ability to analyse complex data, communicate with stakeholders, organise work and use spreadsheet tools. It might regard prior insurance experience or a particular project history as desirable rather than essential.