What is a skills ontology?

Most organisations already have a skills list. A spreadsheet, a set of HR system fields, a taxonomy someone built three reorganisations ago. A list can tell you that Priya has “financial modelling” and a project needs “financial modelling”. What it cannot tell you is what to do when the words don’t match.

A skills ontology stores the relationships between skills, not just their names. “Financial modelling” sits near “valuation”, “forecasting” and “scenario analysis”. “Python” is a kind of “programming language” and is adjacent to “data analysis”. When a request asks for a skill nobody has by that exact name, the ontology lets ProFinda reason about who is close.

Why this matters for matching

Consider a request for someone with “ESG reporting” experience. On a flat list, you find only people who typed that exact phrase into their profile. In the ontology, ESG reporting connects to sustainability disclosure, non-financial reporting and the relevant regulatory frameworks. The search widens intelligently, and the people it surfaces are genuinely relevant rather than keyword accidents.

This is also why profile quality matters less than people fear. A consultant who lists “TCFD reporting” is still discoverable for ESG work, because the ontology knows the two are related. The structure absorbs the variation in how people describe themselves.

Who maintains it

The ontology is maintained centrally, by your platform team together with ProFinda. Individual users do not edit it. That is a feature: everyone in the organisation matches against the same structure, so two resourcing leads searching for the same capability get the same candidates.