\cleardoublepage \part{Competence and Career} \setbookpart{Competence and Career}

Part V: Competence and Career

If the role is transformed, so are the competences it requires and the paths into it. This part describes what the transformed security architect must be able to do, how that is evidenced, how people reach the role from different starting points, and whether the role will exist in ten years.

The part treats competence the way the rest of the book treats architecture: as a framework in code, mapped to ENISA's European Cybersecurity Skills Framework, SFIA and the NIST NICE Framework, with evidence rather than certificates as the measure and the lower of the unassisted and assisted levels counting. It answers how competence is evidenced when AI does much of the visible work (Q7) and, in part, how anyone becomes a security architect when junior work is automated (Q8). It closes with the future of the role (Q12), where every outlook is labelled observable, expected or speculation, and the author's own projections are kept apart and labelled.

Chapters in this part:

• Chapter 21, Competences of the Transformed Security Architect, defines a competence framework as code with domains, levels and evidence.
• Chapter 22, Learning Paths, Certification, Hiring and Upskilling, sets out paths by starting point, the limits of certification and hiring exercises.
• Chapter 23, The Future of the Role, keeps a horizon register for the role and weighs scenarios for 2036.

What you will learn in this part:

• Which competences define the transformed role, and how to evidence them in a competence record
• How a security engineer, an enterprise architect, a developer or an auditor can become a security architect
• How to hire for judgement and verification rather than for certificates alone
• Which futures for the role are observable, which are expected and which are speculation

The part draws on all four shifts, and on Shift 4 in particular.