Architect, Agentic Interfaces

Own the technical design of the agent-native layer end to end, and hold it coherent across the teams building into it. This is a hands-on architecture role with design authority, not a line-management role. Key responsibilities - Own the architecture of the agent-facing interface, the semantic layer beneath it and the controls around it, and keep the design coherent as separate teams build into it. - Set and hold the interface contract: what is exposed, at what granularity, how it versions, and what stays private. - Adjudicate between competing technical approaches where more than one team is solving the same problem, and make the call. - Define the evaluation approach that decides whether the layer is good enough to expose, and set the standard the engineering teams build to. - Establish the security and governance model for agent access, covering identity, entitlements, isolation between customers and safe defaults. - Work with product management, platform engineering and the AI teams to sequence the build against a delivery roadmap. - Represent the architecture to senior technical stakeholders inside IFS, to customers, and to partners. - 10+ years in software engineering with 3+ years in a lead architect role on a platform used by other teams or external developers. - Track record of owning the architecture of a production platform at enterprise scale, through delivery rather than on paper. - Deep API and interface design experience, including versioning, backward compatibility and deprecation across a large consumer base. - Hands-on experience with AI systems that call tools or functions in production, and a clear view of where they fail. - Experience with semantic modelling, knowledge graphs or ontologies over an existing product or data estate. - Security and multi-tenancy design experience: identity, entitlements, isolation between customers. - Able to hold a technical position with senior stakeholders and change it on evidence. Desirable - Experience of enterprise application platforms and their extension or integration models. - Published or public technical work: standards contributions, open source, conference talks. - Background in asset-intensive industries.