Staff Engineer

Help make the world more hospitable The hospitality industry is uniquely human, and it deserves technology that’s just as inspiring as the people behind it. At Mews, we’re transforming the industry with a platform that helps hotels run smarter, move faster and create better guest experiences. You’ll work with smart, curious people who care deeply about what they do. You’ll have autonomy and the trust to make good decisions and move quickly. And you’ll enjoy a real sense of purpose as you see the impact of what we’re building. If you’re motivated by ownership, curiosity and meaningful impact, and are driven to deliver consistent high performance, you’ll feel at home here. About the role Let's get into the specifics. It’s impossible to capture every nuance of a role – especially at a rapidly growing company like Mews – but if we had to distil it into a job description (which we do because this is a job description), it would be this: As Staff Engineer, you'll own the architecture, agents and skills that let every builder in your tribe ship sound, well-architected work without waiting on a handoff, at a moment when Mews has moved almost entirely to an agentic-first engineering model. The problem this role exists to solve is easy to state and hard to do: most technical decisions now get made by builders and the agents they run, not by senior engineers in review, so the standard has to be built into the tooling itself or the gaps show up in what customers touch. Mews is rebuilding hospitality software from the ground up at a genuinely unusual pace, which makes this one of the few staff engineering roles where the leverage you build gets used by everyone around you within weeks. You'll be attached to one tribe, reporting into its Director, and working alongside other staff engineers, staff product managers and staff designers across your division. Your job isn't to ship features. It's to produce the architecture, agents and skills that give every builder in the tribe the context to make sound calls on their own, and to stay hands-on with the hardest problems yourself: the gnarly migrations and system-wide refactors that need an approach invented rather than executed. As Mews moves builders to own a sub-metric end-to-end, with AI covering what they're lighter in, the risk isn't slower shipping, it's the architecture fragmenting underneath the speed. This role exists so the foundations get stronger as the tribe ships faster, not shakier. What you would do • Own the tribe's engineering context, agents and skills, and be accountable for keeping them coherent, current and grounded in real product work • Build and evaluate the internal engineering agents and skills that Product Builders use daily, encoding architectural standards, review logic and quality gates directly into the tools they run • Extend and improve the tribe's agentic tooling when it isn't good enough yet, since agentic development is the default way you build, not a fallback • Stay hands-on with the hardest technical problems: gnarly migrations, system-wide refactors and architecture calls that will shape years of future building • When work ships off-bar, trace it back to what was missing in the agents or patterns and fix it at the root so the same class of miss doesn't recur AI Fluency Level 4: in this role that means building and shipping the engineering agents and skills that Product Builders rely on every day, not just using AI tools yourself. You need enough understanding of the underlying models and infrastructure to make real engineering decisions about them, because the agents you build become part of the tribe's production system. For more information on AI fluency at Mews, please refer to " AI Fluency at Mews: A Comprehensive Guide for Candidates "