Skip to content

Careers

No open roles right now.

That is the honest answer rather than a holding page. We are a small team, and when that changes this is where it will be posted first.

Nothing open — but we do read everything

If you are a Flutter or backend engineer who finds retail software more interesting than it sounds, write to us anyway. We would rather know you exist before we have a role than start looking from scratch.

What it is like

The work, honestly described

Useful to know now rather than in an interview — and all of it checkable against the product.

Flutter and TypeScript, end to end

One Flutter codebase across Android, iOS and web, and a Bun + Hono backend on Postgres. Small surface, high standards, no legacy to carry.

Hard problems, not big ones

Offline-first sync, idempotent payments, per-tenant theming, thermal printers. The difficulty is in getting them exactly right, not in scale.

Written down, and argued about

Decisions live in the repo with the reasoning attached, including the ones that turned out wrong. If you like knowing why the code is the way it is, you would like it here.