Skip to content

Full role catalogue

Analysis

  • Business Analyst — Understand a business problem well enough that the right thing gets built, and specify it so it can be tested
  • Systems Analyst — Bridge requirements and existing systems: what the systems do now, what they must do, and what has to change
  • Requirements Engineer — Engineer the requirements set itself: elicitation, specification, validation and management over the full lifecycle
  • Process Analyst — Model, measure and improve how work actually flows through the organisation
  • Enterprise Business Analyst — Analyse problems that span domains, systems and business units, where no single team owns the answer
  • Data Analyst — Answer business questions with data, honestly, including when the data cannot answer them
  • Business Intelligence Analyst — Turn agreed metrics into reporting products people can trust and use without asking an analyst
  • FinOps Analyst — Make cloud and technology spend visible, attributable and defensible
  • Product Analyst — Measure how the product is actually used and whether changes to it worked
  • Service Level Analyst — Measure and report whether services deliver what was promised, and make the gaps visible early
  • Configuration Analyst — Keep the record of what exists, how it is connected and who owns it accurate enough to rely on during an incident

Architecture

  • Enterprise Architect — Keep the whole technology estate coherent and steerable against business strategy
  • Business Architect — Model what the business does and needs to be able to do, independent of how systems currently support it
  • Solution Architect — Design one solution end to end so that it meets its requirements, fits the estate and can actually be built and run
  • Application Architect — Own the internal structure of one significant application so it stays changeable over years
  • Domain Architect — Own the architecture of one business domain so that its systems, data and integrations stay coherent
  • Data Architect — Design how data is structured, stored, moved and governed across the estate
  • Integration Architect — Design how systems talk to each other so that coupling stays manageable as the estate changes
  • Cloud Architect — Design cloud platforms that meet performance, cost, resilience and sovereignty requirements
  • Network Architect — Design the network so that connectivity, segmentation and performance meet requirements at acceptable cost
  • Security Architect — Design security into systems so that controls are structural rather than bolted on afterwards
  • AI and ML Architect — Design systems that train, serve and govern models reliably and within their legal and ethical limits
  • Technical Design Authority Member — Provide independent review of significant designs so that quality and coherence survive delivery pressure
  • Architecture Repository and Modelling Lead — Keep architecture models, viewpoints and repository semantics consistent enough that published views are traceable, reusable and trustworthy across projects.
  • Identity and Access Management Architect — Design identity, authentication, authorisation, privilege and federation as one coherent architecture across workforce, customer and workload identities.
  • Operational and Technology Resilience Architect — Design end-to-end technology resilience across services, dependencies, failure domains and recovery capabilities so that business impact tolerances are technically credible.
  • Enterprise Applications Architect — Own the target enterprise application landscape and the architecture decisions that govern strategic platforms, enterprise SaaS/ERP ecosystems, capability fit, integration boundaries and application rationalisation.
  • Secure Delivery / DevSecOps Architect — Own the secure delivery architecture that turns security policy into enforceable Secure SDLC, CI/CD, software supply-chain, policy-as-code and developer control patterns without collapsing assurance into the delivery team.
  • Application Portfolio Manager — Own application portfolio lifecycle decisions and evidence, maintaining a defensible view of business fit, technical health, cost, risk, redundancy and transition so invest/tolerate/migrate/retire choices are governed rather than anecdotal.

