Distributed systems with a physical edge
Queues, leases, reconnection, idempotency, and job state meet USB devices, drivers, sleeping computers, and paper.
Careers
RocketPrint lives at an unusually honest boundary: APIs are deterministic; printers, drivers, networks, and warehouses are not. We build the infrastructure between them.
The work
A print job is a tiny request that can stop a packing line, duplicate a shipment, or expose customer data if the surrounding system is careless. That makes the details matter.
Queues, leases, reconnection, idempotency, and job state meet USB devices, drivers, sleeping computers, and paper.
We explain exactly what each state proves, where the boundary ends, and which features have not shipped yet.
RocketPrint Station has to feel ordinary on macOS, Windows, and Linux while handling decidedly unordinary printer behavior.
The API needs clean contracts; the console needs to make remote operational questions answerable without a terminal.
Open roles
When there is a specific role, it will appear on this page with the work, expectations, location, and compensation spelled out.
If RocketPrint is exactly the kind of problem you want to work on, you can still introduce yourself at hello@rocketprint.io. We read every note; we cannot promise a role.
See the product
Read the architecture and reliability pages to see how we think before you write.