Operations research in real software
Systems that run e-SAF, e-methanol and e-hydrogen plants and ports, and internal systems with operations research built in. You model the problem and build the software people use every day.
Decision systemsWorking here
We are about 50 people in around 20 countries, remote-first, and ten years into it. We hire senior engineers and give them whole problems, from the first conversation to running software. Most of our clients are in the USA.
Who the work suits
-
Seniority and judgement
You take a messy problem, work out what matters and own the result.
-
Depth in a discipline
You go deep in one of operations research, applied AI, formal methods or product engineering.
-
You write it down
You put your thinking in writing and publish it under your own name.
What would be on your desk
Large systems for known clients
We built and ran nine internal systems for Livesport, which more than 100 million people use. Clients include Guaranteed Rate, Reify Health and Alza. And Gitrevio is our own product.
The workOur own theorem prover
Rainbow is our theorem prover in Clojure. It has kernel-checked theorems about all 222 catalogued operations-research algorithms, and its open core is on GitHub. Rainbow Pro generates certified code from a specification.
RainbowThe shape of the job
You lead your part of the work.
You decide how to solve the problems in your area, and you stay with the system after it goes live.
We work across time zones, so we write things down. We use AI every day, and with it our team does the work of 30 to 40 extra PhD-level people. In research roles you publish under your own name.
Teams are small, usually four or five people. You can see every role in how we work.
How we hire
No puzzles. The whole process takes two to three weeks.
-
Introduction
Tell us what you are good at and what you want to work on.
-
Conversation
A senior person talks through your experience and how you weigh trade-offs. Ask us anything.
-
Real problem
We spend a couple of hours on a problem together, close to the work we do.
-
Decision
You get a clear yes or no, with the reason.
Introduce yourself any time
Open roles appear on this page. You don't have to wait for one.
Read us before you apply
The engineering handbook has the standards you'd work to. The engineering archive shows what we publish under our own names.
Tell us what you do well
A short introduction is enough. A senior person replies within the week.