Role profile library
Predefined role profile
IT business analysts, architects and systems designers
The behaviours this profile measures, drawn from the great{with}talent job library and occupational research. Download the full competency-based interview guide to assess them.
The full interview guideCompetency-based questions, follow-up probes and a 1–5 rating form for each behaviour — ready to print or run on screen.
Download
Behaviours assessed — 5 priority competencies
1
Analytical Skills
Breaks a problem down into its core elements. Draws on different data sources to inform their thinking, identifying the most pertinent issues within this. Incorporates the emotive elements of a situation into their thinking, before making sound inferences based on the available information.
Why this matters for IT business analysts, architects and systems designers: BABOK Strategy analysis and Requirements analysis knowledge areas centre breaking complex business problems into elements. BCS Modelling business processes is a named competence. The whole craft is structured analytical reasoning across systems, processes, and stakeholder needs.
2
Technical Capability
Has the necessary knowledge, skills and proficiency to conduct their role. Demonstrates mastery in their area of technical capability. Stays up to date with advances in their field and commits to their continuous development.
Why this matters for IT business analysts, architects and systems designers: BCS competence framework + SFIA technical knowledge requirement + DDaT architecture skills (modelling, patterns, trade-off analysis). The role demands strong technical literacy across systems, data, integration patterns, and methodologies.
3
Collaborative Working
Looks to understand others’ perspectives and objectives. Respects different styles/approaches, whilst adapting their own style to enable them to work effectively with others.
Why this matters for IT business analysts, architects and systems designers: BABOK Elicitation and collaboration is one of the six core knowledge areas — workshops, stakeholder engagement, group facilitation. DDaT Solution Architect explicitly works closely with stakeholders. Coordination across business and IT is central.
4
Influencing and Persuading
Presents simple, impactful messages in a compelling manner. Changes their emphasis and approach to address resistance, focusing on the value their ideas will bring different stakeholders. Confidently negotiates effective outcomes.
Why this matters for IT business analysts, architects and systems designers: BABOK Strategy analysis emphasises current state vs future state and change strategy. The BA/architect's job is partly to sell change to stakeholders, build consensus across functions, and surface trade-offs that aren't obvious. Persuasion in the absence of authority is sustained.
5
Strategic Perspective
Understands the wider context within which they operate, being quick to spot new opportunities. Has a clear view of the future needs for their part of the organisation, balancing immediate needs with longer-term requirements. Considers issues from an organisational as well as local perspective.
Why this matters for IT business analysts, architects and systems designers: BABOK Strategy analysis covers change strategy and future state design. SFIA at senior level expects contribution to formulation of strategy. DDaT architects make architectural choices with long-term implications. The role demands a longer horizon than the developer's.