A restaurant signs about a hundred agreements. Nobody checks them.
The lease, the linen contract, vendor prices, delivery deals. They all live in one place, the owner's head. Nobody checks that the money moving through the bank matches what was signed, so it leaks, and when it gets found, it gets found by chance.
Big chains pay a person whose whole job is catching this. We're building that person, and that's the job you'd be doing.
The role
Founding engineer
Let me be straight with you: there is no salary yet, and I won't dress that up. What there is: an ownership stake that vests over time, on paper before you write a line of code, and a real product inside real restaurants. That's the risk I'm offering.
- Read a working codebase and start shipping into it.
TypeScript,Next.js,Supabase. - Write the checks that catch real problems: a vendor price that went up without notice, a deposit that never landed, a delivery fee that stopped matching the deal.
- Ship to restaurant owners who will tell you within a day if you got it wrong.
Who you'd work with
A restaurant kid, not an engineer. I built this with the tools we have today, and there are 10,371 automated tests on it.
Former COO of The Halal Guys, CEO of Asian Box, VP at Qdoba. Thirty years running restaurants at scale. The product gets built to his standard.
Apply
Tell me who you are.
Name, email, and a couple of sentences is enough. A resume is optional, and a link to something you built says more than one anyway.