INDEX / ABOUT / CAREERS

Small team, real bench time.

Twenty-one people build, measure, and service every instrument this company ships. When a role opens, it opens here with the honest version of the job attached, including the parts that are tedious. There is no ping-pong table and there is a thermal chamber you can put your lunch next to, which is a worse idea than it sounds.

01 Open roles

OPEN / DETROIT STUDIO

Assembly and QC technician

The job
Hand assembly, panel fitting, and the QC pass: every module you build gets its own measurement certificate, signed by you
You bring
Soldering discipline, patience with a torque driver, and the willingness to reject your own work when the rig says to
We provide
Training on the rig, a bench of your own, and a say in the batch sheet that goes out with your serials
Honest part
Repetition. The tenth HELIOS-8 of a batch is the same as the first, and the certificate does not care how you feel about that
Apply
front@ address, subject BENCH, with anything you have built or measured

OPEN / BERLIN STUDIO / REMOTE-FRIENDLY

Firmware contributor track

The job
A paid, part-time track for community contributors who want to maintain the subsystem they know best
You bring
A merged contribution or a convincing argument in the repository history
We provide
A development HELIOS-8, direct bench access by appointment, and your name in the release receipts you shape
Honest part
Reviews here are slow on purpose. Eleven months of argument shipped a better skip engine; that pace is a feature
Apply
bench@ address, subject CONTRIBUTOR, with the patch or the argument

CLOSED / FILLED OCTOBER 2026

Service technician, Berlin

Filled by internal move. Listed here because a careers page that only shows wins is a brochure, not a record. The next service opening will be posted the week it opens.

02 How we work

BENCH TIME

Every engineer, including the founders, takes a bench day each week. The person writing the filter code has soldered the filter and measured it, which is why the code comments read like they were written by someone who was there.

PUBLISHED DISAGREEMENTS

Technical arguments happen in the open, in the repository and the community threads, and the losing side is named with respect. The skip engine note is the canonical example.

NO CRUNCH

Batch dates are printed and therefore real, which is exactly why they are conservative. A batch that slips a week slips with a note. A team that burned out to hide a slip would be a team you could not trust with a measurement.