About this role.
This fractional RevOps/GTM Engineer will build and own the revenue systems layer spanning HubSpot, Stripe, Snowflake, Metabase, Zapier, and AI-enabled workflows. The work centers on complex account hierarchies, multiple GTM motions, and normalized reporting across subscription, usage-based, and percentage-of-collections pricing. The contractor will design CRM architecture, maintain production integrations, model revenue data, and create leadership-facing analytics. This is a highly hands-on, self-directed role requiring strong technical judgment and comfort operating asynchronously with minimal oversight.
Role DNA
A quick view of the complexity, pace, ownership and collaboration implied by the job description.
Job Complexity
5/5Pace & Pressure
5/5Autonomy Level
5/5Communication Load
4/5Salary analysis
Estimated compensation compared with the broader US market for similar roles.
Core skills
Skills and capabilities most closely associated with this opportunity.
Sample interview questions
I would define a clear canonical company-object strategy, using parent-child associations and, where needed, custom objects or properties for hierarchy level and external identifiers. I would establish deduplication rules that account for location and parent ownership, then publish tested rollup logic to the warehouse so both location-level and parent-level reporting remain consistent.
I would first create a documented revenue taxonomy and a grain-consistent billing fact table in Snowflake. Each pricing model would be transformed into normalized recurring-revenue measures with explicit assumptions, then reconciled against Stripe source data and CRM account mappings before powering ARR, NRR, cohort, churn, and expansion dashboards.
I use Zapier for stable, low-volume workflows with straightforward triggers, limited transformation needs, and low operational risk. I prefer custom code or managed integration services when workflows require robust retries, idempotency, complex matching, sensitive data handling, higher throughput, detailed observability, or version-controlled business logic.
I would begin with a measurable use case, authoritative data sources, structured output schemas, and a human-review path for consequential updates. I would evaluate precision, coverage, latency, and cost on a representative sample, log prompts and outcomes, and use deterministic validation rules before writing results back to HubSpot.
I would define shared lifecycle and metric contracts while allowing motion-specific routing attributes and stage mappings. The warehouse model would retain both a common reporting layer and motion-level detail, supported by data-quality tests, reconciliation checks, and documented ownership for each operational definition.
Anagram is the ultimate insurance billing platform for eye care providers. Combining instant eligibility and benefit verifications, patient responsibility calculation, claims management, payment posting, and more, Anagram’s all-in-one revenue cycle management solution is designed to save providers time and money, and free doctors to deliver the best care for their patients. Our mission is to simplify insurance, and it’s working: over 2,000 eye care professionals rely on Anagram to manage their insurance billing.
Founded in 2014, Anagram is the largest and fastest-growing insurance billing platform for eye care providers in America and processes hundreds of millions of dollars each year.
About the Role
We’re looking for a hands-on RevOps/GTM engineer to own the revenue systems layer across a genuinely messy and interesting go-to-market. You’ll design and maintain the pipes connecting CRM, billing, warehouse, and analytics, and wire AI into the workflows in between. You’ll work directly with revenue leadership and have wide latitude in how things get built.
Why This Role Is Harder Than It Sounds
The account hierarchy is real. Our market spans solo practices, multi-location companies, roll-up brands, and PE platforms. The HubSpot company object has to do quadruple duty — PE firm → brand → company → location — with clean parent-child associations, dedup logic that respects the hierarchy, and reporting that rolls up correctly at every level.
Four GTM motions run in parallel. SMB, mid-market, enterprise, and partner led — each needs its own routing, lifecycle logic, handoffs, and funnel reporting, without forking the CRM into four incompatible systems.
Three products, three pricing models. Subscription, usage-based, and percentage-of-collections billing all flow through the same revenue stack. Normalizing these into coherent ARR/NRR, cohort, and revenue reporting is a core design problem, not an afterthought.
About You
You’re a hands-on RevOps/GTM engineer with a builder profile.
Strong SQL from scratch.
You know when a Zap is enough and when it’s time to write code.
Self-directed; comfortable operating fractionally with async communication and minimal oversight.
What We’re Looking For
Must-Haves
4+ years in RevOps, GTM engineering, or sales/marketing ops with a builder profile
Deep, hands-on HubSpot experience custom objects, associations, workflows, API —ideally with complex parent-child account structures (multi-location, franchise, healthcare, or roll-up environments)
Production experience with Stripe data, including usage-based or non-standard billing models
Production experience with Zapier
Practical experience building with Claude or comparable LLM APIs, prompting, evaluation, and knowing the failure modes
Self-directed; comfortable operating fractionally with async communication and minimal oversight
Nice-to-Haves
Healthcare or vertical SaaS experience; familiarity with provider data (NPI/NPPES, CMS datasets)
Experience supporting multiple concurrent GTM motions (PLG/SMB velocity alongside enterprise sales)
dbt and enrichment tooling (Apollo)
What You’ll Do
CRM architecture (HubSpot): The parent-child company model, lifecycle stages, lead routing by segment, workflows, dedup, and data hygiene. You keep the CRM trustworthy so pipeline numbers are real at both the location and parent level.
Billing-to-CRM sync (Stripe): Reconcile heterogeneous billing data (subscription, usage, % of collections) with CRM records; surface churn, expansion, and payment signals where the revenue team can act on them.
Automation (Zapier + scripting): Build and maintain the integration layer. Know when a Zap is enough and when it’s time to write code.
Data warehouse (Snowflake): Model GTM and revenue data into clean, queryable tables that handle the hierarchy and mixed pricing models. Strong SQL from scratch.
Analytics (Metabase): Dashboards leadership actually uses funnel conversion by motion, pipeline coverage, revenue normalized across pricing models, rollups by parent account.
AI workflows (Claude): Lead enrichment and scoring, call summarization, follow-up drafting, and data cleanup at scale, including provider-level enrichment from industry datasets (NPI/NPPES).
Anagram offers employees:
Industry-leading compensation, including salary and equity ownership
MacBook, monitor, and all the technologies you need to succeed
Full Medical & Dental Insurance
Unlimited PTO
401k
Remote first company
Fast-paced startup environment
Anagram is an equal opportunity employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex (including pregnancy), sexual orientation, gender identity, national origin, age, disability, veteran status, or any other characteristic protected by applicable law.
Annual salary information is not provided for this position. Explore salary ranges for similar roles in our Salary Directory ›
Upload your resume now
- To unlock remote work opportunities and be discovered by global employers.
This job listing has been manually reviewed by the Jobicy Trust & Safety Team for compliance with our posting guidelines, including verification of the company's legitimacy, accuracy of job details, clarity of remote work policy, and absence of misleading or fraudulent content.
