Technology
Chief Technology Officer
Set the technical standard for Nexus: how it is built, secured, messaged, and released.
Role purpose
Inject Group Ltd licences Nexus, supervisory software that central banks and financial intelligence units run on their own estate. The Chief Technology Officer sets the technical standard for that product: how it is built, secured, messaged, packaged, and released.
This is not a generic digital-transformation seat. The postholder owns one engineering line — infrastructure, security, ISO 20022, and product delivery — and decides what belongs in the core versus what a local integrator may configure.
Success is a product a central-bank CIO can install, audit, and take a defect to, without discovering that the public story and the software disagree.
Accountabilities
Product and architecture
- Define the core engine, APIs, and what stays out of the product so an SI cannot rewrite it.
- Keep governor, FIU, operator, and admin workflows as one coherent system.
Security and sovereign deploy
- Own on-premise, air-gapped, and designated-cloud install paths with Principal Security and Infrastructure Architecture.
- Ensure identity, logging, keys, and break-glass work on an estate Inject Group does not operate.
Messaging and data
- Hold the ISO 20022 models and supervisory fields that FIU staff actually open.
- Refuse MT translations that drop originator, beneficiary, or travel-rule data.
Release and SI enablement
- Run a signed release train an integrator can install under the buyer’s change board.
- Make hotfixes and runbooks versioned with the product, not tribal knowledge.
Engineering line
- Lead infrastructure, security, messaging, and delivery as one organisation.
- Be the named technical counterpart a central-bank CIO can escalate a defect to.
External credibility
- Own the technical answers in the NDA pack, tenders, and incident posture.
- Keep every public claim inside what the software and the contract can defend.
Who this is for
Essential
- Executive or senior leadership of a software product used in a regulated, sovereign, or high-assurance environment.
- A record of shipping and operating complex systems — not only of writing strategy papers.
- Experience separating a core product from local configuration and integrator work.
- Working knowledge of identity, logging, encryption, and how those controls look off the public cloud.
- Experience of ISO 20022, payments messaging, or an equivalent structured-data domain.
- Built and held a multidisciplinary engineering organisation to a bar a buyer can audit.
- Oversight of release, packaging, and how a patch reaches a locked-down estate.
- Comfort briefing CIOs, procurement technical panels, and independent security reviewers.
Desirable
- Supervisory technology, FMI, IMTO, or central-bank infrastructure.
- Air-gapped or on-premise production in a public-sector buyer.
- HSM, PKI, or comparable key-management estates (Thales, Entrust, or equivalent).
How we judge this role
- A coherent architecture a buyer can install without a UK team on the floor every week.
- Clear core-versus-configuration boundaries that survive the first SI engagement.
- A release and hotfix path that works under the buyer’s change control.
- NDA-pack answers that match the running software.
- An engineering line that can take a live defect from a central-bank CIO.