RevOps Engineer

About demandDrive:

demandDrive is a growth-focused go-to-market agency that helps B2B organizations accelerate pipeline and revenue through integrated sales, marketing, and revenue operations solutions. We partner with companies ranging from emerging businesses to enterprise brands to design and execute customized programs that align strategy, technology, and execution across the full customer journey. Our services include sales development, demand generation, digital marketing, website development, CRM optimization, and GTM systems support - all built to deliver measurable business outcomes. At our core, we combine smart technology, data-driven processes, and talented people to help clients grow faster and operate more efficiently.

Position Overview - RevOps Engineer:

As our RevOps Engineer, you'll own client CRM engagements end to end, from the first discovery call through blueprint, build, documentation, launch, enablement, and post-launch ROI reporting. You'll be assigned your own clients and own those relationships directly.

The split is roughly 85% client work, 15% internal. That 15% means supporting demandDrive's own HubSpot instance: executing builds and requests from our sales and marketing teams, keeping our data clean and documented, and helping use our portal as the proving ground for things we later bring to clients.

Who We're Looking For:

You know the feeling when you open a client's portal for the first time and find 340 unused properties, four lifecycle stages that all mean "kind of interested," and a pipeline where half the deals closed in 2023 and nobody noticed? Most people see a mess. You see a system that hasn't been designed yet.

We want a builder first. Someone who thinks in object models and data flows, not just workflows, and who would rather script a change from the command line than click through it one property at a time. You already work in Claude Code. You've connected it to a CRM through an MCP server, used the HubSpot CLI to build and deploy, and you have opinions about when to automate a build versus do it by hand. When something new ships, whether it's a HubSpot release, a new MCP server, or a new model, you've already tried it, watched it do something dumb, and rebuilt it with the right guardrails.

You're also business minded. Clients will hand you a list of twenty requests. You can tell which three are business critical and will actually move the needle, translate the goal behind them into clear, actionable next steps, and explain why the rest can wait.

We're an agency, so you won't be building in the background while an account manager talks to the client. You'll be in the room. You'll run discovery, write the blueprint, build it, and train the team on it. Some engagements are greenfield. Some are rescues. Some are Salesforce migrations for a team that's terrified of the change. No two CRMs look the same, and that's the fun part.

Job Responsibilities:

Client delivery (~85%)

• Lead discovery and working sessions with stakeholders across sales, marketing, sales engineering, and post-sale delivery to document current-state process, data sources, and gaps, and translate client goals into clear, actionable next steps.
• Separate business-critical requests from nice-to-haves, and prioritize the work that will actually move pipeline and revenue for the client.
• Write the build blueprint covering object model, lifecycle stages, pipeline design, property architecture, automation logic, and reporting plan, then walk clients through it to sign off before configuration starts.
• Architect and build the full CRM foundation, most often in HubSpot: property architecture, record and object customization, create forms, lifecycle and status frameworks, the Lead object, routing and assignment logic, and multi-pipeline deal processes across sales and post-sale motions.
• Build CLI-first: use Claude Code, the HubSpot CLI, and MCP servers to script configuration, migrations, and integrations so builds are faster, version-controlled, and repeatable across clients.
• Run data consolidation, deduplication, standardization, and migration projects, and stand up the enrichment and data quality automation that keeps the database clean after launch.
• Design attribution models and build the dashboards and reporting infrastructure leadership actually uses to forecast, treating reporting as a design input from day one rather than a final step.
• Build with AI where it earns its place: Claude Code and MCP-connected agents working against live CRM data, plus HubSpot's Breeze agents, Agent Builder, and Breeze Assistant, with the governance and guardrails to match.
• Deliver enablement including recorded training, written documentation, admin enablement for the client's internal system owner, and post-launch support through the first weeks of real usage.
• Build and maintain documentation of each client’s HubSpot instance, covering object model, properties, automation logic, and integrations, so the system stays understandable long after launch.
• Track and report on post-launch ROI, tying what was built back to the business goals set in discovery.
• Scope change orders and retainer expansions honestly, and tell clients when they should wait on something rather than buy it.

