Traditionally the architect role has evolved into certain activities at different levels within an organisation.
You will see some architects working closely with the exec team and never with developers, others work close to the coal face and organisations like to keep this distinction by differing titles.
The Public Sector is made up of hundreds (if not thousands) of organisations all moving at a differing pace and many levels of size and digital maturity.
GDS have a definition of architecture roles here, of which this role definition is the most relevent and overlaps more clearly with Made Tech skills and behaviours.
However, alignment with DDaT professions is not a given and on the ground when working with Central, Local or Arms Lengths Bodies wthin the Public Sector and you are likely to see other roles in the wild.
Can also be described as: Application Architect or Software Architect or Product Architect
Can also be described as: Infrastructure Architect
Integration architect, Solution Architect, Security Architect, Data Architect, Transformation Architect
We are seeing the emergence of a modern architect within leaner, more agile ‘Digital Enterprises’ where role and activities are less siloed.
Modern architects align organization and technology, reduce friction, and chart transformation journeys. In addition to working with UML and architecture styles, such architects ride the Architect Elevator from the penthouse, where the business strategy is set, to the engine room, where the enabling technologies are implemented. They shun popular buzzwords in favor of a clear strategy defined by conscious decision making.
Gregor Hohpe, https://architectelevator.com/
We also consider how all Developers as play a part in the architecture role and how the modern architect facilitates this.
Next - The Modern Architect