Small team, unusually deep problems
We are not running a formal hiring pipeline yet. We are, however, always glad to hear from people who find this kind of work interesting.
What the work actually is
Industrial software sits in an unusual place. It has the correctness requirements of systems programming, the interaction design problems of a consumer app, and a deployment environment where the network drops for six hours and nobody is on site to restart anything.
On any given week the work might be a protocol state machine, a rendering path that has to stay smooth with a thousand live bindings, a historian write path, or a 3D scene graph bound to real-time data.
The kinds of people we want to hear from
- Backend / systems engineers who are comfortable in Go and think carefully about failure modes, buffering and back-pressure.
- Frontend engineers who care about performance under load — high-frequency data on screen is a different discipline from a marketing page.
- Controls and automation engineers who have commissioned real systems and are tired of the tooling. You do not need to be a software engineer to help us build the right thing.
How we work
Small team, direct communication, no layers between the person writing the code and the person running the plant. Design partners talk to engineers rather than to an account manager, and engineers are expected to have opinions about the product rather than just the ticket.
No formal openings right now
We would rather be honest than list roles we cannot fill yet. If the work sounds like yours, send us something you have built or a note about what you would want to work on. We read all of it.