The Position

We are looking for an innovative engineer for the GTM Product Team to strengthen the technology beneath OPSWAT's marketing operations. Marketing runs on HubSpot today, and it works hard for us: 1.1 million contacts, 817 active workflows, and the integrations that connect it to SugarCRM, Salesloft, My OPSWAT, websites and our data master. Your first job is to make that foundation more reliable — keeping the integrations healthy, resolving the sync and data-quality issues that slow the team down, and giving Marketing Operations a technical partner who understands their platform from the inside.

From there, you will help us build the next generation of that capability in house. The four functions HubSpot performs for us are the roadmap: marketing automation and email; lead capture from web, portal, events and webinars; lead management, meaning scoring, lifecycle and routing; contact data governance and consent and tight integration with our OPSWAT Data Master (ODM). Along the way you will bring AI into the product to enable smarter lead qualification, routing and scoring and more automated campaign managements.

What You Will Be Doing

Build the Platform

• Build one governed front door for every lead, whatever the source — web forms, My OPSWAT, webinars, field events, partner and list imports — so each lead is validated, de-duplicated, consented and enriched once, at the gate, and nothing reaches the CRM or the data spine any other way.
• Build AI-native lead qualification: a model that reads fit and engagement across every signal we hold — product usage in My OPSWAT, Academy progress, web behavior, intent, firmographics — ranks the whole database with real resolution, explains every score in plain language, and learns from what SDRs actually convert.
• Build intelligent lead routing: the right lead to the right rep at the right moment, with territory, capacity, availability and priority held as data that Marketing Operations can shape and preview themselves, and a decision record behind every assignment so anyone can see why a lead went where it did.
• Make every hand-off dependable: each lead tracked from capture to first touch, stalls surfaced automatically, every priority tier followed up, and nothing lost between systems.
• Give Marketing Operations a self-service campaign layer: per-campaign behavior — routing, priority, nurture — configured in minutes with a preview of what it would have done to yesterday's leads, so new campaigns stop requiring new workflows and old overrides expire on their own.
• Build the platform AI-native from day one: expose its data and actions through an MCP server so OPSWAT's internal agents and assistants can look up a lead, explain a routing decision, or trigger a campaign action in natural language — and design every capability so an agent can use it as readily as a person can.
• Make consent and suppression a single source of truth, enforced at the gate and impossible to bypass, and stream every signal and every decision into OPSWAT Data Master so marketing, product and sales data finally join in one place.
• Build the seams to SugarCRM, the email service provider, visitor identification, enrichment and My OPSWAT so that a failure in any one of them is contained, retried and visible — never silent, never lossy.
• Leveraging OPSWAT Agentic SDLC — use the Platform team's agentic coding platform as your primary means of production, own the quality and security of what ships, and document the system as you go so it stays knowable.

Keep HubSpot Running Through the Transition

• Own the health of HubSpot's existing integrations until each one is retired: the SugarCRM sync through the Sugar Data Tool, Salesloft, the My OPSWAT feed (portal and Academy), 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 write down what happened.
• Make safe, minimal changes in HubSpot when the business needs them, and hold the line against new workflow and list sediment that the migration would only have to unwind.
• Build the Forms Gateway pull-forward so website capture decouples from HubSpot early, and run the interim enrollment connector that keeps Salesloft working through cutover.
• Reconcile HubSpot and platform data continuously during the parallel run so drift is caught long before a cutover gate.

What We Need From You

• 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 (Claude Code, Cursor, Copilot agent mode, Codex or similar). You can show us the workflow, the review and test loop, and something real that shipped through it.
• Production support of a marketing automation platform's integrations — HubSpot strongly preferred; Marketo or Pardot considered — including its APIs, its data model, and its sync to a CRM. You have kept one of these healthy while other things changed around it.
• Production experience with event-driven and durable-execution patterns: message queues, outboxes, idempotency keys, replay. Temporal or a comparable workflow engine strongly preferred.
• Hands-on integration engineering against real vendor APIs — REST, webhooks, OAuth 2.0, rate limits, retries — built and operated, not configured through a wizard.
• PostgreSQL to a strong level: schema design, JSONB, partitioning, migrations with Alembic, and query performance work you can describe.
• 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 rather than building the infrastructure.
• Excellent written and spoken English, and the skill to explain a technical trade-off to a marketing operations lead in their terms.

It Would Be Nice If You Had

• 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.