Marketing Engineer

AI Fund is on a mission to empower everyone to build with AI, and they are seeking a Marketing Engineer to enhance their marketing operations through automation and AI-driven tooling. This hands-on technical role involves designing workflows, integrating marketing technologies, and building infrastructure for experimentation and reporting.

Responsibilities:

• Design and build agentic workflows that automate lifecycle triggers, campaign QA, segmentation logic, and reporting that the team currently does by hand
• Identify which marketing workflows are highest-leverage to automate first, in partnership with the Lifecycle Marketing Manager and Marketing Operations Coordinator
• Build internal tools that let non-technical marketers configure and launch automations without engineering support
• Continuously evaluate new agentic and AI tooling (Claude, other LLM APIs, automation platforms) and prototype how it applies to our specific funnel problems
• Own the technical integration layer between Customer.io, Stripe, PostHog, our platform's event data and any other tools we might use, so lifecycle triggers fire on accurate, real-time data
• Support various platform and data migrations with scripting, platform expansions, and workflow recreation as needed
• Build and maintain the data pipelines that feed our Metabase dashboard, partnering with Data Engineering to close our current LTV and cohort data gaps
• Set up and maintain UTM, tracking, and attribution infrastructure so channel performance data is trustworthy
• Build the technical infrastructure for A/B testing across lifecycle, email, and on-platform messaging, so the Lifecycle Marketing Manager and PMM team can test rigorously without engineering as a bottleneck
• Build self-serve reporting tools that let marketing stakeholders answer their own data questions without filing a ticket
• Where it's a natural byproduct of the automation work, document exciting or interesting builds for use in our content across our newsletters, YouTube accounts, events, or technical blogs. Note this supports the content engine but is not a primary deliverable or goal
• Partner with Developer Relations when a build is interesting enough to become a public case study or tutorial