Commercial, Sourcing and Enablement

  • IT Procurement Specialist — Buy technology on terms that serve the organisation, with the right people involved before signature
  • Vendor Manager — Manage suppliers after signature: performance, relationship, risk and value
  • Contract Manager — Make sure what was agreed is written down correctly and then actually happens
  • Software Licence Compliance Specialist — Understand licensing rules well enough to keep the organisation compliant and out of audit exposure
  • Pre-Sales Solution Consultant — Show prospects credibly how the product solves their problem, without promising what cannot be built
  • Sales Engineer — Provide the technical substance behind the sale: validation, integration answers and honest limitations
  • Customer Success Engineer — Make sure customers get the value they bought, and surface problems before they become churn
  • Implementation Consultant — Get the product working in the customer's environment, configured for how they actually operate
  • Technical Account Manager — Be the named technical owner of a major customer relationship across support, adoption and escalation
  • Technical Writer — Produce documentation people can actually use at the moment they need it
  • Developer Advocate — Help external developers succeed with the product, and bring their reality back to the product team
  • IT Trainer — Build the capability people need to use technology properly, measured by what changes afterwards
  • Technical Recruiter — Find and attract people who can actually do the work, without wasting anyone's time
  • Resource Manager — Match people to work across the portfolio, honestly, including when there are not enough of them
  • IT Financial Management / TBM Manager — Own the transparent service/project cost model, TCO and technology-business allocation model that lets leaders make comparable investment, sourcing, optimisation and lifecycle decisions across cloud and non-cloud spend.
  • Bid / Proposal Manager — Own the supplier's evidence-based bid and proposal process from qualification through submission, clarification and controlled handover, so the offer is complete, responsive, deliverable and authorised.
  • Commercial Pricing / Deal Finance Specialist — Develop defensible supplier selling-price and deal-finance recommendations that connect delivery cost, cash flow, commercial terms and uncertainty to authorised return and risk appetite over the full contract lifecycle.
  • Estimation / Cost Engineering Specialist — Produce and maintain a reproducible basis of estimate for supplier work and lifecycle cost, with calibrated methods, explicit uncertainty and a learning loop from actual delivery rather than unsupported numerical precision.
  • Independent Commercial Assurance Reviewer — Independently challenge the evidence, completeness and consistency of supplier proposals, estimates, pricing and lifecycle commercial controls, reporting located findings without authoring the model or accepting management's risk.
  • Supplier Commercial / Deal Manager — Own supplier-side commercial coherence across qualification, negotiation, contract handover, delivery change, service operation, renewal and exit, ensuring agreed commitments and economic risk remain aligned throughout the deal.

Data, Analytics and AI

  • Data Engineer — Move data reliably from where it is produced to where it can be used, at known quality and cost
  • Analytics Engineer — Turn raw data into well-modelled, tested, documented datasets that analysts can trust
  • Database Administrator — Keep databases available, performant, recoverable and secure
  • Database Reliability Engineer — Apply engineering practice to data stores: automation, service objectives and safe schema evolution
  • Data Modeller — Define what the data means and how it is structured, so that systems and people agree
  • Data Steward — Take day-to-day responsibility for the meaning, quality and correct use of data in one domain
  • Data Owner — Be accountable for a data asset: its quality standard, who may use it and on what basis
  • Data Custodian — Hold and protect data technically on the owner's behalf: storage, access enforcement, retention and disposal
  • Data Governance Lead — Make data governance operate in practice: roles, policy, quality standards and the forum that resolves disputes
  • Data Quality Analyst — Measure whether data is fit for its purpose, and make the cost of poor quality visible
  • Master Data Management Specialist — Establish and maintain single, trusted versions of core business entities across systems
  • Data Scientist — Answer hard questions with statistical and machine learning methods, and say honestly how much to trust the answer
  • Research Scientist — Advance the state of what the organisation can do, and publish results that survive scrutiny
  • Machine Learning Engineer — Take models from notebook to production and keep them working under real conditions
  • MLOps Engineer — Run the machine learning platform and lifecycle: deployment, monitoring, retraining and rollback
  • LLMOps and AI Platform Engineer — Run the platform for large model workloads: serving, cost, evaluation, safety controls and observability
  • AI Solutions Engineer — Design and build applications on top of foundation models so they behave reliably in a real workflow
  • AI Safety and Model Red Team Specialist — Probe models and AI systems for harmful, unsafe or manipulable behaviour before users find it
  • AI Governance Officer — Hold AI systems inside their legal, ethical and risk boundaries throughout their lifecycle
  • Data Privacy Engineer — Build privacy into data systems technically, rather than documenting it after the fact
  • Metadata Manager — Make it possible to find data, understand it and trace where it came from

Design and User Experience

  • UX Designer — Design how the product works for the people using it, based on evidence rather than preference
  • UI Designer — Design the visual layer so that it communicates clearly, works at every size and meets accessibility requirements
  • Product Designer — Own the whole design of a product area: research, interaction, visual and the outcome it produces
  • UX Researcher — Find out what users actually do and need, using methods that produce trustworthy answers
  • Usability Tester — Run structured usability sessions that show whether people can complete real tasks
  • Interaction Designer — Design the detailed behaviour of the interface: states, transitions, feedback and micro-interactions
  • Service Designer — Design the whole service across channels, including the parts users never see
  • Information Architect — Organise content and functionality so people can find things and understand where they are
  • Design System Engineer — Build and maintain the shared component library so that consistency and accessibility are the default
  • Accessibility Specialist — Make sure the organisation's digital services are usable by disabled people, and can prove it
  • Content Designer — Write the words in the product so that people understand what to do and what just happened

