RevOps Engineer (GTM Systems)

Title: RevOps Engineer (GTM Systems)

Reports to: Head of GTM Ops

Mission:

Own and operate the systems that run Docket's go-to-market: the TAM engine, attribution, martech stack, and reporting, so leadership can trust the numbers and the pipelines keep flowing without a single point of failure.

What you'll own:

- Maintain the engine (Supabase, agents, crons, data ingestion from Factors,HubSpot, Clay, and outbound tools). Keep it correct, monitored, and documented.

- Own the internal tools hub and dashboards on cron jobs, routines, and uptime.

- Own attribution and data hygiene end to end: the UTM spec, HubSpot property mappings and workflows, dedupe, suppression, deliverability, and source-of-truth definitions

- Run and evolve the ad-channel data pipelines and the weekly/monthly reporting that marketing and sales leadership rely on.

- Manage the martech and API stack: HubSpot, Factors, Clay, Lemlist, and the Google/Meta/LinkedIn/Bing ad APIs,including credential and token rotation.

- Instrument sales-marketing-CS handoffs and keep cross the funnel.

- Reduce key-person risk: document systems, add monitoring and alerting, and make the stack operable by more than one person.

Required

- Strong SQL and comfort in Postgres. Understands enough code to know when to let LLM make changes vs interfere and ship via Git and Vercel.

- Built or maintained API integrations against marketing and CRM platforms.

- HubSpot admin-level fluency, including workflows

- Practical grasp of B2B attribution and funnel metrics (MQL/AQL, pipeline stages, source tracking).

- Operator mindset: owns uptime, catches silent failures, documents as they go.

Nice to have

- Experience with product-led or PLG data, deanonymization/intent tools (Factors, RB2B, Vector), and outbound tooling.

- Exposure to LLM-driven workflows or agentic auto

First 90 days

1. Document and take over operation of the TAM engine and the tools hub, including all crons and credential rotations.

2. Add monitoring and alerting so failures surfaced numbers.

3. Take ownership of the weekly reporting cadence end to end.