Platform Architect - Banking

<p style="min-height:1.5em"><strong>About us</strong></p><p style="min-height:1.5em">EggAI is a fast-growing AI consulting and development startup. We build agentic AI solutions for enterprise clients. We are growing in several European markets.</p><p style="min-height:1.5em"><strong>The role</strong></p><p style="min-height:1.5em">You will own the design of a shared AI platform for our clients. The platform has two parts. An AI Control Plane governs what agents may do, through identity and delegated permissions, policy enforcement, approvals, budgets and durable audit records. A managed AI Runtime is where the agents run. Both integrate with the client's identity, security, delivery and audit services.</p><p style="min-height:1.5em">You will set the architecture, define how services and controls fit together, and make sure what the team builds is sound, assured and ready for production. The role reaches across engineering, security, audit, risk and the client's architecture function. You will take designs through their governance, record the decisions, and give the engineers a design they can build and the client a design they can approve.</p><p style="min-height:1.5em">You will be EggAI's accountable architecture lead on the engagement, leading design for a delivery team of platform engineers. You make the technical decisions within the team's remit, recommend on the rest, and secure the client's approval where their architecture or risk governance requires it. </p><p style="min-height:1.5em"><strong>What you will do</strong></p><p style="min-height:1.5em">- Own the architecture of the AI Control Plane and AI Runtime and keep it aligned with the client's architecture standards, cloud substrate, API gateway, identity provider and audit services.<br />- Define service interfaces and contracts. Decide where each security and policy control is enforced: in the gateway, the control plane, the runtime or the client's own services.<br />- Keep the design record. Write architecture decision records (ADRs) and record every deviation from the client's standards or our reference designs for a client decision.<br />- Take designs through the client's architecture and risk forums. Secure approvals in time for dependent work, so that design precedes implementation.<br />- Lead design and quality review across all platform services. Review engineers' changes, cross-service tests and fault exercises with the CTO.<br />- Define how the architecture will be proven. Agree acceptance criteria with engineers and client control owners for each interface, control and infrastructure contract, including behaviour when a dependency fails, and review the test evidence showing they are met.<br />- Hold the build to the design's principles: policy enforced outside the agent, decisions recorded before actions take effect, fail closed with stop always available, and audit evidence that is administered independently of the people who build and run the platform, reconciled against what actually happened, and readable with the client's own tools.<br />- Maintain the inventory of platform controls. Record for each one whether it is enforced or only monitored, whether it is implemented, tested or still open, and what evidence it produces, so acceptance reviews work from a current record and coverage gaps are visible.<br />- Assess proposed technology, scope and dependency changes for their effect on the design, controls, effort and running costs, and give the programme lead a clear basis for plan and cost decisions.<br />- Evaluate new runtimes and managed services against the platform's control requirements. Compare shared controls with provider-native ones on integration effort, operating cost and assur