Growth Automation Engineer
Posted 14 Jul 2026
BranchFactor Summary
The original posting with the fluff stripped out
- Management level
- Individual contributor
- Employment
- Remote
- Contract
- Full-time
No salary listed for this role.
GTM Automation Engineer
Full-time · Remote (Latin America) · US Pacific-hours overlap ·
About the role
We're hiring a Growth Automation Engineer. to treat growth as an engineering problem: design and operationalize the systems behind demand capture, lead routing, and experimentation. The marketing operation exists and runs today — the job is to transform its workflows with automation and AI, and build the production-grade systems it runs on next. This is a fast-iteration role: build something, ship it, watch real numbers move, and iterate.
What you'll do
-
Identify and prioritize the highest-leverage GTM motion to transform first, partnering with the marketing team to surface opportunities and develop the strategy to act on them
-
Build and ship working automations with Claude Code and event-driven tools like Zapier and n8n, taking prototypes to production and productizing tools for team-wide use
-
Own the enrichment strategy — ICP segmentation and scoring, and signal-to-action workflows that turn raw data into sales-ready intelligence for reps
-
Design and run multi-channel prospecting pipelines: built-in A/B testing, automated enrichment and scoring, response-detection routing, backed by deliverability infrastructure (SPF/DKIM/DMARC, domain warmup, bounce handling)
-
Support ABM and paid media — audience targeting on LinkedIn and Google, suppression and match-rate workflows, connecting ad-platform engagement to pipeline data, and testing/bidding automation
-
Use AI to scale organic and inbound demand, improving how the brand surfaces in search and AI-generated answers, and tightening capture, routing, and speed-to-lead
What we're looking for
-
Professional experience in GTM engineering, revenue technology, data engineering, or a closely related technical domain
-
Strong bias toward action — you'd rather ship a working prototype and iterate than spec something to death
-
Hands-on experience with workflow automation platforms (Zapier, n8n, Clay, or similar), with real shipped automations, not configured templates
-
Salesforce familiarity, including the data model and experience integrating with or automating within the CRM
-
Experience connecting systems via APIs — REST, webhooks, OAuth, rate limiting, error handling
-
An owner mindset — not just closing tickets, but asking whether the right problems are being solved the right way