The global skills and competency framework for the digital world

Software Engineering, SWEBOK and SFIA

Knowledge Areas in SWEBOK Version 4

SWEBOK V4.0 is the newest edition of the internationally acclaimed Software Engineering Body of Knowledge.  The SWEBOK Guide, published by the IEEE Computer Society, represents the current state of generally accepted knowledge and promotes a consistent view of software engineering worldwide 

Using SWEBOK and SFIA together

SFIA skill descriptions describe workplace  tasks, activities and responsibilities.

  • This forms the basis of the  mapping to SWEBOK KA’s and related disciplines. It is not a mapping of knowledge only.
  • The mapping is not 1:1 SFIA skill to KA.
  • The mapping is a loose coupling for informative purposes.
  • Content from SWEBOK is not copied into SFIA.

Summary and illustrative applications of these skills

SFIA version 9



SFIA 9 is the new version of the global skills and competency framework for the digital world - published in October 2024.
You can download this and other SFIA documents here

SWEBOK:SFIA Mapping

This Software Engineering competency model is based on the SWEBOK v4 and SFIA v9 (published October 2024). Presented here is a route map into SFIA software engineering skills and competencies via the Knowledge Areas of the SWEBOK.


Presentation from SWEBOK Global Summit - April 2025

Click image to download.


Summary chart - Interactive pdf 

A layout of the software engineering and software engineering skills which have been mapped to the SWEBOK v4.

Each skill name is hyperlinked to the corresponding full skill definition on the website making this a powerful navigation tool.

Summary and illustrative applications of these skills

More than technical skills

Levels of responsibility and generic attributes

Tools and technologies bring SFIA skills to life in practice, but the SFIA skills themselves are broader and more enduring

SFIA provides a stable, human-centred way to describe software engineering capability, independent of shifting technology trends.

  • Focuses on the underlying skill, knowledge, principles being applied, not the tool used to do it
  • Provides continuity as tools evolve—organisations don’t need to redefine roles or retrain entire teams each time the tech stack changes
  • Allows specialisation without fragmentation—a Java developer and a Rust developer can both operate at SFIA Level 3 for PROG, even if the tools differ
  • Supports learning and development by identifying transferrable skills that underpin tool usage (e.g. debugging, code optimization, version control)
  • Helps individuals describe what they do with tools and the value that their skills offer employers

Assigning skills and skill levels to software engineering job roles


Roles combine multiple SFIA skills

Typically 5 to 7 (sometimes fewer) at different levels rather than mapping a job role 1:1 to a skill

Flexibility by design

The same job title in different employers can contain different skill and level combinations

Skills vs. roles

SFIA defines capabilities (skills), not organizational positions (job titles)

Level indicates responsibility

SFIA levels reflect responsibility, accountability and impact, not years of experience or technical expertise

Context is key

Skills are practiced differently depending on industry and technical domain

Find out more about skills-based job analysis and job architectures.

Video - SFIA and skills management

  • This short video, produced by the SFIA Foundation, is designed mainly for new SFIA users.
  • The video and others is available on the SFIA Foundation YouTube channel

Video - SFIA for career paths

  • This video provides an illustration of using the SFIA Levels of Responsibility and professional skills with NICE Work Roles to support cybersecurity role and job levelling and the development of cybersecurity career paths.