Skip to main content

Complete our 3 minute feedback survey to help us improve the framework.

Solution architect

Find out what a solution architect in government does and the skills you need to do the role at each level.

Last updated 30 November 2024 — See all updates

What a solution architect does

A solution architect designs solutions for problems that affect the organisation.

In this role, you will:

  • ensure a problem and the desired outcomes are properly defined
  • ensure the scope of a solution meets the organisation's requirements
  • stay up to date on technology trends and approaches
  • understand organisational objectives and external drivers, for example, legislation or financial constraints
  • work with others to develop business and technical strategies
  • work within business and technical constraints
  • design and document solutions so they can be implemented by the organisation
  • comply with standards and governance
  • communicate and work effectively with stakeholders
  • manage risks and decisions in a transparent way

Solution architect role levels

There are 5 solution architect role levels, from associate solution architect to principal solution architect.

The typical responsibilities and skills for each role level are described in the sections below. You can use this to identify the skills you need to progress in your career, or simply to learn more about each role in the Government Digital and Data profession.

1. Associate solution architect

An associate solution architect supports other solution architects to design solutions. You will usually work under supervision.

At this role level, you will:

  • support the design of solutions by working with stakeholders
  • help your team achieve its objectives

Skill Description

Architect for the whole context

Level: awareness

Awareness is the first of 4 ascending skill levels

You can:

  • identify relevant information that can inform your architectural work, such as strategies, roadmaps, policies and technical trends
  • understand how your work supports the team in enabling change​

Architecture communication

Level: working

Working is the second of 4 ascending skill levels

You can:

  • listen to the needs of technical and business stakeholders
  • create and use different architecture representations to communicate effectively, achieving agreement with technical and non-technical stakeholders
  • provide support in discussions about architectural topics within a multidisciplinary team

Commercial perspective

Level: awareness

Awareness is the first of 4 ascending skill levels

You can:

  • show an awareness of government commercial processes
  • show an awareness of legal and compliance rules

Community collaboration

Level: awareness

Awareness is the first of 4 ascending skill levels

You can:

  • understand the work of others and the importance of team dynamics, collaboration and feedback

Making architectural decisions

Level: awareness

Awareness is the first of 4 ascending skill levels

You can:

  • describe the reasoning behind architectural design decisions
  • gather information to inform decisions
  • understand architectural governance and assurance relevant to your work

Problem definition and shaping

Level: working

Working is the second of 4 ascending skill levels

You can:

  • help to frame a problem characterised by managed levels of complexity, complication, or risk so that a solution can be created
  • help to create options for solving problems at an appropriate level of detail

Strategy design

Level: awareness

Awareness is the first of 4 ascending skill levels

You can:

  • explain how organisational objectives link to designing strategy
  • describe the purpose and application of strategy, standards, patterns, policies, roadmaps, vision, and mission statements

Technical design throughout the life cycle

Level: working

Working is the second of 4 ascending skill levels

You can:

  • create technical designs characterised by managed levels of risk, impact, and complexity
  • provide guidance and support to teams using technical designs throughout the life cycle
  • adapt a technical design if needed during delivery
  • work with well-understood technology and identify appropriate patterns

2. Solution architect

A solution architect is responsible for a single solution. They usually work independently on solutions where risk is low. They also often support or contribute to work led by more senior solution architects.

At this role level, you will:

  • build relationships with stakeholders across different business or technical areas in the organisation
  • be proactive in identifying opportunities to improve the organisation
  • follow best practice for solution design
  • use emerging technologies and approaches
  • help your team achieve its objective

Skill Description

Architect for the whole context

Level: working

Working is the second of 4 ascending skill levels

You can:

  • align your work with the work being done by other architects and technical professionals
  • track emerging issues, strategies, roadmaps, patterns and technologies over time to assess opportunities and risks to your work
  • identify how other teams contribute to delivering outcomes through change

Architecture communication

Level: practitioner

Practitioner is the third of 4 ascending skill levels

