> Markdown version of [/jobs/ext/2311122-ai-delivery-architect](https://www.wearedevelopers.com/jobs/ext/2311122-ai-delivery-architect). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # AI Delivery Architect - **Company:** lumo. - **Location:** Greater London, UK - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Amazon Web Services, Cloud Computing, Continuous Integration, Data Infrastructure, Extract Transform Load (ETL), Cursor (Graphical User Interface Elements), Systems Development Life Cycle, Software Engineering, Large Language Models, Backend, Front End Software Development, Terraform - **Published:** August 30, 2026 - **Apply:** https://www.collegerecruiter.com/job/2815458801-ai-delivery-architect ## About the Role First, the most important thing: this role is built around a strong, experienced engineer-turned-architect - someone with real delivery behind them and the credibility that comes with it. You do not need to be an AI expert today. If you have deep AI tooling experience, brilliant. If you don't, but you have the engineering depth and a genuine track record of learning fast, we will back you to pick it up here. The experience is the hard part; the AI we can teach., * A strong engineering background, with a backend bias. You came up building production systems - services, data, integration - and you have a deep appreciation for how technology actually gets delivered. * A move into architecture, while staying hands-on. You took on architecture and led deliveries, but you never stopped building. You are not a diagrams-only architect. * A track record of learning and adapting. This matters most. You can point to times you picked up an unfamiliar stack, tool, or way of working and shipped with it. You are self-sufficient and you thrive in new delivery methods rather than waiting to be shown. * Credibility with technical leaders. You have led delivery and can hold your own in a room with a client's senior engineers - advising, challenging, and being trusted. * Comfortable working directly with clients. You can run a working session, explain progress and trade-offs clearly, raise risks early, and adjust register for technical and non-technical audiences. * Enough breadth to use AI across the stack. You don't need to be a specialist front-end engineer or platform engineer, but you understand front-end, IaC, and the broader stack well enough to direct AI tooling across them confidently. * London-based and happy with hybrid working and occasional travel to client sites., We would love someone who already lives in AI tooling - but we know that person is rare. If you bring the engineering experience, the architecture judgement, and the track record of adapting, we will back you to pick up the AI side fast. So these are a bonus, not a barrier ## Description * Work with client teams. Sit alongside our clients' engineers, architects, and product leads to understand how they deliver today and where AI changes the picture. Run working sessions, advise on practice and tooling, and translate the work for technical and non-technical stakeholders without losing precision. * Help evolve their AI SDLC. Shape how AI tooling fits into a client's delivery lifecycle - design, build, review, test, release. Recommend where to lean in, where to be cautious, and what good looks like, then help them adopt it. * Stay hands-on with AI. Show, don't just tell. Use Claude Code, Devin, Cursor/Windsurf, and agentic workflows as a force multiplier. Know what to delegate to agents, what to keep yourself, what to put behind an eval, and what to throw away. * Set credible technical direction. Bring architecture judgement built on real delivery - sensible system design, integration patterns, and trade-offs that hold up in production, not just on a slide. * Partner with the Lumo delivery team. Work with our delivery lead and the wider team to scope engagements, raise risks early, and keep things moving. We are a start-up, so the shape of the team is still forming - you are comfortable with that., * Daily, sophisticated use of AI coding tools (Claude Code, Devin, Cursor/Windsurf, Copilot) with informed views on where each earns its keep. * LLM application engineering - agent orchestration, RAG, structured outputs, evals. * Prior consultancy or client-facing delivery experience. * Cloud and data infrastructure depth (GCP/AWS, Terraform, CI/CD, warehouses, ETL). * Front-end or IaC delivery experience to complement the backend core., You like being the person clients trust to tell them the truth about how to build better - and then to roll up your sleeves and show them. You would rather learn a new tool and ship with it than defend the way you have always worked. And you are energised, not unsettled, by a start-up where the role will keep changing as AI delivery itself changes., * AI-native delivery is the default. We are a small senior team because we orchestrate AI tooling well. If you would rather pretend that isn't happening, this isn't the place. * Honest, not over-sold. Our client posture is candid. We flag risk, recommend gates, and prefer documentation and handover over perpetual retainer. You'll be expected to do the same. * Fast paced. Change is relentless. Roles, teams, and methods are evolving - that is the opportunity, and it is why self-sufficiency matters so much. ## Related Videos - [Reference Architecture of AI in the Cloud](https://www.wearedevelopers.com/videos/1613-reference-architecture-of-ai-in-the-cloud) - [Developing the Backend with Stefan Lingler, CTO at Shpock](https://www.wearedevelopers.com/videos/100360-developing-the-backend-with-stefan-lingler-cto-at-shpock) - [Infrastructure as Code: The Developer's Secret Weapon](https://www.wearedevelopers.com/videos/1221-infrastructure-as-code-the-developer-s-secret-weapon) - [Green Cloud Computing](https://www.wearedevelopers.com/videos/592-green-cloud-computing) - [AI-Enabled Organisations: From Strategy to Practice](https://www.wearedevelopers.com/videos/100171-ai-enabled-organisations-from-strategy-to-practice) - [Nest.js - TypeScript in the backend can also be clean](https://www.wearedevelopers.com/videos/1033-nest-js-typescript-in-the-backend-can-also-be-clean) ## Related Articles - [How to Become an AI Engineer](https://www.wearedevelopers.com/magazine/331-how-to-become-an-ai-engineer) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [What is Software Engineering in the Age of AI?](https://www.wearedevelopers.com/magazine/640-what-is-software-engineering-in-the-age-of-ai) - [What Industries Outside of AI Are Hiring The Most AI Experts?](https://www.wearedevelopers.com/magazine/98-what-industries-outside-of-ai-are-hiring-the-most-ai-experts) - [Transforming Software Development: The Role of AI and Developer Tools](https://www.wearedevelopers.com/magazine/527-transforming-software-development-the-role-of-ai-and-developer-tools) - [MLOps And AI Driven Development](https://www.wearedevelopers.com/magazine/82-mlops-and-ai-driven-development)