Senior GTM System Builder

About the role

<div class="content-intro"><h4><strong>Help make the world more hospitable </strong></h4> <p>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.</p> <p>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.</p> <p>If you’re motivated by ownership, curiosity and meaningful impact, and are driven to deliver consistent high performance, you’ll feel at home here.</p> <h4><strong>About the role</strong></h4> <p>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:</p></div><p>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.</p> <p>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.</p> <p class="font-claude-response-body break-words whitespace-normal"><strong>What you would do</strong></p> <ul class="[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3 print:block print:space-y-1"> <li>Own the full lifecycle of automation and AI-tooling initiatives within your assigned GTM pod: scoping, building, shipping to production, and iterating based on adoption and KPI data — not just ticket completion</li> <li>Build and ship AI-powered pipelines that permanently remove manual GTM work: deal enrichment, outbound research and routing, Gong-driven coaching signals, forecasting inputs, CPQ automation, and proposal follow-up</li> <li>Design the prompting architecture and agent logic that commercial reps, BDRs, and AEs interact with daily — reliable outputs for non-technical end users, with observability and error handling built in from the start</li> <li>Own operational health of your domain's live systems: first responder when things break, with adoption metrics, error rates, and data quality visibility instrumented before deployment</li> <li>Manage vendor relationships at pod level (Gong, Clay, LeanData, ZoomInfo, depending on assignment): SLAs, incident escalation, business reviews, and periodic build-vs-buy re-decisions</li> <li>Support other engineers through code review, pairing, and coaching on architecture trade-offs — and contribute reusable patterns and integrations that accelerate delivery across pod</li> </ul> <p><strong>AI Fluency Level 4:</strong> 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.</p> <p><em>For more information on AI fluency at Mews, please refer to <a href="https://mews.atlassian.net/wiki/x/XQOskg">AI Fluency at Mews: A Comprehensive Guide for Candidates</a> on Confluence.</em></p> <p class="font-claude-response-body break-words whitespace-normal"><strong>What you would bring</strong></p> <ul class="[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3 print:block print:space-y-1"> <li>4 to 6 years delivering production software with measurable commercial impact in a product-driven company (high-growth SaaS, startup, or scale-up)</li> <li>Demonstrated end-to-end ownership with strong autonomy: you have defined the approach, navigated genuine ambiguity, and owned the outcome — not executed tickets</li> <li>Has shipped AI-powered pipelines or agents in a real operational context: enrichment, routing, summarization, or AI-assisted automation — not just prototypes</li> <li>Active practitioner of modern AI development tooling (Claude, Lovable, Cursor, or equivalent) and comfortable working with LLM APIs and MCP integrations — AI Fluency Level 4 or the equivalent hands-on engineering experience</li> <li>Hands-on experience building against Salesforce or equivalent CRM APIs: workflows, event-driven logic, and data integrations across multiple systems</li> <li>Comfortable owning live production systems: incident response, observability, vendor management, and data integrity — draws no hard line between building and running</li> <li>Can translate operational pain into technical requirements and explain technical decisions clearly to non-technical stakeholders</li> </ul> <p class="font-claude-response-body break-words whitespace-normal"><strong>Nice to have</strong></p> <ul class="[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-