You can:

  • lead the communication of complicated, complex or risky architecture topics with technical and non-technical stakeholders
  • communicate with senior stakeholders across your organisation
  • adapt your message and communication techniques to your audience
  • advocate on behalf of a team to other stakeholders
  • manage stakeholder expectations effectively

Commercial perspective

Level: working

Working is the second of 4 ascending skill levels

You can:

  • understand commercial processes and the appropriate internal contacts within a government department
  • understand different sourcing strategies and when to apply them

Community collaboration

Level: working

Working is the second of 4 ascending skill levels

You can:

  • contribute to the work of others
  • motivate and empower teams
  • create the right environment for teams to work in, and can identify the best team makeup depending on the situation
  • recognise and deal with issues

Making architectural decisions

Level: working

Working is the second of 4 ascending skill levels

You can:

  • work with others to make architectural design decisions characterised by managed levels of risk and complexity
  • identify and address architectural risks relevant to your team or domain, for example, business, data, or security
  • engage with architectural governance and assurance to effectively manage decisions and risks, with support

Problem definition and shaping

Level: practitioner

Practitioner is the third of 4 ascending skill levels

You can:

  • frame a problem characterised by medium complexity, complication, or risk so that a solution can be created
  • produce architectural representations that enable different teams to have a shared understanding of problems throughout the life cycle
  • describe options for solving problems so that appropriate delivery methods can be decided

Strategy design

Level: working

Working is the second of 4 ascending skill levels

You can:

  • support the development of a strategy or vision that aligns with organisational objectives
  • challenge requirements and assumptions, and identify opportunities to develop strategy
  • support the implementation of a strategy or vision, for example, by using a roadmap or plan
  • use architectural principles, patterns, and constraints when appropriate

Technical design throughout the life cycle

Level: working

Working is the second of 4 ascending skill levels

You can:

  • create technical designs characterised by managed levels of risk, impact, and complexity
  • provide guidance and support to teams using technical designs throughout the life cycle
  • adapt a technical design if needed during delivery
  • work with well-understood technology and identify appropriate patterns

3. Senior solution architect

A senior solution architect is responsible for a single, more complex, solution. They usually work on solutions where the risk is moderate. They may lead and coach other solution architects.

At this role level, you will:

  • build relationships with senior stakeholders across different business or technical areas in the organisation
  • be proactive in identifying opportunities to improve the organisation
  • support multiple architecture projects
  • find and use emerging technologies and approaches
  • support others to follow best practice for solution architecture

Skill Description

Architect for the whole context

Level: working

Working is the second of 4 ascending skill levels

You can:

  • align your work with the work being done by other architects and technical professionals
  • track emerging issues, strategies, roadmaps, patterns and technologies over time to assess opportunities and risks to your work
  • identify how other teams contribute to delivering outcomes through change

Architecture communication

Level: practitioner

Practitioner is the third of 4 ascending skill levels

You can:

  • lead the communication of complicated, complex or risky architecture topics with technical and non-technical stakeholders
  • communicate with senior stakeholders across your organisation
  • adapt your message and communication techniques to your audience
  • advocate on behalf of a team to other stakeholders
  • manage stakeholder expectations effectively

Commercial perspective

Level: working

Working is the second of 4 ascending skill levels

You can:

  • understand commercial processes and the appropriate internal contacts within a government department
  • understand different sourcing strategies and when to apply them

Community collaboration

Level: practitioner

Practitioner is the third of 4 ascending skill levels

You can:

  • work collaboratively in a group, actively networking with others
  • adapt feedback to ensure it’s effective and lasting
  • use your initiative to identify problems or issues in the team dynamic and rectify them
  • identify issues through Agile ‘health checks’ with the team, and help to stimulate the right responses

Making architectural decisions

Level: practitioner

Practitioner is the third of 4 ascending skill levels

You can:

  • make and guide architectural design decisions characterised by medium risk and complexity
  • identify and address architectural risks that affect multiple teams or domains
  • use architectural governance and assurance to make design decisions and manage technical risks at the appropriate level
  • contribute to the development of architectural governance and assurance

Problem definition and shaping

Level: practitioner

