Chief Architect in Swindon

The Chief Architect is the technical conscience of the Openwork technology function. This is a hands‑on, deeply technical role: you will own the architectural strategy for the entire estate, set and enforce the standards that govern how Openwork builds and assembles technology, and be the final word on whether what is being designed is coherent, secure, and fit for the long term. Openwork is executing an assemble architecture strategy—API‑first, cloud‑native, vendor‑core where it makes sense, and AI‑ready throughout. For our new digital proposition this means ensuring best of breed vendors are orchestrated into a coherent, scalable platform. Alongside this, we need to navigate the removal of a significant legacy estate. The Chief Architect will define how that integration works, hold the line on architectural integrity across every programme, and ensure that the choices made today do not create the legacy debt of tomorrow. This is not a role for someone who draws boxes on slides and delegates the hard thinking. You will be in the detail—reviewing designs, challenging decisions, writing ADRs, and making calls. You will also operate at the highest levels of the organisation, translating architectural direction into business outcomes for the CTO, Head of Engineering and Senior leadership teams. This is a hybrid role, based 3 days a week in the Swindon office.

The Benefits

• Salary – up to £120,000
• Car allowance: £7245
• Bonus scheme – on target bonus – 30%
• Pension scheme – contribute up to 5% of your salary and Openwork will match you and put in an extra 5%
• Critical illness cover
• Income protection
• Death in service – 4x salary
• 27 days holiday + bank holidays, with the opportunity to buy up to an additional 10 days
• A range of other flexible benefits to include private medical insurance, dental insurance and much more

Key Accountabilities

• Own and maintain the Openwork target architecture: a living, versioned artefact that reflects current state, transition state, and target state across all domains.
• Define, publish, and enforce architectural standards, principles, and patterns across the technology function—covering cloud, integration, data, security, and application architecture.
• Act as the architectural authority for the new digital proposition: approve integration designs, gateway patterns, and data flows across key vendors, and the wider Openwork estate.
• Lead the Architecture Review Board and Technical Design Authority (or equivalent governance mechanism): every significant design decision is reviewed, challenged, and approved before build commences.
• Produce and maintain Architecture Decision Records (ADRs) for all material decisions—capturing context, options considered, rationale, and implications.
• Partner with the Head of Engineering on technical quality: architectural and engineering standards are two sides of the same coin; this role sets the architectural half.
• Evaluate new technologies, platforms, and vendors against the assemble architecture strategy—providing clear, evidence‑based recommendations to the CTO.
• Own the adopt‑not‑adapt principle in practice: identify where customisation is being proposed without sufficient justification and elevate or reject accordingly.
• Lead architectural thinking on AI and agentic capability: define patterns for safe, governed adoption of AI across the Openwork platform.
• Actively contribute to the decommissioning strategy under Clean Slate: map legacy dependencies, identify safe removal sequences, and ensure replacement architectures are sound before migration begins.
• Mentor and develop the architecture community within the technology function.

What will you need to succeed?

• Experienced architect – a strong track record operating hands‑on as an enterprise or solution architect within complex, multi‑system environments, with accountability for shaping and upholding architecture standards.
• Modern Azure architecture – deep experience designing cloud‑native, API‑first and event‑driven solutions on Azure, including integration patterns and scalable platform design.
• Technical breadth and depth – practical experience across modern application design (.NET, microservices), data platforms, AI‑led architectures, and engineering practices such as DevSecOps and infrastructure‑as‑code.
• Security and regulation – good understanding of security‑by‑design, identity and access management, and designing within regulated environments (ideally financial services).
• Commercial and stakeholder focus – able to connect architecture decisions to business outcomes and communicate clearly with both senior stakeholders and technical teams.
• Relevant industry insight – experience within regulated sectors, with financial services or platform‑based businesses particularly beneficial.
• Leadership and approach – brings sound judgement, clear thinking and a collaborative style; able to challenge constructively, support others, and continuously improve how architecture is delivered.

Equal opportunity statement: The Openwork Partnership is an equal‑opportunity employer and does not discriminate on the basis of race, religion, disability, gender or any other protected characteristic.