Executive and Leadership

  • Chief Information Officer — Own the enterprise IT capability, its budget, its risk posture and its ability to serve the business
  • Chief Technology Officer — Set the technology direction for the products the organisation sells and own the engineering capability that builds them
  • Chief Information Security Officer — Own the information security programme, articulate security risk in business terms and hold the organisation to its stated risk appetite
  • Chief Data Officer — Own data as an enterprise asset: its quality, its governance, its lawful use and the value extracted from it
  • Chief Digital Officer — Lead the change of business models, channels and ways of working that digital capability makes possible
  • Chief Product Officer — Own the product portfolio, its strategy, its profitability and the discipline of deciding what not to build
  • Chief AI Officer — Direct the adoption of AI across the organisation and hold it inside legal, ethical and risk boundaries
  • IT Chief of Staff — Make the technology leadership team's decisions, cadence and commitments actually operate
  • VP of Engineering — Own the engineering organisation's ability to deliver: its structure, its standards, its throughput and its people
  • Head of Platform — Run the internal platform as a product so that stream-aligned teams can deliver safely without waiting on central approval
  • IT Service Owner — Own one service end to end across its lifecycle: its value, its cost, its risk and its performance for users

Governance, Risk, Compliance, Audit and Privacy

  • IT Governance Manager — Make sure technology decisions are made by the right people, on evidence, within appetite
  • GRC Analyst — Keep the governance, risk and compliance machinery running with accurate, current data
  • IT Risk Manager — Make technology risk visible, comparable and owned, so the organisation can decide rather than hope
  • Information Security Officer (Local) — Be the accountable security presence inside a business unit or country, close enough to the work to see what is really happening
  • Compliance Officer (Technology) — Translate external obligations into internal requirements and prove they are met
  • Internal IT Auditor — Give independent, evidence-based assurance about whether controls are designed and operating properly
  • External Auditor and Assessor — Provide independent third-party assessment against a defined scheme, to that scheme's rules
  • Control Owner — Be accountable for one control: that it is designed properly, operates as intended and can be evidenced
  • Control Tester — Test whether controls actually operate, using a defensible method and sample
  • Data Protection Officer — Independently oversee how personal data is handled and advise on compliance with data protection law
  • Privacy Analyst — Do the detailed privacy work: assessments, records, rights requests and advice on new processing
  • Records Manager — Decide how long information is kept, why, and make sure it is actually disposed of
  • Business Continuity Manager — Make sure the organisation can keep operating, and recover, when something serious happens
  • Disaster Recovery Coordinator — Make sure technical recovery actually works when it is needed, by testing it before it is
  • Third-Party Risk Manager — Understand and control the risk that comes with suppliers, especially the ones you cannot live without
  • Policy Author — Write policy and standards that people can follow, that mean something, and that can be audited
  • Crisis Manager — Lead the organisation through events that exceed normal incident handling
  • Privacy Architect — Translate privacy obligations and risk into solution and enterprise architecture constraints, patterns and traceable design decisions.

Infrastructure, Cloud and Operations

  • Linux Systems Administrator — Keep Linux systems running, patched, hardened and recoverable
  • Windows Systems Administrator — Keep Windows Server and directory infrastructure available, secure and correctly configured
  • Cloud Engineer — Build and maintain cloud infrastructure as code, within the agreed guardrails
  • Cloud Operations Engineer — Run the cloud estate day to day: health, cost, compliance and incident response
  • Platform Engineer — Build the internal platform that lets product teams deploy and run services safely on their own
  • DevOps Engineer — Remove the handoff between building and running by automating the path to production
  • Site Reliability Engineer — Make services reliable enough for the business by engineering, not by heroics
  • Kubernetes Platform Engineer — Run container orchestration as a reliable, secure, multi-tenant platform
  • Infrastructure as Code Engineer — Define the whole estate as reviewed, versioned, reproducible code so that no environment depends on remembered manual steps
  • Container Platform Engineer — Build and maintain the container image supply chain and stack definitions so that what runs in production is provably what was built
  • Environment Manager — Own the lifecycle of non-production environments so teams can test realistically without waiting for each other
  • Virtualisation Engineer — Run the virtualisation estate: capacity, resilience, patching and lifecycle
  • Storage Engineer — Provide storage that performs, protects data and scales predictably
  • Backup and Recovery Engineer — Make sure the organisation can actually get its data back, under the conditions it will really face
  • Datacentre Technician — Keep the physical estate working: installation, replacement, cabling, power and physical access
  • Capacity Manager — Make sure there is enough capacity to meet demand, and not much more, at acceptable cost
  • Availability Manager — Ensure services meet their availability commitments by design and by evidence
  • Observability Engineer — Make the system's behaviour knowable: metrics, logs, traces and alerts that people trust
  • Middleware Administrator — Run application servers, message brokers and integration middleware reliably
  • FinOps Engineer — Engineer cloud cost down without reducing capability: architecture, automation and accountability
  • Sustainable IT Engineer — Measure and reduce the environmental impact of the technology estate with defensible numbers