Practitioner is the third of 4 ascending skill levels

You can:

  • frame a problem characterised by medium complexity, complication, or risk so that a solution can be created
  • produce architectural representations that enable different teams to have a shared understanding of problems throughout the life cycle
  • describe options for solving problems so that appropriate delivery methods can be decided

Strategy design

Level: working

Working is the second of 4 ascending skill levels

You can:

  • support the development of a strategy or vision that aligns with organisational objectives
  • challenge requirements and assumptions, and identify opportunities to develop strategy
  • support the implementation of a strategy or vision, for example, by using a roadmap or plan
  • use architectural principles, patterns, and constraints when appropriate

Technical design throughout the life cycle

Level: practitioner

Practitioner is the third of 4 ascending skill levels

You can:

  • create technical designs characterised by medium risk, impact, and complexity
  • maintain appropriate quality and architectural coherence of a technical design in response to change
  • use feedback to optimise and refine technical designs throughout the life cycle

4. Lead solution architect

A lead solution architect is responsible for a group of solution architecture projects, or a single more complex area. They may lead teams of more junior solution architects.

At this role level, you will:

  • build relationships with senior stakeholders across multiple business or technical areas in the organisation
  • be proactive in identifying opportunities to improve the organisation
  • support multiple architecture projects or programmes
  • find and use emerging technologies and approaches
  • develop best practice for solution architecture

Skill Description

Architect for the whole context

Level: practitioner

Practitioner is the third of 4 ascending skill levels

You can:

  • work to support wider organisational objectives beyond your immediate goals​
  • track emerging internal and external issues over time that could affect the work of teams across the organisation
  • take action to solve or mitigate problems by influencing colleagues across the organisation

Architecture communication

Level: expert

Expert is the fourth of 4 ascending skill levels

You can:

  • communicate with technical and non-technical stakeholders at all levels, and across organisations, using architecture communication techniques​
  • mediate between people in difficult architectural discussions
  • gain support from business and technical stakeholders for architectural initiatives with high levels of risk, impact and complexity
  • coach and support others in architecture communication

Commercial perspective

Level: practitioner

Practitioner is the third of 4 ascending skill levels

You can:

  • identify appropriate contractual frameworks and approaches
  • identify, evaluate and select appropriate suppliers

Community collaboration

Level: practitioner

Practitioner is the third of 4 ascending skill levels

You can:

  • work collaboratively in a group, actively networking with others
  • adapt feedback to ensure it’s effective and lasting
  • use your initiative to identify problems or issues in the team dynamic and rectify them
  • identify issues through Agile ‘health checks’ with the team, and help to stimulate the right responses

Making architectural decisions

Level: practitioner

Practitioner is the third of 4 ascending skill levels

You can:

  • make and guide architectural design decisions characterised by medium risk and complexity
  • identify and address architectural risks that affect multiple teams or domains
  • use architectural governance and assurance to make design decisions and manage technical risks at the appropriate level
  • contribute to the development of architectural governance and assurance

Problem definition and shaping

Level: expert

Expert is the fourth of 4 ascending skill levels

You can:

  • lead the framing of a problem characterised by high complexity, complication, or risk so that a solution can be created
  • coach others in defining problems and describing appropriate options for solutions
  • help others challenge requirements and assumptions, and identify opportunities when defining problems and solution options

Strategy design

Level: practitioner

Practitioner is the third of 4 ascending skill levels

You can:

  • define strategies or visions across teams that align with organisational objectives
  • direct the implementation of a strategy or vision, for example, by creating roadmaps or plans
  • define architectural principles and patterns
  • develop or maintain strategy in response to feedback and findings

Technical design throughout the life cycle

Level: expert

Expert is the fourth of 4 ascending skill levels

You can:

  • create technical designs characterised by high risk, impact, and complexity
  • lead and guide others in creating technical designs that achieve organisational objectives
  • use feedback to optimise and refine standards for technical designs throughout the life cycle

5. Principal solution architect

A principal solution architect can be responsible for a large programme or group of solution architecture projects, or a single, very complex or critical business area.

