Design Engineer

Valthos Inc.

Valthos is an applied biological intelligence company. We build and deploy software and biological AI systems to safeguard humanity.

The same AI architectures that enable self-driving cars, land rockets with precision, and deliver expert-level reasoning are beginning to be deployed in biological design. To stay ahead, we must advance our arsenal of tools to capture and design against real-time sensitivities in nature's evolving mutational landscape.

We are a group of mission-driven software engineers from Palantir and applied biological ML engineers from MIT's Broad Institute and DeepMind making the latest advances in computational biology accessible in the real-world for federal and commercial use.

Finding a biological signal is only half the job. The other half is helping someone understand it, decide whether to trust it, and know what to do next.

Valthos users are trying to recognize biological threats, protect people, and make decisions before the picture is complete. The work is full of uncertainty, competing evidence, and unfamiliar technical detail. They need to move from raw data to an answer they can defend: what changed, why it matters, how strongly the evidence supports the conclusion, what remains uncertain, and what to do next. Design at Valthos makes that path clear without flattening the science or pretending the uncertainty is not there.

A design engineer at Valthos helps define how the platform works and feels from the ground up. The work spans product design and frontend engineering and requires direct collaboration with computational biologists, engineers, business development, and users on workflows that are still rough or only partly understood. A project may begin with a sketch, move into a coded prototype, and end as production software tested against how people actually work. There is no handoff between design and engineering; the role owns the path from idea to working product.

The person who thrives here has strong taste but is not precious about process. They are curious enough to learn a hard domain, technical enough to carry an idea into production, and thoughtful enough to simplify without hiding what matters. They notice when a chart is technically correct but misleading, when a workflow asks too much of the user, or when a polished screen still has not earned trust. They care about the details because, in this product, the details affect whether the answer is useful.

This role carries genuine ownership over the product’s visual language, interaction patterns, and design foundations. It is an opportunity to build serious software for serious work—and make it genuinely good to use.

The Role

• Own the design and frontend implementation of core product experiences, from early user flows and prototypes through production-ready interfaces