> Markdown version of [/jobs/ext/2175886-software-engineer-live-ai-platform](https://www.wearedevelopers.com/jobs/ext/2175886-software-engineer-live-ai-platform). 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). --- # Software Engineer - Live AI Platform - **Company:** Ellison Institute, LLC - **Location:** Oxford, UK - **Salary:** £68,595.0 - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Computational Biology, Human-Computer Interaction, Systems Architecture, AI Platforms - **Published:** August 22, 2026 - **Apply:** https://www.adzuna.co.uk/jobs/details/5851365509 ## About the Role * A strong plus: direct life-science or lab experience - for example in protein design, computational biology, bioinformatics, or building tools alongside bench scientists. * Building the internal tooling and standards that let a team work with coding agents well - not just doing it yourself. * Scientific visualisation - 3D molecular structure, large result sets, comparison and triage interfaces. * Experience as an engineering lead or manager who has chosen to come back to building. We'd want to talk about why. ## Description Within EIT's AI and Robotics team, we believe powerful AI and increasingly capable robotics will meaningfully accelerate science discovery. We are building a platform to empower scientists to move from a question, to a designed experiment, to a result on the bench-without having to do the plumbing themselves. This is an undefined product category. You will be part of the founding team to shape the product and the architecture. To begin with, you'd be building for EIT's own scientists, in the same institute. They're a short walk from your desk, not behind an account manager or a research panel. You'll own the system architecture from model endpoint to interface. We build prototypes to learn from, and we're willing to throw them away. What comes next depends on what that pilot teaches us, and you'll have a large hand in deciding it. This role starts as an individual contributor, with the opportunity to build a team over time. You become the technical anchor for how AI models reach the scientists who need them - the person who owns that seam and establishes the technical approach. Requirements Day-to-Day, You Will * Build an agentic workflow for scientists end to end, from model endpoints to the user interface. There is nobody to hand a ticket to at the beginning. * Build and operate the technical foundations for agentic systems, including orchestration, tool interfaces, state management, evaluation, observability and failure recovery. * Design evaluative frameworks to understand if the deployed model is working * Work directly with scientists, observe how they operate and translate what you learn into clear engineering priorities. * Synthesise the knowledge from individual workflows to build generalisable capability * Partner with product, data and research to shape the roadmap and ship at speed in an emerging category where the most impactful problems remain unsolved. What We're Looking For * You've built and shipped systems from scratch as a core engineer and independent contributor or have created something new and standalone inside a larger organisation. You can turn an open-ended problem into a clear technical strategy and working software. * You've built agentic AI products, not just used them. You understand orchestration, tool use, human-in-the-loop review and evaluation, and have dealt with agents and their typical failure modes. * You've designed and built production-ready systems. You can make sound decisions about APIs, data models, testing, deployment, observability and failure recovery. * You've built policy-aware systems with durable audit trails. Constraints are enforced by design, and every decision leaves a trustworthy, queryable record. * You are full-stack and self-sufficient. You can take a system from model endpoint to production interface without waiting for someone else to fill the gaps. * You can create clarity from ambiguity. You are comfortable setting technical direction and making trade-offs between what is technically elegant and what users need for adoption. ## Related Videos - [The AI-Ready Stack: Rethinking the Engineering Org of the Future](https://www.wearedevelopers.com/videos/1706-the-ai-ready-stack-rethinking-the-engineering-org-of-the-future) - [DOOM on Neurons, Training AI with Harry Potter & Robots Watching YouTube - Zoran Jambor](https://www.wearedevelopers.com/videos/1823-doom-on-neurons-training-ai-with-harry-potter-robots-watching-youtube-zoran-jambor) - [The QUEST for Better Software](https://www.wearedevelopers.com/videos/721-the-quest-for-better-software) - [This App Reached 10,000 Users in One Week. Here's How.](https://www.wearedevelopers.com/videos/100329-this-app-reached-10-000-users-in-one-week-here-s-how) - [Developer Experience, Platform Engineering and AI powered Apps](https://www.wearedevelopers.com/videos/990-developer-experience-platform-engineering-and-ai-powered-apps) - [The Future of Computing: AI Technologies in the Exascale Era](https://www.wearedevelopers.com/videos/1106-the-future-of-computing-ai-technologies-in-the-exascale-era) ## 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) - [MLOps And AI Driven Development](https://www.wearedevelopers.com/magazine/82-mlops-and-ai-driven-development) - [Dev Digest 137 - AI'm not sure about this](https://www.wearedevelopers.com/magazine/485-dev-digest-137-ai-m-not-sure-about-this) - [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 is Agentic Programming and Why Should Developers Care?](https://www.wearedevelopers.com/magazine/625-what-is-agentic-programming-and-why-should-developers-care)