Head of Revenue Operations

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. We need to parse the posting. First part: "About This Role" description: It's a description of company and role. That could be "About the role". We'll put that in

About the role

then

with that prose. Then "About The Role" heading again? Actually there is "About The Role" after the first paragraph. That seems duplicate. We'll combine. We need sections: Responsibilities: list of duties. The posting includes many bullet-like sentences under "You Will Own Revenue Systems..." etc. Those are responsibilities. We'll extract them into

• . Requirements/Qualifications/Skills: The posting includes "You Have Must Have RevOps Leadership Experience:" list of must-haves, and "Nice to Have" list. Those could be Requirements (must have) and Qualifications (nice to have) or Skills. We need to decide. We have sections: Requirements, Qualifications, Skills. We could put must-have under Requirements, nice-to-have under Qualifications, and maybe Skills under Skills? But we must not create empty sections. We need to see if we have content for each. We have must-have items: 5-8+ years experience, Systems & Tech Stack Mastery, AI & Automation Curiosity, Enablement & Ramp Ownership, Data & Analytics Proficiency, Stack Rationalization Skills. Those are requirements. Nice-to-have: Billing Operations, Product-Led Growth, Early-Stage/High-Growth Scaling, Multi-Segment GTM, Marketing Attribution & Demand Gen. Those could be Qualifications or Skills. We could treat Requirements as must-have, Qualifications as nice-to-have, Skills maybe not needed if we already covered. But we need to include Skills only if there is specific skill content. Could we put technical skills like HubSpot, Chargebee, SQL, BI tools under Skills? Those are mentioned in must-have. Might be redundant. Better: Use Requirements for must-have, Qualifications for nice-to-have, and omit Skills if no distinct content. But we need to check if we have any skill-specific list separate: The posting mentions "Deep expertise configuring and managing HubSpot, along with strong experience in billing/subscription management platforms (Chargebee or similar) and operational architecture." That's skill. Could be under Skills. We could allocate: Requirements: years experience, leadership experience. Qualifications: nice-to-have. Skills: technical expertise (HubSpot, Chargebee, SQL, BI tools, AI tools). However we must avoid duplication. Let's think: The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can choose which to include. We have content for About the role, Responsibilities, Requirements (must-have), Qualifications (nice-to-have), Skills (technical), Benefits (listed), Pay? Not mentioned. Schedule? It says "This role is 100% remote and available to US‑based candidates. (Boston, MA preferred)*" That's schedule/location info. Could be Schedule section? It mentions remote work, but not specific schedule like full-time, hours. Might be considered Schedule? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits are stated: medical, dental, vision, equity, PTO, parental leave, FSA/HSA, 401(k), stipends, WFH equipment stipend. So Benefits section is valid. Pay: not stated, so omit. Schedule: The posting says "This role is 100% remote and available to US‑based candidates. (Boston, MA preferred)*". That's about location/remote, not schedule like hours. Could be considered Schedule? Might be considered "Schedule" as remote work arrangement. But the instruction says only if posting actually states them. It does state remote work. Could treat as Schedule. However we already have Benefits section for remote? Actually remote work is not a benefit but work arrangement. Could be Schedule. I'd include Schedule section with that sentence. But we must avoid filler like "varies". This is specific: 100% remote, US-based, Boston preferred. So we can include. Now we need to ensure we don't repeat content. Let's extract About the role prose: The first paragraph about Steer company and role summary. Also there is "About The Role" heading later with similar content. We'll combine into one prose. Prose: "Steer offers a suite of software tools for today's automotive repair shop. We combine a mix of software tools that a repair shop needs to run a highly profitable shop, in one user‑friendly, cost‑effective platform. Through the Steer suite, we allow the shop owner to get back to focusing on what matters, and to stop worrying about marketing and customer retention. Steer began as an online directory for drivers to find a local mechanic. Fast forward to today, Steer has launched a complete Customer Relationship Management (CRM) marketing suite, complete with text messaging, email automation, direct mail integration, reputation management, appointment reminders, declined/recommended services, and many other features. We are always innovating and we are proud to be a leader in the automotive repair industry. In August 2024 Steer acquired AutoOps — the leader in modern, intelligent, and fully integrated scheduling software for auto repair shops. AutoOps allows customers to smoothly schedule through a shop's website and Google Business Profile. As Head of Revenue Operations, you will build, optimize, and scale the operational, data, and technology foundation across our entire go‑to‑market organization—including Sales, Marketing, Customer Success, Finance, and Partnerships. Reporting directly to executive leadership, your mission is to transform our systems, billing infrastructure, reporting, and GTM strategy into a clear, high‑performing growth engine. You will lead a small but high‑impact RevOps team (2 direct reports) while personally owning the architecture and execution of our RevTech stack (including HubSpot and Chargebee), lead management, funnel optimization, enablement and ramp, and AI deployment. This is not a traditional admin role—we are looking for a builder, strategic systems architect, and AI‑forward operator who rationalizes existing tools before adding new ones, replaces manual reporting with automated signal, and shortens new‑hire time‑to‑productivity as a core business metric. This role is 100% remote and available to US‑based candidates. (Boston, MA preferred)*" That seems good. Now Responsibilities: list of duties under "You Will Own Revenue Systems..." etc. We'll extract each sentence as a bullet. Let's list: - Lead full ownership and architecture of core revenue systems (HubSpot, Chargebee, and broader RevTech). - Continuously inspect, consolidate, and optimize current platforms before evaluating new spend. - Build advanced automation workflows across Marketing, Sales, CS, Finance, and Partnerships, and deploy AI tools (such as living AI knowledge bases/Claude skills libraries) to streamline operations. - Drive Enablement, Ramp & Team Productivity: Own new‑hire ramp time with a clear, measurable path to reduction. Design onboarding, coaching, and exception‑based reporting workflows that run through systems rather than headcount. Partner with Sales leadership on structural changes (comp design, team placement) that raise pipeline productivity per rep. - Optimize Funnel Performance & Revenue Intelligence: Diagnose pipeline leaks and conversion bottlenecks across all channels. Build executive dashboards, forecasting models, and predictive analytics to improve speed‑to‑lead, decision‑maker contact rates, expansion efficiency, and retention outcomes. Ground all recommendations in data first. - Lead Data Strategy & Governance: Define how data is captured, structured, and managed across the customer lifecycle, improving CRM hygiene, billing accuracy, reporting integrity, and system interoperability. - Manage & Develop the RevOps Team: Lead, hire, and mentor 2 direct reports. Build a culture of innovation, systems thinking, accountability, and technical excellence, raising team competency across AI, automation, and systems architecture. - Partner Cross‑Functionally: Collaborate closely with Sales, Marketing, CS, Finance, Product, and Executive Leadership to support product‑led growth (PLG) motions, upgrade paths, monetization strategies, and long‑term GTM infrastructure. We could split some long bullets but okay. Now Requirements (must-have): - 5–8+ years of experience in Revenue Operations, Sales Operations, GTM Systems, or Revenue Enablement, with proven experience leading teams or major strategic initiatives. - Systems & Tech Stack Mastery: Deep expertise configuring and managing HubSpot, along with strong experience in billing/subscription management platforms (Chargebee or similar) and operational architecture. - AI & Automation Curiosity: Hands‑on track record implementing modern automation tools and proactive experience deploying AI solutions (including AI‑powered knowledge or enablement systems). - Enablement & Ramp Ownership: Experience owning, measuring, or influencing new‑hire ramp time and onboarding outcomes as core operational metrics. - Data & Analytics Proficiency: Strong analytical background with direct experience querying raw data, building forecasting models, and designing board‑level/executive dashboards (SQL, BI tools, or advanced analytics platforms). - Stack Rationalization Skills: Proven track record evaluating, consolidating, or replacing major GTM and business software platforms. Now Qualifications (nice-to-have): - Billing Operations: Direct experience with Chargebee, subscription management, and revenue recognition workflows. - Product‑Led Growth (PLG): Experience supporting PLG motions, automated upgrade paths, and expansion loops. - Early‑Stage / High‑Growth Scaling: Experience scaling a RevOps function in a fast‑growing SaaS tech company. - Multi‑Segment GTM: Background supporting multi‑segment environments (SMB, Mid‑Market, and Enterprise). - Marketing Attribution & Demand Gen: Deep understanding of marketing attribution models and demand generation tech stacks. Now Skills: Could include technical skills like HubSpot, Chargebee, SQL, BI tools, AI tools, automation platforms. But we already covered many in Requirements. Might be redundant. Perhaps we can omit Skills section to avoid thin content. But we have technical skills not covered as separate? The Requirements includes HubSpot, Chargebee, SQL, BI tools. That's enough. So we could skip Skills. Benefits: list: - 100% remote work environment - Medical, Dental, and Vision insurance within 30 days (100% employer‑paid medical) - Equity package - Flexible PTO with a 15‑day minimum - Generous Parental Leave - FSA and HSA options - 401(k) - Growth & Wellness Stipend - WFH Equipment stipend - Chance to work with the latest technology and AI tools - A collaborative, high‑ownership culture with clear opportunities for career growth Schedule: remote work arrangement: "This role is 100% remote and available to US‑based candidates. (Boston, MA preferred)*". We'll put that as a paragraph. Now ensure we don't include boilerplate like interview process, Wonderlic assessment, etc. Remove those. Also remove "We Offer" heading? We already captured benefits under Benefits. The "We Offer" list includes those benefits; we already captured. Also "Why Join Steer?" is promotional; we can omit as boilerplate? It's not required but could be considered fluff. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Why Join Steer?" is promotional but not boilerplate; could be considered part of About the role? Might be okay to include but it's somewhat generic. However we already have About the role covering mission. Might be safe to omit to keep concise. We must not invent or summarize away detail. We need to preserve all substantive information. The "Why Join Steer?" includes mission alignment, opportunities