Marketing Engineer
About the role
This is a builder role. You’ll spend less time working through requests and more time building things that make requests unnecessary. If you like connecting tools, cleaning up data at the source and shipping automations people actually use, you’ll fit right in.
What you’ll do
- Design and build the systems that create pipeline: lead scoring, routing, enrichment and lifecycle automation.
- Connect the marketing stack through APIs, webhooks and shared data so the tools work as one system.
- Own the marketing data model in [CRM] and the data warehouse, so records show up clean instead of getting cleaned later.
- Design, test and monitor AI agents that do real work, with people checking the output.
- Build templates and self-serve workflows so marketers can launch campaigns on their own.
- Model the funnel and attribution so anyone can get a trusted answer without filing a ticket.
- Document what you build so it keeps running without you.
What you’ll bring
- Hands-on experience with a marketing automation platform and CRM, such as HubSpot, Marketo or Salesforce.
- Comfort with SQL and with reading API documentation.
- Scripting in Python or JavaScript, or strong low-code workflow skills in tools like n8n, Zapier or Make.
- Experience building with AI models or agents, and the judgment to know when not to.
- Clear writing. You document what you build and explain it to teammates who aren’t technical.
Nice to have
- A data warehouse such as BigQuery or Snowflake.
- Enrichment and intent tools such as Clay or 6sense.
- Version control with Git.
- Product analytics such as Amplitude, for product-led signals.
Tools you’ll work in
[List your stack, for example: HubSpot, Salesforce, BigQuery, Clay, n8n and Claude]
Your first 90 days
- 30 days: Audit the stack and the data. Map how a lead moves from first touch to opportunity and where it gets stuck.
- 60 days: Ship your first fix that gives the team real hours back, like faster routing or automatic enrichment.
- 90 days: Deliver a roadmap of systems ranked by pipeline impact, with at least one automation or agent running in production.
How you’ll be measured
Pipeline created, speed to lead, data quality and hours given back to the team. Not tickets closed.