At this role level, you will:

  • lead teams of more junior solution architects
  • lead multiple architecture projects or programmes
  • build relationships with senior stakeholders across multiple business or technical areas in the organisation and its partners
  • be proactive in identifying opportunities to improve the organisation and its partners
  • work with technology partners to inform their roadmaps
  • take a leading role in the overall direction of business and digital capabilities
  • inspire other architects and help them understand how to meet organisational goals

Skill Description

Architect for the whole context

Level: expert

Expert is the fourth of 4 ascending skill levels

You can:

  • assess how trends in society and industry practices might impact the organisation
  • work with people outside of your organisation to inform policies, strategies and standards
  • anticipate changes to policy and build resilience through your architectural work
  • coach others in identifying important trends

Architecture communication

Level: expert

Expert is the fourth of 4 ascending skill levels

You can:

  • communicate with technical and non-technical stakeholders at all levels, and across organisations, using architecture communication techniques​
  • mediate between people in difficult architectural discussions
  • gain support from business and technical stakeholders for architectural initiatives with high levels of risk, impact and complexity
  • coach and support others in architecture communication

Commercial perspective

Level: practitioner

Practitioner is the third of 4 ascending skill levels

You can:

  • identify appropriate contractual frameworks and approaches
  • identify, evaluate and select appropriate suppliers

Community collaboration

Level: expert

Expert is the fourth of 4 ascending skill levels

You can:

  • solve and unblock issues between teams or departments at the highest level
  • coach the organisation on team dynamics and conflict resolution, while also building and growing the community

Making architectural decisions

Level: expert

Expert is the fourth of 4 ascending skill levels

You can:

  • make and guide architectural design decisions characterised by high levels of risk and complexity
  • identify and address architectural risks across the organisation or wider government
  • lead and evolve architectural governance and assurance
  • represent architectural governance as part of wider governance, for example, legal or commercial

Problem definition and shaping

Level: expert

Expert is the fourth of 4 ascending skill levels

You can:

  • lead the framing of a problem characterised by high complexity, complication, or risk so that a solution can be created
  • coach others in defining problems and describing appropriate options for solutions
  • help others challenge requirements and assumptions, and identify opportunities when defining problems and solution options

Strategy design

Level: expert

Expert is the fourth of 4 ascending skill levels

You can:

  • define and connect strategies or visions across the organisation or wider government
  • enable the implementation of strategies or visions across the organisation or wider government, for example, by advocating for resources and removing blockers

Technical design throughout the life cycle

Level: expert

Expert is the fourth of 4 ascending skill levels

You can:

  • create technical designs characterised by high risk, impact, and complexity
  • lead and guide others in creating technical designs that achieve organisational objectives
  • use feedback to optimise and refine standards for technical designs throughout the life cycle

Role Shared skills
Enterprise architect

Architect for the whole context

Architecture communication

Commercial perspective

Community collaboration

Making architectural decisions

Problem definition and shaping

Strategy design

Technical architect

Architect for the whole context

Architecture communication

Community collaboration

Making architectural decisions

Strategy design

Technical design throughout the life cycle

Change and release manager

Community collaboration

Command and control centre manager

Community collaboration

Frontend developer

Community collaboration

Updates

Published 28 February 2024

Last updated 30 November 2024

30 November 2024

  • In the 'expert' level description of the 'community collaboration' skill, the second requirement referring to 'understand the pychology of the team and have strong mediation skills' was removed as it is duplicated meaning of other requirements and does not meet framework guidelines for technical skills. This ensures consistency with the rest of the framework and allows for the skill to be shared with roles previously using the 'community collaboration (frontend developer)' skill.

31 May 2024

  • Solution architect now includes the skills 'community collaboration', 'making architectural decisions', 'problem definition and shaping', 'strategy design', and 'technical design throughout the life cycle'.
  • The skills 'governance and assurance', 'life cycle perspective', 'making and guiding decisions', 'requirements definition and management', 'strategy' and 'technical breadth' have been removed from the role.

28 February 2024

  • First published