GTM Engineer (Solutions Delivery)

Client Implementation

1. Own end-to-end implementation of GTM systems across CRM, marketing automation, data enrichment, and outbound infrastructure
2. Translate client briefs and discovery calls into scoped, working solutions — not just recommendations
3. Build and configure workflows, sequences, scoring models, routing logic, and attribution setups across tools like HubSpot, Salesforce, Clay, Apollo, and similar

Systems Thinking

1. Diagnose broken or inefficient GTM stacks and propose fixes with clear tradeoffs
2. Design integrations between tools using native connectors, Zapier/Make, or lightweight custom code where needed
3. Document what you build so clients can operate it after you hand it off

Cross-functional Collaboration

1. Work closely with strategists and account leads to make sure implementation maps back to the original GTM hypothesis
2. Surface insights from the stack — pipeline trends, conversion drop-offs, data quality issues — and flag them proactively
3. Occasionally contribute to scoping calls and proposals, helping clients understand what's technically feasible

You're a good fit if you:

1. Have 2–4 years of experience in a GTM, RevOps, marketing ops, or sales ops role — ideally at a B2B SaaS company or an agency serving one
2. Are comfortable owning a project from kickoff to delivery without a lot of hand-holding
3. Know your way around at least 3–4 of the major GTM tools and can pick up new ones quickly
4. Can write basic scripts or use low-code tools to connect systems when native integrations fall short
5. Think in systems — you naturally ask "what happens downstream?" before you build anything
6. Communicate clearly with clients, including when something is more complicated than they assumed

Nice to Have

1. Experience with data enrichment workflows (Clay, Clearbit, Apollo)
2. Familiarity with AI-assisted GTM tooling (agents, prompting for research/personalization, LLM-based enrichment)
3. Prior work in a services or consulting environment
4. Exposure to ICP definition, segmentation, or messaging work — not just the tooling layer