Head of Pharmacy Success

We need to output HTML fragment with headings

for 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: EEO, legal, etc. Must preserve all substantive info. We need to parse the posting. Key sections: - Location: Nashville, TN (hybrid) or Remote - Reports to: COO - Type: Full-time These are metadata; we can put in a short

maybe. - The Role: description paragraph. - What You Own: list of responsibilities (bulleted). This is responsibilities. - What Success Looks Like: maybe also responsibilities or outcomes; could be part of responsibilities or separate? Could be "Success metrics". Might be considered part of responsibilities or maybe a separate section like "What Success Looks Like" but not in allowed headings. Allowed headings are limited to those list. We can map content to those headings: About the role (intro), Responsibilities (What You Own + maybe What Success Looks Like?), Requirements (Background etc), Qualifications (maybe overlapping), Skills (specific abilities), Benefits (none explicit), Pay (Compensation), Schedule (maybe Type: Full-time). Also we have "Compensation" section. We need to decide what goes where. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not create sections with filler. So we need to see if we have content for each. - About the role: we have introductory paragraph: "The Role VITL’s marketplace only works when the pharmacy side works..." That's about the role. So we can put that under

About the role

as a

. - Responsibilities: we have "What You Own:" list of items (Operating Pharmacy agreements, Pharmacy onboarding, Network coverage, Pharmacy integration, Pricing oversight, Customer Support Network performance, Escalation triage, Performance reviews, Admin / Finance Charge validation, VITL catalog management, Compliance record, Building Pharmacy Digest, Pharmacy-success playbook, Capacity planning). Also "What Success Looks Like" could be considered responsibilities outcomes; but we could include as part of responsibilities or maybe separate but not allowed. We'll include those bullet points under Responsibilities. - Requirements: we have "What You Bring" background statements: background in marketplace supply-side OR compounding pharmacy operations, working knowledge, experience holding partners to agreements, fluency with operational data, familiarity with cash-pay compounding space, comfort partnering with Product and Engineering. Those are requirements/qualifications. We need to split into Requirements and Qualifications and Skills maybe. We could treat "What You Bring" as Requirements (background) and Qualifications (specific knowledge) and Skills (operational data fluency, familiarity, comfort partnering). But we need to avoid duplication. Better: Requirements: background in marketplace supply-side OR compounding pharmacy operations (or both). Qualifications: working knowledge of compounding pharmacies produce, price, ship; experience holding partners to commercial agreements; familiarity with cash-pay compounding space. Skills: fluency with operational data; comfort partnering with Product and Engineering; strong follow-through, documentation habits. But we need to ensure we don't invent content not present. All these are present. We also have "Compensation" section: base salary range competitive, performance-based incentives, benefits, company options. That's Pay. We have "Type: Full-time" which is Schedule? Actually Schedule could be full-time, hybrid/remote. We'll put Schedule: Full-time (hybrid/remote). Or we could put location under About the role? But we have location metadata separate. We have "Reports to: COO" maybe not needed. We need to include location and reports maybe in a short

under About the role or separate? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include location, reports, type in a short paragraph. Thus we can have a

at top: "Location: Nashville, TN (hybrid) or Remote • Reports to: COO • Type: Full-time". That's minor metadata. Then sections. Now Benefits: The posting mentions "total compensation may include performance-based incentives, benefits and company options." That's vague but mentions benefits. It does not detail specific benefits (health, 401k). It's still a mention of benefits. Should we create Benefits section? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It states "benefits" generically. So we can include a Benefits section with that statement. However we must avoid filler like "not specified". We have a statement: "total compensation may include performance-based incentives, benefits and company options." That's enough to create a Benefits section: we can put that as a

under Benefits. Pay: we have base salary range competitive, determined based on skills, experience, location. Plus performance-based incentives, benefits, company options. That's Pay. Schedule: we have Type: Full-time (hybrid/remote). So we can put Schedule section. Now we need to ensure we don't repeat content across sections unnecessarily but it's okay. Let's craft HTML. Structure:

Location: Nashville, TN (hybrid) or Remote • Reports to: COO • Type: Full-time

About the role

The Role VITL’s marketplace only works when the pharmacy side works. The Head of Pharmacy Success owns that side — the 503A and 503B compounding pharmacy network that fills every clinic order. You are accountable for whether an order ships on time, correctly, and from a pharmacy that is licensed, compliant, and priced to win. The role covers contract enforcement, SLA accountability, ongoing pricing management, billing, formulary, escalations, and pharmacy-facing product. When something breaks, you fix it. This is a senior IC role with a mandate to build the pharmacy-success function — not just run it. We’re open to candidates from marketplace supply-side operations, compounding pharmacy operations, or both. The overlap is where the best candidates live.

Responsibilities

