Senior GTM System Builder at Mewssystems

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:

The commercial team at Mews moves deals through a complex, multi-touch GTM motion. The person in this role owns the systems that make that motion faster, smarter, and less dependent on manual effort — from inbound routing and deal enrichment to Gong-driven coaching intelligence and CPQ automation. This is not a support role for the commercial team. It is an ownership role for the infrastructure they run on.

You will join the Growth team to own an assigned domain within the GTM stack end to end: scoping, building, shipping, and running production systems that move ARR. You will work under staff technical direction but make your own architecture and build-vs-buy decisions within your domain. You will manage vendor relationships, define observability standards, and be the person who picks up the phone when something breaks in production.

What you would do

AI Fluency Level 4: In this role, AI is not a productivity layer — it is the product. You will architect and ship LLM-powered agents, enrichment pipelines, and AI-assisted automations that the commercial org depends on. You will make engineering decisions about models, infrastructure, and MCP integrations. You will design prompting systems that non-technical users rely on without ever touching a prompt themselves. The test for everything you build is whether a KPI moved — which means your judgment about where AI is trustworthy and where it needs a human in the loop is part of the work, not an afterthought.

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