GTM Engineer

Job Description

Name / Title: [Name], GTM Engineer

\n

Salary Range: $85,000 to $100,000

\n

Position Close Date: When Filled

\n

Function: Revenue Operations / Growth Systems

\n

How This Role Is Different\n

\n
• At many agencies, GTM engineering means building contact lists and running email sequences. At OTM, this role builds and maintains the automated systems that find, qualify, and contact target buyers.
\n
• Success is measured by the pipeline those systems produce.
\n
• This role supports client accounts and OTM's own sales. OTM is treated as a client, with the same standards, reporting, and priority as any other account.
\n
• On the OTM account, the GTM Engineer works with Kerrie to build and run the sales pipeline.
\n
• Strategists and sales leads define the ICP and messaging. The GTM Engineer builds the workflows that put them into practice, maintains the AI agents that run them, and reports on results.
\n
• This role also grows the GTM engineering service line by recommending what to change and what to add.
\n

\n

Signature Moves\n

\n
• Workflow Build: Build automated outbound, inbound, and account-based workflows for enrichment, scoring, routing, and outreach.
\n
• Signal Setup: Define buying signals (hiring, funding, technology changes, intent, website visits) and use them to trigger outreach.
\n
• Data Management: Keep data accurate and in sync across Clay, HubSpot, Apollo, and other tools.
\n
• Sales Support: Give sellers account research, meeting prep, and follow-up drafts so they spend their time selling.
\n
• Pipeline Reporting: Track pipeline, conversion, and results. Report what's working, what isn't, and what to do next.
\n
• Agent Maintenance: Build, maintain, and improve the AI agents used for research, personalization, and qualification.
\n

\n

Who Succeeds in This Role\n

\n
• Thinks in systems and workflows.
\n
• Looks for ways to automate manual work.
\n
• Works independently in Clay, HubSpot, n8n, and APIs.
\n
• Checks data quality before it's used in outreach.
\n
• Measures work by pipeline and revenue, not activity.
\n
• Runs tests, reports results accurately, and adjusts.
\n
• Manages multiple accounts, including OTM, without letting any fall behind.
\n
• Explains technical systems clearly to non-technical clients and teammates.
\n
• Starts work without needing a detailed brief.
\n
• Documents what they build so others can maintain and reuse it.
\n
• Keeps up with GTM tools and AI capabilities, and recommends useful ones to the team.
\n

\n

Impact Areas Workflow Build (30%)\n

\n
• Within 30 days of kickoff, every active account, including OTM, has a documented, automated workflow running and producing qualified pipeline against its quarterly target
\n

\n

Signal Setup (15%)\n

\n
• Each quarter, every active account has defined buying signals triggering outreach, and signal-based outreach outperforms static lists on meetings booked.
\n

\n

Data Management (10%)\n

\n
• Each month, contact and CRM data meets agreed accuracy and deliverability targets, with sync errors fixed within one week.
\n

\n

Pipeline Reporting (20%)\n

\n
• Each month, every account receives a pipeline report with clear recommendations, and at least one test is run and documented.
\n

\n

Agent Maintenance (15%)\n

\n
• Each quarter, every agent and workflow is documented, meets quality standards, and costs less in manual effort or tool spend than the prior quarter.
\n

\n

Sales Support (10%)\n

\n
• Sellers receive a research brief before every first meeting, and follow-ups with next steps are logged within one business day.
\n

\n