Work on a foundation that can compound.
The durable advantage is not a one-off prediction. It is infrastructure that makes biological information more useful as research advances.
We are an early team working across the life sciences, machine learning, data, and product. The problem is hard enough to require deep specialists — and connected enough to reward people who cross boundaries.
We want to build a consequential company without confusing a compelling demo for evidence.
The durable advantage is not a one-off prediction. It is infrastructure that makes biological information more useful as research advances.
Product work here means shaping how scientists and models share state, compare evidence, resolve uncertainty, and decide what deserves the next expensive step.
We distinguish implemented capability, planned architecture, computational hypothesis, and experimental proof. That precision is part of the product.
At this stage, research choices affect product choices, and product choices affect the company. People here have a real hand in all three.
Titles are starting points. We care more about the problem you can own, the evidence you use, and the quality of judgment you bring.
The immediate priority is product strategy: turning a deep technical direction into a focused sequence of users, decisions, and proof. We are also building the research and model layers around it.
Own the research-to-product thesis, user discovery, programme sequencing, and the boundary between workflow, models, services, and partnerships. Strong writing and first-principles judgment matter more than a familiar playbook.
Work on typed research state, immutable lineage, model adapters, verification, artifact systems, and interfaces for human review. You should enjoy making complex workflows explicit and difficult to misuse.
Develop and evaluate biological models, design honest baselines, connect representations to measured outcomes, and make uncertainty visible. We value rigorous negative results and reproducibility as much as a new model idea.
We are open to experienced scientific, product, and company-building partners whose work is unusually aligned with this direction. We prefer substantive mutual diligence and a small piece of real work before deciding what form the relationship should take.
Computational biology, scientific operations, applied research, design, partnerships, safety, or another discipline we have not named — send the work that best shows how you think.
Define what has to be learned, which evidence would change the path, and where authority sits.
Encode inputs, constraints, provenance, and handoffs so another person can inspect the work.
Test baselines, failure modes, leakage, hidden assumptions, and where a score overreaches.
A result changes the next round without erasing the record of how the previous one was reached.
We keep the process compact and adapt it to the seniority and shape of the relationship.
A resume is useful; a piece of work, a sharp memo, or a short account of what draws you to the problem is better.
We compare how we see the market, the science, the missing evidence, and the most important next decision.
We use an existing problem or prior work, not generic puzzles. The point is to see how judgment travels between us.
Role, scope, location, and pace follow from the work. We make the mutual expectations explicit before either side commits.
Send a concise introduction and the strongest example of your work. If you are exploring a partnership rather than a role, say so plainly — both conversations are welcome.