Revenue Operations Analyst

We need to output HTML fragment with sections only when content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content: Mission description, values, opportunity, what you'll do, experience, technical skills, soft skills, bonus points, people you'll work with, life at company, pledge, compensation range. Need to map to sections. We should not repeat job title. No Job ID. Remove boilerplate: EEO, equal opportunity, scam warning, navigation, cookie, legal, application instructions. The text includes "Our Pledge for an Equitable Future" and "We are an equal opportunity employer." That's EEO boilerplate; we should remove that. Also "If you require any accommodations..." is part of EEO; remove. Also "Compensation Range: $115K - $145K" is pay info, so we need a Pay section. Benefits: The posting mentions "We offer competitive benefits, professional development opportunities, and a culture that prioritizes work-life balance and continuous improvement." That's benefits info. So Benefits section. Schedule: Not mentioned; no schedule info, so omit. About the role: Could be the mission/opportunity description. We'll put an About the role section summarizing mission and opportunity. Responsibilities: The "What You'll Do" bullet points. Requirements: Could be experience requirements? Usually Requirements separate from Qualifications. But we can combine? The instruction: prefer few substantive sections over many thin ones. We have Experience, Technical Skills, Soft Skills, Bonus Points. Could merge into Requirements and Qualifications and Skills. But we need to follow headings list; we can use only those that have content. Let's decide: - About the role: mission and opportunity. - Responsibilities: What You'll Do. - Requirements: Experience (2+ years in RevOps etc.) maybe also technical skills? But we have separate Skills heading. Could put technical skills under Skills, soft skills under Skills? Actually Skills heading could cover both technical and soft skills. Bonus points could be under Qualifications? Or we could have Qualifications for bonus points. Let's think. We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those with real content. We have: - About the role: yes. - Responsibilities: yes. - Requirements: we have experience requirements (2+ years in revenue operations etc.) plus maybe "Time in a growth-stage company where you built rather than maintained counts for more than years on a résumé." That's experience. So Requirements. - Qualifications: maybe "Strong understanding of GTM metrics..." etc. That's more like qualifications. Could also include technical skills? But we have Skills heading for technical and soft skills. Let's put Qualifications as the bullet list of "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..." etc. That seems like qualifications. - Skills: technical skills (Strong SQL, Deep Salesforce, Hands-on work with LLM tooling, Experience with BI tool and data warehouse) plus soft skills (Analytical and detail-oriented, Clear communication, Track record partnering, Bias for automation, Comfortable operating with urgency, Low ego high ownership). Also bonus points could be under Skills? But bonus points are extra; we could put them under Qualifications as well. However we already used Qualifications for some. Could put bonus points under Qualifications as additional. Or we could create a separate section but not in list; we must only use allowed headings. So we can put bonus points under Qualifications as extra bullet. - Benefits: yes. - Pay: yes (Compensation Range). - Schedule: none -> omit. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Now need to format: headings

then content: either

for prose,

