Since the 1990s, we've been promised a bio-revolution—cell therapies that reprogram immune systems to hunt cancer, and gene therapies that make the blind see. But the bottleneck isn't discovery; it's the brutal, decade-long journey from the lab to the patient. We are building the operating system to destroy that bottleneck.
To be clear: this is not a drug discovery sandbox. Our software governs GxP data, automates complex clinical workflows, and produces the verifiable audit trails regulators require. Our users are manufacturing real, physical therapies that save lives, and they run their production on our code. The stakes are real, and we need serious, hardcore engineers to build the infrastructure they rely on. You can read our full mission here.
You will own critical parts of this platform: the automation engine, AI interfaces, and the low-level data primitives that underpin everything. Building a true platform rather than a fixed product is a profoundly difficult engineering challenge—every feature requires an extra layer of abstraction to allow for infinite customizability.
The platform is written in TypeScript and built from the ground up for AI. It functions almost like a developer platform for our customers. Everything is version-controlled, and configurations are grouped into "change sets" that act exactly like pull requests for scientific processes. This strict, code-like architecture is what makes AI uniquely powerful on Seal. Right now, our primary AI use case is acting as a hyper-competent co-pilot that makes it radically fast for users to compose, deploy, and continuously evolve their own custom operating systems within Seal. Our next frontier is putting AI directly into the runtime workflow—giving scientists intelligent agents that can reason over the vast amounts of proprietary data the operating system captures to make decisions, flag risks, and accelerate production.
We are a tiny team with an extremely high bar. We care deeply about every detail of what we build, and we expect you to do the same. We don't do tickets. Each week we sit down together, argue hard about priorities, and each engineer takes full ownership of one problem—writing the spec, making the architectural decisions, and shipping the code.
There is no customer success layer. Engineers talk to customers directly, run an on-call rota covering US timezones, and travel onsite for the ones that matter—wherever in the world that is. You will be the person who hears when something breaks. That is the point.
This demands someone pathologically obsessed with product and user experience. You must be a first-principles thinker who can hold the aesthetic of a UI in your head while architecting the primitives that power it. Your raw intelligence and work ethic matter far more than the specific languages you know.
This is an in-person role in London. We sponsor visas for the right person.
The challenge is immense and the standards are absolute. We are looking for people who are compelled by this, not intimidated. If you are one of them, join us.