SFIA Skills: What They Are and How the Levels Actually Work
The most common mistake I see when people describe the SFIA framework is calling its seven-level structure a set of proficiency levels. It is not. Calling them proficiency levels misrepresents what SFIA actually measures, leads to misuse in practice, and creates confusion when organisations try to apply the framework to real workforce decisions. The levels in SFIA are levels of responsibility. That distinction matters more than it might seem.
What Are SFIA Skills
SFIA skills are the professional competencies defined by the SFIA framework to describe the work performed by people in digital, data, and technology roles. Each skill is defined with a unique name, a four-letter code, a short description, and level descriptions that specify what the skill looks like when performed at relevant levels of responsibility.
The current version, SFIA 9, defines more than 120 professional skills. These cover the full range of work performed in digital and technology environments, from software development and data engineering through to security, governance, and business change. No single role uses all 120 skills. In practice, a role profile is built by selecting the small number of skills, typically three to eight, that best describe the actual work of that role.
SFIA skills are organised into six categories and a series of subcategories. These categories are a navigation aid rather than rigid boundaries. A single role can draw skills from multiple categories. The six categories are:
- Strategy and architecture
- Change and transformation
- Development and implementation
- Delivery and operation
- Skills and quality
- Relationships and engagement
As the SFIA Foundation notes, these categories do not equate to teams, departments, or areas of personal job responsibility. They exist to help practitioners locate skills when building role profiles or capability framework designs.
Why SFIA Defines Skills This Way
The reason SFIA describes skills as it does is that technical role requirements in digital environments are genuinely different from one level of work to the next. A data engineer working on routine pipeline maintenance is doing something categorically different from someone setting the organisation's data architecture strategy, even if they nominally share the same skill.
A common language for those differences, consistent across sectors and roles, is what makes SFIA useful. Without it, organisations end up with role profiles that are either too vague to support hiring decisions or so context-specific that no two roles can be compared across functions or entities.
Research on SFIA as a communication bridge between higher education, employers, and ICT professionals identifies the shared language function as one of the primary reasons SFIA was developed and has sustained adoption across diverse sectors over more than two decades.
How SFIA Skill Levels Actually Work
Each SFIA skill is described at the levels of responsibility at which it is realistically performed. Not all skills are defined at all seven levels. A skill like Digital Forensics might be described at Levels 3 to 6. A strategic skill like IT governance might only appear at Levels 5 to 7. This reflects actual workplace practice, not a design limitation.
The seven levels in SFIA are:
- Follow: working under close direction on routine tasks with limited discretion
- Assist: working under supervision with some latitude for judgement
- Apply: working under general direction on a range of tasks with some complexity
- Enable: working with broad direction, taking responsibility for specific outcomes
- Ensure and advise: accountable for strategic decisions, providing authoritative guidance
- Initiate and influence: shaping organisational direction, driving change at scale
- Set strategy, inspire, mobilise: operating at the highest level of strategic leadership
Each level is characterised by five generic attributes that apply consistently across all skills: autonomy, influence, complexity, knowledge, and business skills and behavioural factors. As the SFIA Foundation's description of levels of responsibility makes clear, these attributes describe the nature of the work environment and the scope of accountability.
Why SFIA Levels Are Not Proficiency Levels
This is where the most consequential misunderstanding occurs. Proficiency levels, as typically used in skills frameworks, describe how expert someone is at a specific capability, from novice through to advanced or expert. SFIA's seven levels do not do that.
A Level 3 description of a SFIA skill tells you what that skill looks like when performed by someone operating at Level 3 responsibility: someone working under general direction, handling activities of moderate complexity, with some autonomy but without strategic accountability. It does not tell you that the person is "intermediate" at the skill, or that their next development step is to become more advanced at the same task.
A person progressing from Level 3 to Level 4 in a skill is not becoming more expert at the same work. They are taking on a fundamentally different scope of responsibility. The work changes: its complexity, its accountability, and the degree of independent judgement it requires. The skill description at Level 4 reflects that change, not an improvement on Level 3.
This is also why academic examination of SFIA in practice consistently treats the levels as organisational context descriptors, not individual mastery ratings. Organisations that misapply SFIA as a proficiency measurement system end up assessing people against criteria designed for a different level of accountability than the one they are actually working in.
What SFIA Skills Are Not
SFIA skills are not job titles. The skill Cloud computing does not describe a Cloud Engineer. A Cloud Engineer role would be built by combining Cloud computing with several related skills, each at the levels relevant to that role's actual scope of responsibility.
SFIA skills are not a learning programme or curriculum. They describe the professional application of a capability in a real-world work context. The SFIA Foundation is explicit that competency at a given level is attained through practice at that level in a real workplace, not through studying a body of knowledge. This is different from a digital literacy skills framework, which is typically designed to describe learning progressions for general digital competence across a population rather than professional performance in specific technical roles.
SFIA skills are not a competency framework. A competency framework describes expected behaviours and performance standards across a workforce. SFIA describes the professional skills required in specific digital and technology roles. The two are complementary and often used together, but they describe different things.
SFIA skills are not a performance rating scale. You cannot assess someone as "Level 4" overall in the way you might give a performance rating. SFIA works at the level of individual skills, with each skill assessed at the level of responsibility at which it is being performed.
How Organisations Use SFIA Skills in Practice
In practice, SFIA skills are used to build role profiles for digital and technology roles, describe workforce requirements for planning purposes, design career pathways, and create recruitment criteria grounded in specific capability requirements at defined levels of responsibility.
The SFIA professional skills documentation describes how each skill is constructed for adaptability. Organisations working across multiple sectors, or with diverse role families, can use SFIA skills selectively. No organisation is expected to use all 120 skills, and the framework is designed for adaptation, not wholesale adoption.
The VPS Capability Framework uses SFIA as a reference point for digital and data roles within the Victorian Public Service, drawing on SFIA skill definitions and level structures to build role-specific profiles. This illustrates how SFIA skills can be adapted within a broader capability architecture without losing their structural integrity.
The structure of a SFIA skill, with its name, code, description, guidance notes, and level descriptions, gives organisations a ready-made vocabulary for role design. A role profile might specify four SFIA skills, each at defined levels, alongside the generic attributes at the equivalent level. That combination tells you what the role does, at what scope, and with what accountability, in a form that can be compared across roles, teams, and organisations.
Common Failure Modes
The most damaging misuse of SFIA is assessing existing staff against all skills at all levels to produce a comprehensive skills map. This produces data that looks rigorous but is difficult to interpret, because SFIA's level descriptions are designed to describe job context, not individual assessment outcomes divorced from the job being performed.
A related error is applying SFIA skills to roles outside digital and technology. SFIA is explicitly designed for professionals who design, develop, implement, manage, and protect data and technology. Organisations that extend SFIA into HR, finance, or operational leadership roles often find the skill language does not match the work and the level structure does not align with how those roles are graded.
A third failure is selecting too many skills for a role. A role profile with twelve or fifteen SFIA skills is not a comprehensive description of the role; it is a list of activities that has not been properly analysed to identify what the role is actually accountable for. Most SFIA role profiles should specify three to eight core skills.
Frequently Asked Questions
What are SFIA skills?
SFIA skills are the professional competencies defined by the Skills Framework for the Information Age. SFIA 9 defines more than 120 skills covering digital, data, and technology work, each described at the levels of responsibility at which they are realistically performed.
What are the seven levels in SFIA?
The seven levels are levels of responsibility: Follow, Assist, Apply, Enable, Ensure and advise, Initiate and influence, and Set strategy, inspire, mobilise. They describe the scope of autonomy, influence, and complexity in which a skill is performed, not the proficiency of an individual at a specific skill.
Are SFIA levels the same as proficiency levels?
No. SFIA levels describe the level of responsibility and the work context in which a skill is performed. They are not proficiency ratings measuring how expert someone is at a specific skill. Progressing from Level 3 to Level 4 means taking on a different scope of accountability, not becoming more skilled at the same task.
Why are not all SFIA skills defined at all seven levels?
Because not all skills are meaningfully performed at every level of responsibility. Some skills only exist in senior leadership contexts. Others are only relevant at operational levels. The level coverage for each skill reflects real-world professional practice.
How many SFIA skills should a role profile include?
Most role profiles should specify three to eight SFIA skills. A role profile with significantly more than this is typically too broad and has not been properly analysed to identify the skills most central to the role's accountabilities.
How do SFIA skills differ from a competency framework?
SFIA skills describe the professional capabilities required in specific roles, particularly in digital and technology environments. A competency framework describes expected behaviours and performance standards across a workforce. SFIA operates at the level of role design. A competency framework operates at the level of behavioural expectations. Both are often used together within the same workforce system.