AI Foundation Architect

h3Why Keyrus, Why Now /h3 pbwe operationalise intelligence. /b AI does not replace humans. It repositions us to a place no system can follow: understanding, deciding, designing, and creating. At Keyrus, you will not just develop skills
- you will develop judgment. Your expertise sharpens with every system you architect, every client challenge you solve, every deployment that compounds on the last. /p h3Why Keyrus, Why Now /h3 pbKeyrus /b is an international group of b2,800 consultants /b and experts across b28 countries /b, built on a single conviction: bAI does not transform businesses. Architected intelligence does. /b For more than 30 years, we have been building the data foundations that make intelligent systems work — designing the Operating System of the intelligent enterprise, where intelligence is embedded into the core of business processes to create sustainable value: bwe operationalise intelligence. /b AI does not replace humans. It repositions us to a place no system can follow: understanding, deciding, designing, and creating. At Keyrus, you will not just develop skills
- you will develop judgment. Your expertise sharpens with every system you architect, every client challenge you solve, every deployment that compounds on the last. Over time, you grow into one of the rarest professionals of the intelligence era: someone who bridges data, AI, and human decision‑making at scale, across industries and geographies. This is not a role you fill. It is a discipline you master and a story you help write to become ba Keyrus Architect of Intelligence. /b Technology amplifies. bKeyrus culture differentiates. /b Industrial discipline connects the two. /p h3What You'll Architect /h3 pAs an AI Foundation Architect, you will define the technical architecture that enables production AI and agentic systems to operate reliably at enterprise scale. You will define how models, agents, data, applications, APIs, cloud services, security controls, and operational capabilities fit together, and set the architecture principles and boundaries that guide AI Engineers, Software Engineers, Data Engineers, and other technical teams. Within your assigned architecture scope, you are accountable for the integrity of the target design. Depending on the engagement, this may include formal design approval; explicitly define broader enterprise governance authority rather than assume it. Your primary focus is client‑facing architecture and technical design. You will also turn successful approaches into reusable Keyrus architecture patterns and standards without automatically owning an internal platform product or roadmap. /p h3Your Responsibilities /h3 ul liDefine target architectures for production GenAI and agentic systems, connecting models, agents, enterprise data, applications, APIs, cloud infrastructure, security, and operational services. /li liEstablish architecture principles, reference patterns, technical boundaries, and non‑functional requirements that engineering and delivery teams can apply consistently. /li liMake and document material architecture decisions across platform selection, model access, integration patterns, agent execution, data access, deployment, scalability, resilience, observability, and architecture‑level cost. /li liReview solution and engineering designs for architectural integrity, approving material design decisions within the assigned scope where the role has been designated as the architecture authority. /li liDesign secure, scalable, and operable foundations for intelligent systems, ensuring that reliability, identity, access, auditability, recovery, maintainability, and human‑control requirements are considered from the start. /li liGuide specialist engineering teams without replacing their ownership, working with AI Engineers, Software Engineers, Data Engineers, Governance specialists, and delivery teams on decisions that cross technical domains. /li liEngage with client architecture and technical stakeholders, explaining architecture choices, dependencies, risks, trade‑offs, and required decisions in clear technical and business terms. /li liConvert successful architecture decisions into reusable Keyrus assets, including reference architectures, decision records, standards, patterns, and design guidance that can strengthen future engagements. /li liArchitecture‑level AI FinOps, including model/provider routing, consumption patterns, capacity decisions, and cost optimisation. /li /ul h3Who You Are /h3 pYou are an experienced technical architect who combines strategic architecture judgment with recent practical understanding of production AI systems. You can move between the complete system and its individual components without trying to become the implementation owner for every layer, and you know when an architecture decision requires depth and when it requires coordination across specialists. You remain close enough to modern GenAI and agentic engineering to understand how these systems