Network and Telecommunications

  • Network Engineer — Build, configure and maintain the network so traffic flows correctly, securely and fast enough
  • Network Administrator — Keep the network estate documented, patched and operating within standards day to day
  • Network Operations Centre Analyst — Watch the network and services continuously, and start the response the moment something breaks
  • Wireless and RF Engineer — Design and tune wireless coverage and capacity so it works where and when people need it
  • Unified Communications Engineer — Run voice, video and messaging services so that critical communication works, including in emergencies
  • SD-WAN and Edge Engineer — Connect distributed sites reliably and cost-effectively, with policy applied at the edge
  • Firewall and Perimeter Engineer — Implement and maintain network security policy enforcement without breaking the business or leaving holes
  • DNS DHCP and IPAM Specialist — Run the naming and addressing services that everything else silently depends on
  • Network Field Technician — Install, patch and physically maintain network infrastructure on site

Offensive Security and Adversarial Testing

  • Penetration Tester (Network and Infrastructure) — Find and demonstrate exploitable weaknesses in infrastructure under written authorisation, then explain how to fix them
  • Penetration Tester (Web Application) — Test web applications against the full range of application-layer attacks, under authorisation
  • Penetration Tester (Mobile) — Test mobile applications and their backends for weaknesses that reach data or accounts
  • Penetration Tester (API) — Test interfaces for authorisation, validation and business logic failures that clients never see
  • Penetration Tester (Cloud) — Test cloud environments and their identity and configuration weaknesses, within provider rules
  • Penetration Tester (Wireless) — Test wireless networks for access control and isolation failures, without disrupting legitimate users
  • Penetration Tester (Thick Client) — Test installed desktop applications and their local trust assumptions
  • Red Team Operator — Emulate a real adversary against the whole organisation to test detection and response, not to list vulnerabilities
  • Red Team Lead — Run offensive engagements safely, legally and to a standard the client can act on
  • Exploit Developer — Develop reliable proof-of-concept exploitation capability for authorised testing and defensive research
  • Vulnerability Researcher — Find previously unknown weaknesses in software or hardware and get them fixed responsibly
  • Binary Reverse Engineer — Understand undocumented software or hardware behaviour from its compiled form, lawfully
  • Social Engineering Specialist — Test human-layer defences under authorisation, without harming the people being tested
  • Physical Intrusion Specialist — Test physical security controls under authorisation, safely and with an unambiguous get-out-of-jail letter
  • Open Source Intelligence Investigator — Build an accurate picture from publicly available information, lawfully and without touching targets
  • Adversary Emulation Engineer — Automate the repeatable execution of adversary techniques so detection coverage can be measured continuously
  • Breach and Attack Simulation Engineer — Run continuous, safe simulation of attack paths to validate that controls still work today
  • Bug Bounty Programme Manager — Run an external researcher programme that produces real findings and treats researchers professionally
  • Bug Bounty Triage Analyst — Validate and prioritise external submissions accurately and quickly
  • Vulnerability Disclosure Coordinator — Receive, coordinate and resolve externally reported vulnerabilities in the organisation's own products
  • Hardware and IoT Security Researcher — Assess the security of physical devices where the attacker has the hardware in their hands

