Nory AI offers an AI-powered restaurant management platform that automates back-office tasks and optimizes labor, inventory, and profitability for restaurant operators.
Let's fix hospitality, for good. Hospitality is tough – margins are thin, waste is high, and teams are stretched. But it doesn't have to be this hard. That's why we built Nory. Our CEO, Conor, knows the pain first-hand. After founding and scaling Mad Egg in Ireland, he got fed up with juggling "market-leading" systems, clunky spreadsheets, and endless printouts. So he set out to build the tool he wished he'd had from day one. Nory is an all-knowing restaurant management system. It blends real-time data with AI predictive analytics, giving operators control of their margins. From food prep to forecasting, it's operational intelligence that helps restaurants run with consistency, certainty, and profit. The result? Thriving restaurants, better jobs, less waste, healthier margins. Learn more about what we are building here https://www.linkedin.com/feed/update/urn:li:activity:7414229365426790400/. And we're just getting started. Fresh off a Series B led by Kinnevik https://www.nory.ai/blog/nory-series-b-funding-to-revolutionise-restaurant-operations, we've grown to 100+ people across Ireland, the UK, Spain and recently, New York – and demand is scaling faster than we ever imagined. THE ROLE We're looking for a Staff Engineer to own the problems that actually move the business: the features and initiatives we're betting on, not just the ones that keep things running. This is a backend-leaning full-stack role. Your centre of gravity is backend systems, architecture, and complex product development, with the range to contribute across the stack and help lay the foundations of our AI-native platform. You won't just solve hard technical problems. You'll help decide which ones are worth solving, shape how we approach them, and bring others with you. Strong technical instincts and sharp product thinking both matter here in equal measure. You must have the right to work in the UK or the EU without sponsorship to be considered for this role. WHAT YOU'LL BE DOING: Our teams are cross-functional with clear ownership. You'll take on the highest-impact technical and product priorities: the ones driving ARR, shaping how we differentiate, and defining what Nory becomes over the next few years. - Own the hardest problems. The features and initiatives we're betting the business on, from problem framing through to execution and iteration. Not just the complex, but the consequential. - Work directly with operators and PMs to shape what gets built. You'll talk to restaurant operators, understand what's actually broken, and use that to change direction, not just validate what was already planned. - Shape direction, not just delivery. Define the technical approach, sequence the work, influence the roadmap. Your engineering judgment should change what gets built, not just how. - Drive cross-team alignment. Own initiatives that cut across squads. Make sure decisions account for system-wide impact, not local optimisation. - Make other engineers better. Through technical leadership, decision-making guidance, and clear communication, not just by doing the work yourself. - Improve the system, not just the feature. Spot the foundational gaps before they become incidents. Turn those observations into shipped improvements. WHAT YOU'LL BRING: - Real backend depth. You've built and owned production backend systems (APIs, data models, distributed services) that real customers depend on. You can describe specific data modelling decisions you made, the constraints you were navigating, and why you made the trade-offs you did. You designed for failure, not just the happy path. - Full-stack range. You've shipped end-to-end features and you're comfortable doing it again. - Product instinct, not just technical instinct. You've spoken directly to customers or operators and let that change what you built, not just validated what was already planned. You know which problem is worth solving, and you can point to a moment where your engineering judgment changed a product decision and what happened as a result. - Commercial outcomes, not just technical ones. You can connect your work to what actually mattered: features that drove revenue, changes that shifted how customers operated, initiatives that moved the business. Pure technical impact (reliability, latency, cost) isn't the bar on its own. - Systems thinking, not squad thinking. You've made architectural decisions with a long lens, balancing scalability, maintainability, and pragmatism. You find foundational gaps before they surface and build systems that let multiple teams move faster. - Outcomes, not tickets. You can point to things you personally shaped, not just delivered. You've pushed back when the problem wasn't right, proposed a different approach when the plan was wrong, and owned what came next. You say "I decided," not "we decided." - Built under real constraints. High-stakes initiative, greenfield system, zero-to-one inside a larger org. You've navigated genuine ambiguity, made calls without perfect information, and shipped something real. You know what an MVP actually means at initiative scope, not just feature scope. - Leverage, not just output. You don't just raise the bar, you pull people with you. Engineers work differently because of how you operate. You can describe something specific you put in place that others adopted. You write clearly, align across disciplines, and make decisions better for everyone in the room. Bonus points - Strong instincts around system-wide thinking: how architectural choices ripple into product velocity and org effectiveness - Mentored senior engineers or been the go-to technical leader for a broader group OUR STACK - Python, FastAPI, React, TypeScript, Node.js, AWS (Fargate, Aurora, SQS), Postgres, MongoDB, Docker. - We're stack-agnostic in our hiring and care most about strong engineering fundamentals and the ability to ramp quickly. WHAT YOU'LL GET IN RETURN: 🌎 Remote