<div class="show-more-less-html__markup show-more-less-html__markup--clamp-after-5 relative overflow-hidden"> <p>We are building gastropilot.ai to become the operating intelligence layer for independent hospitality.</p><p><br/></p><p>Restaurants already have the data required to make better decisions. The problem is that it is fragmented, inconsistent and trapped across POS systems, invoices, spreadsheets, recipes, inventory counts and human memory.</p><p><br/></p><p>gastropilot.ai turns this chaos into operational action. Not another dashboard, but a system that understands what happened, predicts what is likely next and tells the team what to do about it.</p><p><br/></p><p>The product foundation exists and the first pilot restaurants are entering onboarding. Now we are looking for the person who wants to build the intelligence behind it.</p><p><br/></p><p>What you will build</p><p>You will own the technical evolution of the AI and data layer.</p><p>• Demand forecasting</p><p>• Anomaly and waste detection</p><p>• Recipe and product matching</p><p>• Supplier-item normalisation</p><p>• Recommendation systems</p><p>• Operational decision engines</p><p>• LLM and agent workflows</p><p>• Evaluation and reliability</p><p>• Extraction from invoices, exports and unstructured documents</p><p>• Learning across restaurants without exposing sensitive business data</p><p><br/></p><p>The data will not be clean</p><p>Product names will differ between suppliers, receipts and recipes. Units will be inconsistent. Historical information will be incomplete. That is the actual problem.</p><p><br/></p><p>You are the right fit if</p><p>• You are strong in Python, SQL and production systems, not just notebooks</p><p>• You have shipped applied ML in production: forecasting, recommendations, anomaly detection, LLM systems or data infrastructure</p><p>• You know exactly what separates a model that performs in a notebook from a product people rely on every day</p><p>• You ship pragmatically and build defensible technical advantage over time</p><p>• You care about the user's problem, not only the model's accuracy</p><p>• You want ownership over architecture, product decisions and technical direction</p><p>• You are comfortable joining before a large team, perfect documentation or a predictable roadmap</p><p>• You have real, shipped systems to show, not side projects that never left your laptop</p><p><br/></p><p>What already exists</p><p>You will not start from a blank document. You will decide what should be kept, rebuilt or removed.</p><p>• A working operational loop across recipes, purchasing, inventory, sales and actions</p><p>• PostgreSQL and Redis infrastructure</p><p>• Role-based product flows</p><p>• Real hospitality use cases</p><p>• Initial pilot restaurants</p><p>• A growing backlog of real operational data problems</p><p>• An existing Python-based application stack</p><p><br/></p><p>The setup</p><p>We start with a three-month founder trial.</p><p>Equity will be formally documented upon incorporation and governed by a founder agreement, vesting and a cliff.</p><p>For the right person, this is a genuine Technical Co-Founder path with meaningful ownership—not a symbolic employee option package.</p><p><br/></p><p>Apply</p><p>Do not send a generic CV. Send us:</p><p>• A product or system you have shipped</p><p>• The hardest technical or product decision you made while building it</p><p>• An example of working with incomplete or messy data</p><p>• What gastropilot.ai should build first to create a defensible advantage</p><p>• GitHub, LinkedIn, portfolio or relevant work</p><p>• Your availability and current location</p><p><br/></p><p>We are not looking for someone who wants to add AI to a restaurant dashboard. We are looking for someone who wants to build the intelligence system hospitality will run on.</p> </div>