Staff Engineer
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" on Confluence.
What you would bring
A track record as a senior or staff-level engineer who has shipped and owned complex systems at scale, not just contributed to them
Experience turning hard-won technical judgment into reusable architecture, tooling or standards that other engineers actually adopt, rather than documentation that goes unused
Comfort holding a multi-cycle technical view (migrations, refactors, architecture decisions that play out over years) while still being able to drop into what needs to ship today
Clear communication across levels: builders, your Director, Principals and, when it counts, the C-suite
AI Fluency Level 4 or the equivalent hands-on experience: you've shipped something where AI is a core component and can make engineering decisions about the underlying models and infrastructure
Nice to have
Experience in hospitality, travel or another operationally complex B2B SaaS environment
A track record of coaching or multiplying other engineers' output, not just your own
Public writing or speaking about technical work you've shipped
Spain
€79.500—€100.500 EUR
Czechia
1 491 000 Kč—2 005 000 Kč CZK
UK
£81,000—£106,500 GBP
Ireland
€91.000—€107.000 EUR