Staff Product Manager

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.

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:

The Guest Revenue tribe owns the products that help hotels earn more from every guest interaction: our booking engine, upselling tools, ancillary revenue features, and the guest recognition layer that makes personalization possible. You'll sit directly alongside Diana Arizmendi (Director of Product and Engineering) as her right hand on the tribe's hardest product problems: improving upsell attach rates (currently ~2%), scaling guest recognition, and shipping the Reputation Manager into GA. You won't be running discovery yourself for every feature — instead, you'll own the tribe's product context and encode your product judgment into the agents, evals, and shared systems that the Product Builders draw on autonomously. When the system doesn't produce the right output, you fix it at the root. When the tribe faces a genuinely ambiguous strategic bet, you own the answer.

• Own the product context your team builds from: the customer evidence, outcome definitions, prioritisation logic and decision history that makes every build decision faster and more grounded.
• Encode your product thinking into shared tools and systems so that good problem framing and rigorous discovery happen by default, not through constant oversight.
• Lead discovery on the team's hardest open questions, from improving how guests discover and accept offers to building the data layer that makes guest recognition reliable at scale.
• Partner closely with the Director of Product and Engineering on complex strategic calls, cross functional alignment and the decisions that have the most long term leverage.
• Collaborate with Staff Engineers and Staff Designers to make sure product decisions hold up technically and create experiences guests actually notice.

AI Fluency Level 3: in this role, that means you design the agents and shared workflows your product builders use to turn customer evidence into decisions, not just use AI tools yourself. You build an approach to discovery and context management that others on the team can pick up and run with on their own, and you are the one who checks whether an AI generated recommendation actually holds up before it shapes a commercial decision.

For more information on AI fluency at Mews, please refer to AI Fluency at Mews: A Comprehensive Guide for Candidates on Confluence.

• Staff or Principal level product experience: you have led the strategy for a meaningful product surface in B2B SaaS, and you set direction rather than execute it.
• A commercial mindset: you naturally reason in outcomes, revenue and business impact, and you can speak to how your product decisions moved a metric that mattered.
• AI Fluency Level 3 or the equivalent hands on experience: you have redesigned how a team works using AI, built an approach others followed, and you actively check AI output rather than taking it at face value.
• Technical fluency: you hold your own in engineering conversations, understand trade offs at the architecture level, and can translate technical constraints into product decisions.
• Experience building reusable product systems: you have encoded your thinking into frameworks, agents or tooling that others actually use, not just documentation that lives in a wiki.