> Markdown version of [/jobs/ext/4619309-senior-gtm-systems-manager](https://www.wearedevelopers.com/jobs/ext/4619309-senior-gtm-systems-manager). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Senior GTM Systems Manager

- **Company:** Merge LLC
- **Location:** New York, NY, United States
- **Experience:** Expert
- **Contract:** Permanent contract
- **Skills:** Artificial Intelligence, Business Systems, Code Coverage, Object-Oriented Software Development, Salesforce.Com, Claude Code, Agentic-AI, Build Tools
- **Published:** November 7, 2026
- **Apply:** https://www.juju.com/job/28_25303_b273132ee79f73fdfeb059dd819cef3f

## About the Role

Project and stakeholder management as a real strength. You plan backwards from deadlines, write in the language of the person reading, and surface slipped timelines before anyone has to askComfort operating in ambiguity as the default: you take a half-formed ask from an exec, return a scoped plan, and drive it without being managed through it5-8+ years in RevOps, business systems, or GTM engineering, including 3+ owning a Salesforce instance as its architect rather than its adminAI-native as a working method rather than a curiosity. You build and solution with Claude Code and agentic tooling daily, and you've shipped AI agents and automations that run in production with real users rather than demosA bias toward durable automation. You build things that hold under change, with validation, monitoring, and tests, rather than workflows that need you in the loop to keep workingHands-on quote-to-cash: CPQ evaluation or implementation, approval and rate-table design, and a billing system

## Description

* We're hiring a Senior Manager, GTM Systems to own that infrastructure end to end
 * You'll be the architect and the primary builder for Salesforce and everything wired into it: deal desk and CPQ, usage-based billing, partner reporting, and the agents we're putting on top of all of it
 * The work rarely arrives scoped
 * It usually starts as one sentence from a sales leader or the CFO about an outcome they need, and you come back with a plan, a timeline, and a system
 * If you want to design the machine rather than operate someone else's, this is the role
 * Own the architecture of Merge's GTM systems (Salesforce object model, automation, permissions, data quality, sandbox and release governance) and be accountable for whether they're reliable, not just how they're configured
 * Architect and ship net-new builds: CPQ and deal desk, quote-to-cash with Finance, and usage-based billing across product lines
 * Build systems that hold. The measure is what keeps running when you're not touching it: automation with validation, monitoring, and test coverage in front of it, rather than workflows that need babysitting or re-fixing the same breakage every quarter
 * Own change management end to end, not just the build. Project plans that work backwards from a go-live date, enablement for the teams who have to use the thing, legal and security intake, and a written record stakeholders can find without asking you
 * Own the systems roadmap on a quarterly and annual horizon. Sit close enough to sales strategy and pipeline that when GTM direction moves, the systems implications are part of the decision rather than the cleanup
 * Build with AI as the default method. Claude Code and agentic tooling to design, build, and audit systems; production agents that take real work off the GTM org's plate; and the judgment to know which problems are worth an agent and which aren't
 * Own the GTM vendor stack: evaluation, procurement, implementation, and renewal negotiation
 * Multiply the team. Documentation, permissioning, and tooling good enough that RevOps can triage and ship without you in the loop