Product, Delivery and Agile

  • Product Manager — Decide what gets built and why, based on evidence of customer need and business value
  • Product Owner — Maximise the value of the work the development team does by owning and ordering the product backlog
  • Technical Product Manager — Own products whose customers are engineers: APIs, platforms, SDKs and internal developer capabilities
  • Scrum Master — Make the team's delivery system work: flow, impediments, and the health of the agreed way of working
  • Agile Coach — Raise the delivery capability of multiple teams by changing how they work, not by doing their work
  • Delivery Manager — Get a defined body of work delivered across teams, dependencies and suppliers
  • Release Train Engineer — Run the programme-level cadence: planning, dependency resolution and flow across a group of teams
  • Epic Owner — Shepherd one large investment from hypothesis through to measured outcome
  • SAFe System Architect — Maintain the architectural runway so that teams can deliver upcoming features without stalling
  • Project Manager — Deliver a defined scope to agreed time, cost and quality, and manage what changes
  • Programme Manager — Deliver a coherent set of projects and change activity that together produce a business outcome
  • Portfolio Manager — Decide which investments the organisation starts, continues and stops, against capacity and strategy
  • PMO Analyst — Turn raw delivery data into a trustworthy picture of portfolio health
  • PMO Lead — Own the delivery governance framework: standards, assurance, reporting and the capability of delivery roles
  • Engineering Manager — Build and sustain a team that can deliver good software repeatedly, and grow the people in it
  • Technical Lead — Set and hold the technical direction inside one team, and keep its code and design healthy enough to change
  • Transformation Manager — Make the organisational change stick: roles, processes, behaviours and capability, not just systems
  • Organisational Change and Adoption Manager — Make the people-side of technology change adoptable, measurable and owned so that delivered capability becomes changed behaviour and realised value.
  • Benefits Realisation Manager — Turn investment claims into measurable benefits with owners, baselines, dependencies and post-implementation accountability.
  • Data Migration and Cutover Lead — Plan and govern migration and cutover so that data, dependencies, business continuity and rollback are proven before irreversible production change.
  • Enterprise Release Manager — Orchestrate enterprise releases across products, platforms, suppliers and business domains, owning the integrated release calendar, readiness model and delegated go/no-go decision without performing the technical deployment.
  • Demand & Intake Manager — Own the controlled entry of demand into the IS/IT portfolio: qualification, duplication/capability fit, minimum evidence, sizing readiness, risk/value framing and transparent prioritisation handoff.

Quality and Testing

  • Test Analyst — Design and run tests that find the defects that matter before customers do
  • Test Automation Engineer — Build automated checks that run fast, fail honestly, and are worth maintaining
  • Performance Test Engineer — Prove how the system behaves under realistic and unrealistic load, before production does it for you
  • Test Manager — Own the test strategy, resourcing and the honest reporting of residual quality risk
  • Test Architect — Design the overall approach to quality across systems, environments, data and tooling
  • User Acceptance Test Coordinator — Get the business to prove the solution works for their actual work, and capture what they find
  • Accessibility Tester — Verify that people using assistive technology can actually complete the tasks, not just that a checker passes
  • Localisation QA Analyst — Verify that the product works, reads correctly and is culturally appropriate in every locale shipped
  • Chaos and Resilience Engineer — Prove the system survives the failures it claims to survive, under controlled conditions
  • Codebase Reviewer — Audit an existing codebase end to end and report, in priority order, what will actually hurt — without changing a line
  • Release Quality Gatekeeper — Hold the line on release quality in regulated environments where evidence, not opinion, decides

Research, Innovation and Specialist Engineering

  • Research Engineer — Build and evaluate what does not exist yet, rigorously enough that the results can be trusted
  • Innovation Lead — Run the pipeline from idea to validated capability without wasting the organisation's attention
  • Technology Scout — Watch what is emerging and tell the organisation what deserves attention, when
  • Standards Body Representative — Represent the organisation's interests in external standards work and bring the outcomes back inside
  • Ethics and Responsible Technology Lead — Make sure the organisation considers the harm its technology can do, before it does it
  • Systems Engineer (INCOSE) — Engineer the whole system across hardware, software, people and process so that it meets its purpose
  • Simulation Engineer — Build models that predict real-world behaviour well enough to make decisions with
  • High Performance Computing Engineer — Run and optimise large-scale computing so that scientific and engineering workloads complete efficiently
  • Quantum Computing Engineer — Assess and develop quantum computing capability honestly, separating real capability from marketing

