Director of Product & Engineering - Support
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:
Support at scale is a product problem, and Mews is hiring the person who will own it end to end. As Director of Product & Engineering, Support, you will build the AI-powered systems that determine how tens of thousands of hospitality operators get help, find answers, and never have a reason to need either. This is not a platform stewardship role. It is a proprietary build problem in a market where no one has solved it well yet.
You will report to the Senior Director of Growth and hold full accountability for the strategy, execution, and culture of the Support tribe. Your scope covers the full AI-powered support and self-service layer (currently built alongside Ada, with internal agents already in development), the product knowledge infrastructure that keeps humans and AI systems accurate as Mews ships fast, and the feedback loop that turns contact volume into engineering prioritisation. This tribe is one of the most influential inputs to the Mews product roadmap. That influence is yours to build and defend.
The boundary is deliberate: your tribe owns what the product does and whether the customer understands it. Everything beyond that (helping customers maximise value from what they have) sits with PLG & CS. Within your boundary, you make the build vs. buy calls, own the architecture, and ship.
What you would do
- Own the full AI-powered support and self-service platform: decide whether Mews extends Ada, migrates to a different platform, or doubles down on the internal agents already in development. Own the configuration, the systems layer, and the platform architecture regardless of which direction you take it. Treat contact rate, chatbot containment and quality, FCR, AHT, and wait time as product outcomes the platform is accountable for moving.
- Design, build, and ship AI-powered resolution and escalation systems: define where LLM-backed retrieval and conversational AI add genuine value in the support motion, where they create friction, and how to measure the difference. Own the evaluation frameworks and the architectural decisions that determine whether Mews builds a proprietary edge or configures toward commodity.
- Own product knowledge infrastructure: the canonical source of truth for how the product works, including help content, release notes, changelogs, and agent-facing knowledge. Build the systems that keep it accurate and discoverable as the product evolves.
- Build and operate the product feedback loop: cluster support tickets by root cause, weight each pattern by ARR exposure and resolution cost, and deliver that intelligence to R&D in a format that moves prioritisation decisions. Track whether the issues you surface get fixed. Measure the support volume reduction when they do.