• for lists. We must preserve all substantive information, not invent or summarize away detail. Must not omit details. Need to include all details from the posting, except boilerplate removed. We need to be careful to include all details from sections we keep. Let's extract content. About the role: Should include mission description, values, opportunity description. The posting starts with "Our Mission: Hospital-Quality Care, Everywhere..." then values, then "The Opportunity Verse Medical is hiring a RevOps Analyst / GTM Engineer..." plus description of role halves, selling to health systems, etc. Also includes "This is a hands-on individual contributor role with no team and no backlog waiting for you..." etc. That's part of opportunity. So About the role should include mission, values, opportunity description. We'll combine into prose paragraphs. Responsibilities: The "What You'll Do" section includes bullet-like paragraphs: Pipeline and Forecast Operations (with sub-bullets), CRM, Data, and AI-Native Operations (with sub-bullets), GTM Insights, Assets, and Operating Support (with sub-bullets). We need to turn each bullet into
• . The sub-bullets are sentences starting with verbs. We'll treat each top-level bullet as
• and include its sub-details as part of that
• (maybe as separate sentences). Could also nest
  but not required. Simpler: each top-level bullet as
  • containing the sentences. Requirements: Experience bullet list: "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 two sentences; we can make
    • each. Qualifications: Contains several bullet-like paragraphs: "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...." Also includes technical skills? Actually technical skills separate. We'll keep qualifications as those non-technical/experience items: Strong understanding..., Ownership..., Comfort..., maybe also "Strong understanding of GTM metrics..." etc. Also includes "Strong understanding of GTM metrics, pipeline mechanics, forecast support, CRM hygiene, and sales process discipline." "Ownership of a system end to end. You have been the person accountable for a CRM, a reporting layer, or a GTM data pipeline, not a requester of tickets." "Comfort with ambiguity and no playbook. You will decide what matters most this month." That's three items. Also maybe "Strong understanding of GTM metrics..." etc. We'll treat each as
    • . Also bonus points could be added as extra
    • under Qualifications: "Bonus Points Healthcare, DME, home health, or post-acute experience, or any background modeling a business where the payor, the referrer, and the patient are three different parties. Familiarity with HCPCS, payer mix, or authorization workflows, and how they show up in GTM data. You've built and maintained an agent or automation that a team came to depend on, including the part where you had to fix it when it broke. dbt, Gong's API, or prior work wiring a GTM stack together with code rather than Zapier." That's a block; we can split into multiple
    • maybe each sentence. But we need to preserve all detail; we can keep as one
    • with multiple sentences. Skills: Technical skills bullet list: "Strong SQL. You can write window functions and multi-CTE queries without looking them up, and you know how to sanity-check your own results. Deep Salesforce. Object model, flows, validation rules, reports and dashboards, permissions, with hands in the org. Certification is welcome but not a substitute. Hands-on work with LLM tooling in production, not as a demo: prompting, function calling or MCP, retrieval, and some way of checking whether the output is right. Show us something you shipped. Experience with a BI tool and a data warehouse, and an opinion on what belongs in the warehouse versus the CRM." That's several sentences; we can split each sentence as
    • . Also soft skills: "Analytical and detail-oriented, but practical: you know the goal is better decisions and cleaner execution, not reporting for reporting's sake. Clear communication with non-technical people, and comfort pushing back respectfully when a number doesn't hold up, including when it's a leader's number. Track record partnering across sales, marketing, finance, and product to turn data into decisions. Bias for automation and AI-enabled workflows that save time and improve accuracy, with the judgment to know when the output is wrong. Comfortable operating with urgency and ambiguity. Low ego, high ownership." We'll include those as
    • under Skills as well. Benefits: "We offer competitive benefits, professional development opportunities, and a culture that prioritizes work-life balance and continuous improvement." That's a sentence; we can put in

      . Pay: "Compensation Range: $115K - $145K". Put in

      . Now ensure we don't include any boilerplate: The equal opportunity pledge, accommodation request, etc. Remove. Also remove "Our Mission: Hospital-Quality Care, Everywhere." The mission statement is okay to keep as part of About the role. Now produce HTML fragment. We'll need to wrap sections in

      then content. Let's craft. About the role: We'll have maybe two

      paragraphs: first mission and values, second opportunity. Responsibilities:

      with
      • for each major bullet. We need to be careful to not lose any detail. Let's extract the exact text for each piece. From posting: 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!" Values paragraph: "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." Opportunity paragraph: "The Opportunity Verse Medical is hiring a RevOps Analyst / GTM Engineer. This role is a critical hire as we build out the revenue operations function at Verse. This is one role with two halves. The analyst half answers the questions leadership cannot answer today: where pipeline comes from, where it stalls, and what the forecast actually is. The GTM engineer half builds the systems that stop those questions from being asked again: the Salesforce object