Internal HubSpot support (~15%)

• Provide support for demandDrive's HubSpot instance by executing internal builds and projects that align with the defined strategy.
• Execute requests from internal teams, from quick fixes to real builds.
• Keep our own data, reporting, and automation in the shape we'd want a client's to be in.
• Build and maintain documentation of our instance so configuration, automation, and changes are tracked.
• Pilot new HubSpot releases, MCP servers, and AI tooling internally so we know what's real before we recommend it.

Job Requirements & Qualifications:

• CRM Experience (HubSpot Is Non-Negotiable) You need deep, hands-on HubSpot expertise across Sales Hub and Marketing Hub at minimum, ideally Service and Content too. Custom objects and association labels. Lifecycle stage architecture. The Lead object and lead pipelines. Multi-pipeline deal processes with stage gating and required properties. Workflow automation at real complexity. Permissions, teams, and portal governance. Custom report builder and dashboards. You know where the platform's edges are and you design inside them instead of promising around them. Hands-on Attio or Salesforce experience is a plus.
• Builder Mindset: Claude Code, CLIs & MCPs You build with Claude Code day to day, not just as a chat window. You've used CLIs, including the HubSpot CLI, to build and deploy, and you've set up or built MCP servers that connect Claude to a CRM. You reach for the command line when it's faster and more repeatable than clicking, you keep your work in version control, and you review what an agent produced before it touches a client's live data.
• Data Hub, Enrichment & Data Quality Working knowledge of HubSpot Data Hub: data sync, data quality automation, formatting rules, property validation, datasets, and where credits get consumed. You understand HubSpot's native enrichment across automatic, continuous, and manual modes, what it can and can't fill in, and how to set realistic expectations on match rates. You've run a real deduplication and cleanup project and know when native tooling is enough versus when a third-party tool needs to come in.
• AI-First Thinking, Including Agent Builder You approach every problem by asking where AI does the heavy lifting. You're familiar with HubSpot's Agent Hub and Agent Builder, building custom agents and agentic workflows on live CRM data, wiring triggers, configuring knowledge sources, and testing before publishing. You think about credit consumption, run limits, and human review on consequential actions, because agents that write to the CRM without guardrails create cleanup work instead of removing it. You're also comfortable building with Claude and other leading models outside of HubSpot, and you stay current as the landscape moves.
• Client Leadership & Business Judgment You can run a discovery session with a VP of Sales and a skeptical sales engineer in the same room, ask the questions that surface the real process, scope a solution, and communicate clearly about what you're building and when it lands. You can say "that's out of scope, here's what it would take" without it becoming a problem. You translate client goals into clear, actionable next steps, and you can tell which requests are business critical and will actually move the needle versus which ones just feel urgent. You don't need hand-holding in client situations.
• Reporting & Attribution You've built forecasting, closed-won, and operational accountability reporting that leadership trusts. You understand attribution models, first touch versus latest touch and why most clients don't need multi-touch, and how to enforce data capture so the reports hold up.
• Technical Foundation Comfortable with APIs, webhooks, and the command line. You can build an integration or debug a sync issue without pulling in a developer. Light scripting in Python or JavaScript is a plus, as are custom coded actions in HubSpot workflows.
• Data Migration You've moved real data into HubSpot from spreadsheets, another CRM, or somewhere worse. You know how to build import templates, handle associations, backfill historical records, and set expectations about what won't survive the trip.

Nice to Have:

• Experience at a HubSpot Solutions Partner or RevOps consulting firm.
• HubSpot certifications, especially Architecture, Data Integrations, or Solutions Partner-level credentials.
• Attio or Salesforce experience, particularly migrations to or from HubSpot.
• Experience building your own MCP servers, Claude Code skills, or HubSpot developer projects.
• Automation tools like Zapier, n8n, or Make for connecting systems HubSpot doesn't natively reach.
• Familiarity with compliance-adjacent constraints like SOC 2, CMMC, and HIPAA, and how they shape what belongs in a CRM.
• Active in HubSpot or RevOps communities.