• Operating Pharmacy agreements — own and enforce contracts: SLA commitments, participation terms, and commercial pricing
• Pharmacy onboarding — verify licensure and multi-state authority, confirm USP // status, load formulary and pricing, validate test orders before go-live
• Network coverage — identify gaps by medication, dosage form, and geography; recruit or activate capacity to close them
• Pharmacy integration — serve as the primary bridge between VITL's platform and pharmacy systems; partner with Product and Engineering to streamline order management, formulary syncing, reporting, and logistics workflows between the two sides
• Pricing oversight — continuously monitor pharmacy-side pricing against market rates, volume benchmarks, and competing sources; persistently push partners to lower prices as volume grows and market conditions shift
• Customer Support Network performance — set fulfillment standards, track fill rates and response times, publish that data on the platform as the accountability lever, and intervene before clinics feel it
• Escalation triage — own resolution for delayed, cancelled, misfilled, or quality-flagged orders; coordinate pharmacy, clinic, and CS to a fast outcome and file tickets to prevent recurrence
• Performance reviews — routine check-ins and quarterly QBRs with strategic partners using shared scorecards
• Admin / Finance Charge validation — validate all pharmacy charges against agreed pricing; catch errors and overcharges before they hit the books
• VITL catalog management — own formulary changes: new products, reformulations, dosage-form updates, and discontinuations; keep the platform catalog accurate
• Compliance record — maintain current licenses, credentials, COAs, and documentation in partnership with Compliance Function
• Building Pharmacy Digest — weekly digest to partners covering network performance, formulary updates, and platform changes
• Pharmacy-success playbook — onboarding checklists, performance scorecards, and review cadences that let the network scale without headcount scaling with it
• Capacity planning — work with high-volume partners so the network scales ahead of clinic growth, not behind it

What Success Looks Like

Not allowed heading. We could incorporate into Responsibilities or maybe a separate section like "Outcomes". But not allowed. We could add bullet points under Responsibilities about success metrics. However the instruction: "Prefer a few substantive sections over many thin ones." We could add a short paragraph under Responsibilities about success metrics. But we already have a list of responsibilities; we could add a

after the list describing success metrics. That would be part of Responsibilities section. Let's do that: after the

, add a

outlining success metrics. Thus under Responsibilities we will have the list then a

:

Success looks like: high fill rates, low cancellations, turnaround times that hold as volume grows; no coverage gaps — always a compliant, competitively priced pharmacy ready to fill; new pharmacies reach their first clean, on-time order fast and predictably; underperformance is caught early; chronic underperformers are remediated or offboarded before clinics feel it; the network is audit-ready at all times; billing matches what was agreed — clean reconciliation, no surprises.

That preserves content. Now Requirements: background in marketplace supply-side OR compounding pharmacy operations (or both). We'll put as

.

Requirements

Background in marketplace supply-side operations (vendor/partner network ownership, SLA enforcement, pricing, coverage management) OR compounding pharmacy operations (503A/503B, formulary, USP compliance, network management for a telehealth or DTC platform) — ideally both.

Qualifications: working knowledge of compounding pharmacies produce, price, ship — 503A vs. 503B distinctions, USP // standards, dosage forms, compliance requirements; experience holding partners to commercial agreements and pricing commitments; familiarity with the cash-pay compounding space — GLP-1s, NAD+, peptides, IV wellness — and how market dynamics affect pharmacy pricing and availability. We'll put as

.

Qualifications

Working knowledge of how compounding pharmacies produce, price, and ship — 503A vs. 503B distinctions, USP // standards, dosage forms, and the compliance requirements that govern each facility type; comfort navigating state board of pharmacy requirements, accreditation standards, and the documentation expectations that keep a pharmacy network audit-ready. Experience holding partners to commercial agreements and pricing commitments — enforcing what was agreed and pushing back when they drift. Familiarity with the cash-pay compounding space — GLP-1s, NAD+, peptides, IV wellness — and how market dynamics affect pharmacy pricing and availability.

Skills: fluency with operational data — you can read a fulfillment dashboard, spot the problem pharmacy, and know what to do about it; comfort partnering with Product and Engineering as a domain expert; strong follow-through across many partners with clean documentation habits.

Skills

Fluency with operational data — you can read a fulfillment dashboard, spot the problem pharmacy, and know what to do about it. Comfort partnering with Product and Engineering as a domain expert; strong follow-through across many partners with clean documentation habits.

Benefits: total compensation may include performance-based incentives, benefits and company options.

Benefits

Total compensation may include performance-based incentives, benefits and company options.

Pay: base salary range competitive, determined based on candidate’s relevant skills, experience, and geographic location. In addition to base pay, total compensation may include performance-based incentives, benefits and company options. We already mentioned benefits