Careers
Small team, real restaurants
We build the software a restaurant runs its day on — the till, the kitchen screen, the booking diary and the storefront. It is a small team, so what you build is what ships.
How we work
Built from three points of view
The pass, the code, and the phone call when something goes wrong. Everyone here spends time in all three.
The job
What working here is like
Everything below is checkable — it describes how the work is shaped, not what we would like you to believe about it.
Four things that are true
- One team, one product, no handover queue
- You own a feature from the API to the screen
- Decisions are written down before they are built
- Small enough that your work is visible
A small team
A handful of people build the whole platform. Nothing you write disappears into somebody else's queue.
One product, many surfaces
An API, a customer site, a seller dashboard, a till, a kitchen screen and three mobile apps. You will touch more than one of them.
Room to learn
The stack is wide on purpose — PHP, TypeScript and Dart in the same week. Nobody arrives knowing all of it.
You answer for what you build
Questions about a feature reach whoever wrote it. It is the fastest way to find out whether a design was any good.
Reasoning is written down
Architecture decisions live in the repository with the argument that produced them. You can read why before you ask.
Early enough to shape it
The platform has not launched to the public yet. What ships in the first year is still being argued about.
Open roles
What we are hiring for
Every role we are recruiting for is listed here. Nothing is posted to collect applications for a job that does not exist.