Revenue Operations Analyst

We need to output HTML fragment with sections: About the role? Actually the posting includes "About This Role" and "Our Mission". We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include sections only when posting has real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate etc. We need to parse the posting and extract sections. The posting includes: - About This Role (with mission description) - Our Values: The Principles That Guide Us (list of values) - The Opportunity (description of role) - What You'll Do (list of duties) - What You Bring (Experience, Technical Skills, Soft Skills, Bonus Points) - The People You'll Work With - Life At The Company (benefits etc) - Our Pledge for an Equitable Future (EEO etc) - we should remove EEO boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should drop the "Our Pledge for an Equitable Future" section as it's EEO boilerplate. Also "Compensation Range: $115K - $145K" is pay info, we should include Pay section. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine sections as appropriate. We need to output only HTML fragment, no /, no markdown fences. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not create sections with filler like "commensurate with experience". So only include sections where we have real content. We need to preserve all substantive information. Let's extract content. **About This Role**: includes mission description: "Our Mission: Hospital-Quality Care, Everywhere." Then paragraph about healthcare industry, Verse Medical building modern software infrastructure, etc. Also "Our Values: The Principles That Guide Us" with list of values (transparent, upfront, direct; speed of iteration; give 110% effort 30% of the time; empathize with customers to a fault). That's values content. We could put mission and values under "About the role" heading. **The Opportunity**: description of role: RevOps Analyst / GTM Engineer, role halves, etc. Could be part of About the role or maybe separate "Responsibilities"? But we have a separate "What You'll Do" for duties. So "The Opportunity" could be considered part of About the role (overview). We'll include it in About the role. **What You'll Do**: list of duties broken into sub-sections: Pipeline and Forecast Operations, CRM, Data, and AI-Native Operations, GTM Insights, Assets, and Operating Support. Each has bullet-like sentences. We need to output as

  • for any list of duties/requirements/benefits. So we can create a
    with each duty as
    • . Might be long but okay. **What You Bring**: includes Experience, Technical Skills, Soft Skills, Bonus Points. This could be split into Requirements, Qualifications, Skills. The instruction: Use headings like Requirements, Qualifications, Skills. We need to decide mapping. Experience: "2+ years in revenue operations, sales operations, GTM operations, business operations, or analytics supporting a sales team. Time in a growth-stage company where you built rather than maintained counts for more than years on a résumé." That's a requirement. Strong understanding of GTM metrics, pipeline mechanics, forecast support, CRM hygiene, and sales process discipline. Ownership of a system end to end. Comfort with ambiguity and no playbook. That's also requirement/qualification. Technical Skills: Strong SQL, Deep Salesforce, Hands-on work with LLM tooling in production, Experience with a BI tool and a data warehouse. That's skills. Soft Skills: Analytical and detail-oriented, practical, Clear communication, Track record partnering across sales, marketing, finance, and product, Bias for automation and AI-enabled workflows, Comfortable operating with urgency and ambiguity. That's also skills or qualifications. Bonus Points: Healthcare experience, familiarity with HCPCS, built agent/automation, dbt, Gong's API, prior work wiring GTM stack. That's also skills/bonus. We could create sections: Requirements (experience + understanding + ownership + ambiguity), Qualifications (maybe technical skills?), Skills (soft skills + bonus). But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one "Requirements" section, and Skills into another "Skills" section. Or we could have Requirements, Qualifications, Skills each with content. Given we have ample content, we can make three sections: Requirements, Qualifications, Skills. But we need to ensure we don't create sections with filler. All have real content. Let's map: - Requirements: Experience (2+ years, growth-stage built), Understanding of GTM metrics, pipeline mechanics, forecast support, CRM hygiene, sales process discipline, Ownership of a system end to end, Comfort with ambiguity and no playbook. - Qualifications: Technical Skills: Strong SQL (window functions, multi-CTE), Deep Salesforce (object model, flows, validation rules, reports/dashboards, permissions), Hands-on work with LLM tooling in production (prompting, function calling, MCP, retrieval, checking output), Experience with a BI tool and a data warehouse, opinion on what belongs in warehouse vs CRM. - Skills: Soft Skills (Analytical/detail-oriented, practical, clear communication with non-technical, pushing back respectfully, track record partnering across sales/marketing/finance/product, bias for automation/AI-enabled workflows, judgment to know when output wrong, comfortable with urgency/ambiguity, low ego high ownership) + Bonus Points (Healthcare/DME/home health/post-acute experience, familiarity with HCPCS/payer mix/authorization workflows, built/maintained agent/automation that team depended on, dbt, Gong's API, prior work wiring GTM stack together with code rather than Zapier). We could also include "Benefits": from Life At The Company: "We foster a collaborative and innovative environment where every team member's contribution is valued. We offer competitive benefits, professional development opportunities, and a culture that prioritizes work‑life balance and continuous improvement." That's benefits. Also maybe mention "competitive benefits" but not specific. However we should not create Benefits section if content is vague like "competitive benefits". The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting says "We offer competitive benefits, professional development opportunities, and a culture that prioritizes work‑life balance and continuous improvement." That's somewhat vague but still states benefits exist. It's not a specific list but it's still stating they offer benefits. I'd say we can include a Benefits section with that prose. Pay: "Compensation Range: $115K - $145K". That's pay. Schedule: Not mentioned. So we should not create Schedule section. Now we need to output HTML with headings

      and content. We must not repeat job title as heading. The job title is RevOps Analyst / GTM Engineer. We'll not include that. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like specifics about SQL window functions, multi-CTE, etc. Also specifics about values: transparent, upfront and direct; operate with honesty and clarity; share information openly; value speed of iteration; give 110% effort, 30% of the time; empathize with customers to a fault. We need to keep the mission paragraph. We need to keep the values list. We need to keep the "What You'll Do" details. We need to keep "The People You'll Work With": "You will report to the Head of RevOps. This role is cross‑functional by design: you will work daily with AEs, SDRs, and Sales Managers, and regularly with marketing, finance, enablement, and clinical operations. You will also work closely with product and engineering, since much of what you build sits on the same systems they do. Expect to be the person several teams come to before they make a decision. The stack you'll own: Salesforce (pipeline, stages, and the data behind every forecast conversation), Gong (call review and deal signals), Slack, Notion, and our data warehouse." We need to keep "Life At The Company": "We foster a collaborative and innovative environment where every team member's contribution is valued. We offer competitive benefits, professional development opportunities, and a culture that prioritizes work‑life balance and continuous improvement." We need to keep compensation range. We need to exclude EEO boilerplate. Now structure:

      About the role

      Mission paragraph + values list (maybe as

      ). Could embed values as list.

      Responsibilities

      • ... each duty

      Requirements

      • ... each requirement

      Qualifications

      • ... each technical skill

      Skills

      • ... each soft skill + bonus points

      Benefits

      ... benefits paragraph

      Pay

      Compensation Range: $115K - $145K

      We need to ensure we don't create thin sections. Each has decent content. Now we need to extract each bullet precisely. Let's craft the About the role content. Mission paragraph: "Our Mission: Hospital\-Quality Care, Everywhere. The healthcare industry still relies on faxes and phone tags to coordinate critical care for patients at home. We think patients and the clinicians who serve them deserve better than a system stuck in 1995. Verse Medical is building the modern software infrastructure to make it happen. We're a well‑funded Series C company (backed by General Catalyst, SignalFire, and Sapphire Ventures) on a mission to heal a fragmented system. Our platform connects the dots between providers, payors, and patients, ensuring people get the high‑quality care they need, reliably and right where they live. We’re growing fast and looking for people who are driven by this mission to join us!" Then values: "Our Values: The Principles That Guide Us. Our values are the operating system for how we work together and with our partners. They aren't just words on a wall; they are the principles we bring to every decision, every day. We are transparent, upfront and direct. We operate with honesty and clarity. We share information openly, the good and the bad, and believe that direct, respectful feedback is the foundation of trust and progress. We value speed of iteration. We are building something new, which means we learn by doing. We prioritize rapid iteration and getting solutions into the hands of users, believing that progress is more valuable than perfection. We give 110% effort, 30% of the time. We are passionate about our mission, and there are moments that require us to go the extra mile. We believe in focused intensity when it counts, balanced by a sustainable pace that keeps our team energized for the long run. We empathize with customers to a fault. When our users face a problem, we own it. Instead of asking them to change, we ask ourselves, 'How can we make this better?' We believe true innovation comes from deep empathy and a relentless focus on solving the real‑world challenges of healthcare." We can combine into a paragraph or list. Since values are a list, we can make