We need to output HTML fragment with sections: About the role (already present), Responsibilities, Requirements/Qualifications/Skills (we need to parse what is in posting). The posting includes "What We Do" (intro), "About the Role", "Key Responsibilities", "What You Bring", "Core Values", "What to expect from working at Roo!" (benefits). Also pay ranges given. Also schedule? Not mentioned. So we need sections: About the role (but rule says do NOT repeat the job title as a heading; but we can have About the role heading). The posting already has "About the Role" heading; we should keep that as
About the Role
and then paragraph(s). Then Responsibilities: from "Key Responsibilities". Then Requirements: from "What You Bring". Possibly also Skills? Could combine. Benefits: from "What to expect from working at Roo!" (list). Pay: from compensation ranges. Schedule: not present, so omit. Also we need to include metadata like Job ID? Not present. Remove boilerplate: cookie/navigation/legal/EEO etc. At end there is EEO statement and scam warning etc; we need to remove those. Also remove "What We Do" maybe? It's introductory but not a section heading; we could keep as a
before About the Role? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we should only include those sections when there is real content. The "What We Do" is not one of the listed headings; we could either omit or treat as a
before sections. Probably better to keep it as a
introductory paragraph. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can keep "What We Do" as a
. Also "Core Values" maybe not a standard heading; but we could include as a section? Not in list; maybe we can omit or treat as
. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we skip Core Values. Benefits section we have. Pay section we have. Responsibilities and Requirements sections we have. About the role we have. So final HTML:
What We Do ...
About the Role
... (the paragraph after About the Role)
Responsibilities
- ... each responsibility line
Requirements
- ... each bullet from What You Bring
Benefits
Pay
... compensation tiers
We must preserve all substantive information; not invent or summarize away detail. So we need to copy the text exactly as given (maybe minor formatting). For responsibilities, we need to break each sentence after period? The responsibilities list is a paragraph with many sentences separated by periods. We should convert each sentence into a
. Ensure we keep all content. Let's extract responsibilities text:
"Own the integrated revenue strategy tied to company goals and unit economics.Design the coverage/territory/segment model across the revenue org (roles, handoffs, specialization, capacity).Allocate headcount and budget by ROI and constraints, maintaining a healthy cost of sales as you grow. Rebalance quickly when necessary.Build the operating cadence that makes forecast accuracy and quota attainment the default.Scale repeatable GTM playbooks across segments while preserving segment nuance.Build an enablement engine (messaging, objection handling, discovery, onboarding, ongoing coaching).Implement QA loops (call scoring, pipeline hygiene, deal reviews) with a clear iteration rhythm.Build a high-bar leadership bench and org design that scales (spans/layers/specialization).Set hiring rubrics and enforce the bar; build a coaching culture and accountability.Set performance standards and upgrade talent decisively—without destroying morale (consistent calibration, early underperformance plans, fast hard calls, keep top talent energized and growing).Own org-level capacity planning that maximizes ROI; drive org-wide clarity on definitions and leading indicators.Own the GTM systems architecture (CRM + tooling) with disciplined build-vs-buy judgment.Drive thoughtful automation that removes toil, enforces standards, and comes with real adoption plans.Align Product, Marketing, Finance, and Data around top revenue bets; secure resourcing for priorities and resolve tradeoffs quickly. Ensure opportunities are framed in a shared metrics backbone across functions—principled, not political.Lead major org/process/comp transformations while maintaining performance—protect the quarter while upgrading the machine."
We need to split at periods. Note some sentences have semicolons inside; but we treat each sentence ending with a period as separate item. Some sentences have no period at end? The last ends with a period. We'll split.
Let's list them:
1. Own the integrated revenue strategy tied to company goals and unit economics.
2. Design the coverage/territory/segment model across the revenue org (roles, handoffs, specialization, capacity).
3. Allocate headcount and budget by ROI and constraints, maintaining a healthy cost of sales as you grow.
4. Rebalance quickly when necessary.
5. Build the operating cadence that makes forecast accuracy and quota attainment the default.
6. Scale repeatable GTM playbooks across segments while preserving segment nuance.
7. Build an enablement engine (messaging, objection handling, discovery, onboarding, ongoing coaching).
8. Implement QA loops (call scoring, pipeline hygiene, deal reviews) with a clear iteration rhythm.
9. Build a high-bar leadership bench and org design that scales (spans/layers/specialization).
10. Set hiring rubrics and enforce the bar; build a coaching culture and accountability.
11. Set performance standards and upgrade talent decisively—without destroying morale (consistent calibration, early underperformance plans, fast hard calls, keep top talent energized and growing).
12. Own org-level capacity planning that maximizes ROI; drive org-wide clarity on definitions and leading indicators.
13. Own the GTM systems architecture (CRM + tooling) with disciplined build-vs-buy judgment.
14. Drive thoughtful automation that removes toil, enforces standards, and comes with real adoption plans.
15. Align Product, Marketing, Finance, and Data around top revenue bets; secure resourcing for priorities and resolve tradeoffs quickly.
16. Ensure opportunities are framed in a shared metrics backbone across functions—principled, not political.
17. Lead major org/process/comp transformations while maintaining performance—protect the quarter while upgrading the machine.
Now Requirements from "What You Bring":
Text:
"Proven Sales Leadership: Marketplace sales experience (or B2B SMB & Mid-market - services with a quota-carrying motion.Executive Presence + Clarity: crisp communicator with board-ready narrative discipline; high-integrity, no-spin, credible variance explanations.Genius-Maker: known for developing strong team - hiring great talent, upgrading fairly and quickly, and building a coaching culture that lifts performance.Rigor: track record of building accurate forecasting, measured motions, clean pipelines and a systematic approach.Data + Unit Economics Orientation: comfortable tying decisions to metrics without losing the plot on growth.Cross-functional Leadership: strong partner to Product/Marketing/Finance/Data; you can resolve tradeoffs, earn trust, and drive alignment around shared metrics. While we are a remote first company, if you are based in San Francisco this will be a hybrid role. Please see below for compensation ranges based on our geographical tiering system recommended by external benchmark data (with example cities listed). Note: We’ve recently been made aware of a job scam where scammers are posing as Roo employees and conducting fake text interviews. Please note that any communication from @lifeatroo.com is not legitimate. All official Roo communication will always come from @roo.vet. Exact compensation may vary based on skills, experience, and location."
We need to extract the requirements bullets. The section seems to have headings like "Proven Sales Leadership:", "Executive Presence + Clarity:", etc. We should treat each as a bullet. Also the later sentences about remote first etc are not requirements; they are notes. We should keep them maybe as a separate paragraph? But they are not part of requirements; they are more about role location and compensation note. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep that info somewhere. Could be placed under a separate section like "Additional Information" but not in allowed headings. Perhaps we can incorporate into About the Role or a after Requirements. Since we cannot create new headings not in list unless we have real content; but we could put them as a
after Requirements (like a note). The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could add a Additional Information
but that's not in the example list; maybe better to avoid extra heading and just put as a
. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; other headings maybe not allowed. Safer to stick to those headings only. So we need to fit the extra info into existing sections: maybe under About the Role (as a paragraph) or under Requirements (as a note). The remote first note and compensation note are not exactly requirements but could be placed under About the Role as additional context. However the About the Role already has a paragraph; we could append that info as another
after the About the Role paragraph but before Responsibilities. That would be okay: it's not a heading, just a paragraph.
Thus we will have:
What We Do ...
About the Role
Roo Veterinary is building the modern labor marketplace and operating system for veterinary care. We help hospitals reliably staff shifts and access great veterinary professionals, so care happens when it’s needed, without burning out teams. We’re hiring a VP of Sales to lead our efforts at building a high-performing sales organization and enhancing the sales culture of the company. Reporting directly to the CEO and serving as a key member of the management team, you’ll be accountable for growth on both sides of the marketplace, activating new hospitals and new providers (veterinarians and technicians) and growing volume through deepening provider engagement with Account Management programs
While we are a remote first company, if you are based in San Francisco this will be a hybrid role. Please see below for compensation ranges based on our geographical tiering system recommended by external benchmark data (with example cities listed). Note: We’ve recently been made aware of a job scam where scammers are posing as Roo employees and conducting fake text interviews. Please note that any communication from @lifeatroo.com is not legitimate. All official Roo communication will always come from @roo.vet. Exact compensation may vary based on skills, experience, and location.
Then Responsibilities ul.
Then Requirements: we need to list each bullet from What You Bring. Let's extract each heading and its description.
The text:
"Proven Sales Leadership: Marketplace sales experience (or B2B SMB & Mid-market - services with a quota-carrying motion.Executive Presence + Clarity: crisp communicator with board-ready narrative discipline; high-integrity, no-spin