Senior AI Engineer, Marketing

Overview

Senior AI Engineer for OPSWAT's GTM Product Team, strengthening the technology beneath marketing operations on HubSpot. The role keeps HubSpot integrations healthy and builds an AI-native, in-house marketing platform for lead capture, qualification, routing and campaign management.

What you'll do

• Build one governed front door for every lead source so each lead is validated, de-duplicated, consented and enriched once, at the gate.
• Build AI-native lead qualification that ranks the whole database, explains every score in plain language and learns from SDR conversions.
• Build intelligent lead routing with territory, capacity, availability and priority held as data that Marketing Operations can shape and preview, plus a decision record behind every assignment.
• Make every lead hand-off dependable, with stalls surfaced automatically and nothing lost between systems.
• Give Marketing Operations a self-service campaign layer with per-campaign routing, priority and nurture configuration and a preview against yesterday's leads.
• Build the platform AI-native by exposing its data and actions through an MCP server so internal agents can look up leads, explain routing decisions and trigger campaign actions.
• Make consent and suppression a single source of truth, enforced at the gate and impossible to bypass.
• Stream every signal and decision into OPSWAT Data Master.
• Build seams to SugarCRM, the email service provider, visitor identification, enrichment and My OPSWAT so that failures are contained, retried and visible.
• Use the Platform team's agentic coding platform as the primary means of production, own the quality and security of what ships, and document the system as you go.
• Own the health of HubSpot's existing integrations until each is retired, including the SugarCRM sync, Salesloft, the My OPSWAT feed, 6sense enrichment, web forms and the Forms API.
• Triage and resolve integration incidents across HubSpot and its neighbors, root-cause them, fix them permanently and document what happened.
• Make safe, minimal changes in HubSpot when the business needs them and avoid new workflow and list sediment.
• Build the Forms Gateway pull-forward and run the interim enrollment connector that keeps Salesloft working through cutover.
• Reconcile HubSpot and platform data continuously during the parallel run.

What you'll need

• Bachelor's degree in Computer Science, Software Engineering, or a related technical field.
• 6+ years building and operating production backend systems, with at least 3 in Python.
• Demonstrated, recent, daily practice building software with AI coding agents (such as Claude Code, Cursor, Copilot agent mode, Codex or similar), including a workflow, a review and test loop, and something real that shipped through it.
• Production support of a marketing automation platform's integrations, including its APIs, data model and sync to a CRM. HubSpot strongly preferred; Marketo or Pardot considered.
• Production experience with event-driven and durable-execution patterns: message queues, outboxes, idempotency keys, replay.
• Hands-on integration engineering against real vendor APIs: REST, webhooks, OAuth 2.0, rate limits, retries.
• PostgreSQL to a strong level: schema design, JSONB, partitioning, migrations with Alembic, and query performance work.
• Cloud deployment on Azure or AWS: containers, infrastructure as code (Terraform or Bicep), CI/CD with GitHub Actions, secrets management, observability.
• Experience shipping LLM features into a product: structured outputs, evaluation discipline, confidence thresholds, fallbacks and guardrails, consuming a provided model gateway.
• Excellent written and spoken English, and the ability to explain a technical trade-off to a marketing operations lead in their terms.

Nice to have

• SugarCRM logic hooks and REST API, or another CRM's server-side extension model; Salesforce Apex or triggers transferable.
• Marketing technology domain knowledge: lead scoring and routing, consent and suppression, deliverability and ESP warm-up, campaign attribution.
• Temporal or a comparable workflow engine (strongly preferred).

Details

• Location: AMER, remote.