Manager, GTM Engineering

What You'll Be Doing

PCP Referral Engine

• Build the referral engine: Design and ship the data model and automation logic that convert SDR/AE/AM physician-office outreach into a repeatable, inbound patient-referral engine.
• Re-architect the data model: Redesign the underlying data model powering the PCP referral engine - how physician accounts, outreach activity, and patient referrals relate to each other in HubSpot - to eliminate structural gaps and support scale.
• Connect outreach to referrals: Build the data pipeline linking office-level outreach activity (HubSpot, Gong, Aircall/Nooks) to physicians and the downstream patient referrals they generate.
• Automate intake and routing: Ship automated intake, validation, and routing logic so inbound referrals from physician offices are captured and assigned with zero manual handling.
• Ship attribution: Build the reporting layer that ties SDR/AE/AM outreach investment directly to referral volume and quality.

EAP Systems (0-to-1)

• Map the journey: Map the end-to-end consultant → employer → employee journey and translate it into a systems and data architecture built from scratch.
• Build the data model: Design and build the staging environment and HubSpot data model representing consultants and employers as distinct, related entities - without conflating them with Grow's existing GTM data model.
• Ship consultant & RFP tooling: Build the workflows and tracking needed to manage consultant relationships and run RFP processes at scale.
• Architect the handoffs: Build the handoff logic from consultant/RFP engagement through to employer sale, so no lead or opportunity is lost between stages.

AI & Automation

• Build AI agents, not just workflows: Design and deploy AI agents (built on Claude) that autonomously perform GTM tasks - referral triage, physician-office research, account qualification - rather than workflows that simply call an LLM API.
• Run an experimentation loop: Treat new automations and agent behaviors as experiments - ship fast, measure impact, and iterate or kill based on data, not intuition.
• Sandbox everything: Implement rigorous testing and deployment across n8n, Workato, and HubSpot so no logic goes live unvalidated.

Systems & Team

• Document the system: Maintain a technical schema map of the Enterprise GTM systems so the broader team understands the logic behind every automation.
• Own the architecture: Serve as the architecture owner for Grow's GTM systems end-to-end - Provider Experience, PCP, and EAP - setting the technical standards, data model conventions, and integration patterns that the GTM Engineer, Provider Experience builds against, even while your own build focus stays on PCP and EAP.
• Own data governance: Define and enforce data governance standards - field definitions, ownership, quality rules, and access controls - across the PCP and EAP data models so they stay trustworthy and consistent as referral and consultant volume scales.
• Build for resilience: Build monitoring and self-healing automations that alert the team when data syncs fail or logic breaks across Aircall, Nooks, Segment, and HubSpot.
• Shape the future team: Partner with the Head of Revenue Operations to scope the future GTM Systems team structure once PCP and EAP are stood up, including how systems analyst hires and the GTM Engineer, Provider Experience role plug into it.

Outcomes You'll Own

• Growing the demand side: Increase the number and quality of inbound physician referrals and successful patient intakes flowing into Grow.
• Scaling without linear effort: Deliver a referral engine and EAP systems foundation that let referral and intake volume grow without a proportional increase in manual effort.
• Unifying the architecture: Ensure Provider Experience, PCP, and EAP run on one coherent, consistent GTM systems architecture rather than three disconnected builds.

You'll Be a Good Fit If You Have

• Experience: 8+ years in a technical RevOps or GTM Engineering role, preferably within a high-velocity B2B or B2B2C environment; experience with healthcare, benefits, or provider referral channels is a plus.
• An Architect Mindset: You see logic gates, data schemas, and API endpoints, and you build for the version of Grow's Enterprise business that's 10x its current size.
• Cross-Org Systems Architecture: Experience owning technical architecture that spans multiple teams or motions - setting standards others build against - not just architecting within a single team's scope.
• HubSpot Mastery: Expert-level technical knowledge of HubSpot (Advanced Workflows, Custom Objects, data model design), Grow's core CRM.
• Orchestration Fluency: Expert proficiency in n8n and Workato, and comfort integrating dialing/outreach tools (Aircall, Nooks), call intelligence (Gong), and event data (Segment).
• AI Agent Builder: Proven experience building AI agents and agentic workflows (Claude, OpenAI, or Gemini) that autonomously perform GTM tasks, not just single-step LLM calls, and using enrichment tools like Clay.
• 0-to-1 Systems Builder: Experience standing up net-new systems and data models for a channel or motion that didn't previously exist, not just optimizing an existing one.
• Multi-Stakeholder Data Modeling: Comfort designing CRM data models that represent complex, multi-party relationships (e.g., consultant/employer, or referring physician/patient).
• Data Governance: Experience setting data governance standards - definitions, ownership, quality rules, access controls - as a core part of data strategy, not an afterthought bolted on once a model is live.