Small team, real systems, no layers

What working here is like

Our software runs a logistics operation. When something breaks, trucks and shipments are affected — which means the feedback loop is short and the work is concrete. You will see the consequences of your decisions within days, not quarters.

There is no layer between engineers and the people doing the work. You will spend time in warehouses and with dispatchers, because that is how you learn what to build.

What we look for

• You can take a vague problem and turn it into something shipped
• You are comfortable across the stack, or willing to become so
• You would rather ask an operator a question than guess at a requirement
• You care whether the thing actually gets used