SABSA Security Architecture

  • Chief Security Architect (SABSA Practice Lead) — Own the enterprise security architecture practice and keep every security decision traceable to a business driver
  • Business Security Architect (SABSA Contextual Layer) — Establish what the business needs security to achieve, in the business's own language, before any technology is considered
  • Business Attribute Profiler — Translate business drivers into measurable business attributes that security architecture can actually be designed and tested against
  • Conceptual Security Architect (SABSA Architect's View) — Define the security strategy, domains, trust model and control objectives that satisfy the business attributes
  • Logical Security Designer (SABSA Designer's View) — Design the logical security services, policies and information flows that deliver the control objectives
  • Physical Security Solution Builder (SABSA Builder's View) — Turn logical security design into a concrete, buildable solution specification
  • Security Component Specialist (SABSA Tradesman's View) — Select, configure and integrate the specific products, standards and tools that realise the design
  • Security Service Manager (SABSA Service Management View) — Run the security architecture in operation, across every layer, so that designed capability stays real
  • Security Domain Authority — Own the security policy, trust relationships and risk decisions within one defined security domain
  • Security Risk and Opportunity Architect — Apply SABSA risk practice so that security addresses both threats to avoid and opportunities to enable
  • Security Assurance and Measurement Architect — Design how the organisation proves its security architecture is working, using measures derived from business attributes
  • SABSA and TOGAF Integration Architect — Make security architecture and enterprise architecture one coherent practice rather than two competing ones

Security Operations and Defensive Security

  • Security Analyst Tier 1 — Triage security alerts quickly and accurately so that real threats reach the right people fast
  • Security Analyst Tier 2 — Investigate escalated alerts to a defensible conclusion and contain what is confirmed
  • Security Analyst Tier 3 — Handle the hardest investigations and raise the analytical capability of the whole team
  • SOC Manager — Run the security operations capability: coverage, quality, people and the pace of response
  • Threat Hunter — Look for adversaries that existing detection missed, using hypotheses rather than alerts
  • Incident Responder — Lead the technical response to confirmed security incidents: contain, eradicate, recover, evidence
  • Digital Forensics Examiner — Produce forensically sound evidence that will survive legal, regulatory or disciplinary scrutiny
  • Malware Analyst — Determine what malicious code does, so the organisation can detect it, remove it and assess the damage
  • Threat Intelligence Analyst — Turn information about adversaries into decisions the organisation actually makes
  • Detection Engineer — Build and maintain the detection logic that turns telemetry into reliable signal
  • Security Engineer — Build and run the security controls that the architecture calls for
  • Vulnerability Management Analyst — Find, prioritise and drive the fixing of vulnerabilities before they are exploited
  • Cryptography and PKI Engineer — Run the organisation's keys, certificates and cryptographic controls so that trust holds and nothing expires unexpectedly
  • Secrets and Configuration Management Engineer — Give every credential and configuration value a managed lifecycle, so nothing important lives in a repository, a wiki or someone's terminal history
  • Identity and Access Management Engineer — Build the systems that decide who can access what, and make the right answer the easy one
  • Identity Governance Specialist — Prove that access rights are appropriate, reviewed and removed when no longer needed
  • Privileged Access Management Administrator — Control, monitor and constrain the accounts that could do the most damage
  • Cloud Security Engineer — Secure cloud platforms where the control plane is the new perimeter
  • Application Security Engineer — Make secure software the default by building security into the delivery pipeline and the teams
  • Security Champion — Be the security-aware engineer embedded in a delivery team, closing the distance to the security function
  • Operational Technology Security Engineer — Protect industrial control and operational technology where safety and availability outrank confidentiality
  • Security Awareness and Training Manager — Change what people actually do, not what they can recite in a quiz
  • Insider Threat Analyst — Detect and address harm caused by people with legitimate access, within strict legal and ethical limits
  • Purple Team Lead — Measure and improve detection and response by running offensive techniques with the defenders in the room

Service Management and Support

  • Service Desk Analyst — Be the reliable first point of contact: resolve what you can, route the rest accurately, and keep the user informed
  • Desktop Support Engineer — Get individual users working again, and keep their devices secure and current
  • Application Support Analyst — Keep business applications working and be the bridge between users and engineering
  • Incident Manager — Restore service quickly and keep everyone correctly informed while it is down
  • Major Incident Manager — Take command of high-impact incidents: mobilise, coordinate, communicate and decide
  • Problem Manager — Find and remove the causes of incidents rather than repeatedly restoring service
  • Change Manager — Balance the speed of change against the risk it introduces, with evidence rather than ceremony
  • Request Fulfilment Manager — Deliver routine service requests predictably, quickly and within entitlement
  • Service Level Manager — Negotiate, monitor and defend the service commitments made to the business
  • Service Catalogue Manager — Maintain an accurate, usable catalogue of what IT actually offers and on what terms
  • Continual Improvement Manager — Make improvement a managed activity with evidence rather than an aspiration
  • Knowledge Manager — Make what the organisation knows findable and usable at the moment of need
  • Configuration Manager — Own the accuracy of the record of what exists and how it relates, because everything else depends on it
  • IT Asset Manager — Know what the organisation owns, what it costs, where it is and when it must be dealt with
  • Software Asset Manager — Keep software licensing compliant and cost-effective, and be ready for an audit at any time
  • End-User Computing Engineer — Engineer the device and workplace platform so that endpoints are secure, current and usable
  • Business Relationship Manager — Be the trusted two-way channel between a business area and IT, translating need into demand and capability into value
  • Service Transition and Operational Readiness Manager — Prove that a new or changed service can be operated, supported, monitored, recovered and owned before it is accepted into production.
  • Technology Lifecycle and Decommission Manager — Retire technology, services and platforms without leaving hidden dependencies, unmanaged data, active access, stale assets, avoidable cost or unowned residual obligations.
  • SIAM Manager — Own end-to-end service integration and accountability across multiple internal and external suppliers, ensuring process, SLA/OLA, incident, problem, change and acceptance responsibilities join into one operable service model.

Software Development and Engineering

  • Software Engineer — Turn requirements into working, tested, observable and maintainable software
  • Senior Software Engineer — Deliver the hard changes and raise the technical quality of everyone around you
  • Staff Engineer — Solve technical problems that cross team boundaries and would otherwise be nobody's problem
  • Backend Engineer — Build the server-side logic, data access and APIs that everything else depends on
  • Frontend Engineer — Build the user-facing application so it is fast, accessible and behaves correctly in the real world
  • Full-stack Engineer — Deliver a feature across the whole stack without waiting for a handoff at every layer
  • Mobile Engineer — Build and maintain native or cross-platform mobile applications, including their release and update path
  • Embedded Firmware Engineer — Build software that runs on constrained hardware, reliably, for years, often without a maintenance window
  • Real-time Systems Engineer — Build systems where being late is the same as being wrong
  • Systems Programmer — Work at the operating system boundary: kernels, drivers, runtimes and performance-critical primitives
  • Mainframe Developer — Maintain and evolve the core systems that the business has depended on for decades
  • API Developer — Build and maintain interfaces other teams depend on, with contracts that do not break them
  • Integration Developer — Build the flows that move data and events reliably between systems that were never designed to talk
  • ERP and CRM Consultant Developer — Configure and extend packaged business platforms without destroying their upgradeability
  • Low-code and RPA Developer — Automate business processes quickly using platform tooling, without creating ungoverned shadow systems
  • Game Developer — Build interactive software where performance, feel and player experience are the requirements
  • Graphics and Engine Engineer — Build the rendering and engine systems that everything else in the product runs on
  • Blockchain and Smart Contract Developer — Build distributed ledger applications where deployed code is effectively permanent and holds value
  • Quantitative Developer — Implement pricing, risk and trading models correctly, fast, and reproducibly
  • Compiler and Toolchain Engineer — Build the language tooling other engineers depend on: compilers, analysers, build systems and runtimes
  • Build Engineer — Make builds fast, reproducible and trustworthy so that nobody debugs the build instead of the product
  • Release Engineer — Get validated changes into production predictably, with an honest record of what shipped
  • CI/CD Platform Engineer — Own the delivery pipeline platform itself — runners, shared workflows, caching, secrets and provenance — so every team ships through a path that is fast and trustworthy
  • GitOps and Continuous Delivery Engineer — Make deployment a reviewed change to declared desired state, with progressive rollout and automatic reversal rather than hope
  • Developer Experience Engineer — Reduce the friction between an engineer having an idea and that idea running in production
  • Open Source Program Office Engineer — Manage how the organisation consumes, contributes to and publishes open source safely
  • Software Modernisation Engineer — Change legacy systems safely and incrementally, without a big-bang rewrite nobody survives