Employer description & source details
Own the GTM systems across our portfolio. Each acquired company brings its own CRM, data, and sales process; you turn it into a connected, automated stack, then package it so the next company onboards faster. Ops first, outbound second. A GTM expert guides architecture and reviews each step. Scope expands to other verticals (sourcing, talent, etc.). Get data access from companies; ingest, clean, dedupe, load, and route it into a CRM in Emergence's name; configure fields, pipelines, permissions, suppression Connect CRMs, Slack, notes tools, and calendars via APIs, webhooks, OAuth, MCPs, cron jobs, and VMs; own auth, rate limits, app registrations, sync fixes Map every process in Figma (or similar) before building and keep it current; document each build as a playbook 5+ years in RevOps or GTM engineering; deep Salesforce or HubSpot, quick to ramp on others Daily building with Claude Code, Codex, Cursor, or similar, plus Python and SQL to fix its code GitHub hygiene: small commits, branches, worktrees, PRs, in-repo docs Per-company permissions and self-running automations Careful and safe: least privilege, secrets in a vault, never pasted in chat, per-company data separation, dry runs, approvals before irreversible steps, idempotent jobs Organized: tasks in one place, notes captured, short log Outbound and GTM/revenue roles: sequences, SDR/AE needs, do-not-call lists, ICP rules More than one CRM administered; same systems rolled out across companies Contact enrichment, data sourcing, AI agents
Extracted skills: python, sql, figma, sales