Build the future of restaurants.

At most companies, a customer problem passes from a product manager to a designer to an engineer, and context disappears at every handoff. We don’t work that way. In this role you own the entire loop: understand the problem, define what should exist, decide the fastest credible path to it, build it end to end, put it in front of customers, and change the plan when reality proves you wrong. You’ll work directly with restaurant operators and carry important problems across requirements, UX, frontend, backend, data, deployment, and post-launch outcomes. “Product” means you can go from a messy customer problem to clear requirements and an opinionated ideal solution. “Engineer” means you can reason from the problem into the systems required to solve it, and use coding agents aggressively without outsourcing judgment to them. This is not a frontend engineer with good taste, and it is not a product manager who can code — it is both disciplines practiced as one job.

• Start with restaurant operators, understand the problem beneath what they ask for, and turn it into clear requirements
• Define the ideal experience and decide what the first version must prove
• Build the highest-priority products end to end, wherever the company and its customers need you most
• Use taste and judgment to simplify complexity for people who don’t think about software all day
• Ship quickly without confusing speed with sloppiness — build durable foundations where failure has real consequences, take shortcuts where learning matters more than polish
• Watch customers use what you built and update both the product and the plan — a feature being deployed is not the same as a problem being solved

You will own our complete restaurant management system across procurement, labor, and food cost. Your responsibility spans product decisions, architecture, code, production behavior, and customer outcomes — not one feature, service, or team. The scope combines traditional software that must be exceptionally dependable with agentic systems that can safely act in the physical world. If the system fails, restaurants lose money, waste food, or fail to serve customers. Knowing when good enough is good enough — and when only excellent is acceptable — is the job. This is an unreasonable amount of scope for an average engineer. We are not hiring an average engineer.

• Build the core platform behind procurement, labor, and food cost, with an early focus on bill pay, bookkeeping, and labor scheduling
• Move Patty from intelligence to execution so she does real work for restaurants — placing vendor orders, creating new offers, scheduling labor — not just telling people what to do
• Invent a new kind of adaptive restaurant software that lets restaurants modify their own software to fit their operation — think an extremely opinionated Lovable or Claude Code, with guardrails
• Own the hardest product and technical decisions from customer problem to production, working directly with restaurant operators and writing critical code yourself
• Set the technical standard and help build the engineering team around it

You’ll be the single point of accountability for a restaurant group’s results. Not check-ins and status updates — you own the targets. That means understanding the customer’s operations deeply enough to know which decisions carry real risk, which ones move the numbers, and what needs to get built to close the gap. You’ll work closely with our forward deployed engineers to prioritize and ship against the customer’s biggest pain points, and you’ll be expected to ship code yourself when the situation calls for it. Think of this as a portfolio manager role — you’re managing a set of outcomes across a complex, dynamic operation.

• Own the relationship and the results for one or more restaurant groups
• Identify the highest-leverage pain points and turn them into product priorities
• Assess risk on key operational decisions and guide customers through them
• Work with forward deployed engineers to ship fixes and features against real customer needs
• Ship code yourself when a customer problem needs a fast response
• Shape the product roadmap from the ground — no one will know what customers need better than you