Senior Associate, Community Partnership Operations

We need to output HTML fragment with sections: About the role? Actually the posting includes "About The Team", "About The Role", "What You'll Do", "What We're Looking For", "Ophelia Compensation Overview", "Compensation Range". Also maybe "Benefits"? Not present. "Pay" is present (Compensation Range). "Schedule" not present. So we include sections only if content present. We must not repeat job title as heading. No Job ID. Remove boilerplate like application instructions, note before applying, etc. Also remove "Interested in learning more... Apply to work with us!" and "A Note Before Applying". Also remove cookie/navigation/legal/EEO etc (none present). Keep substantive info. We need headings:

for section headings: e.g., About the team, About the role, What you'll do, What we're looking for, Compensation overview, Compensation range? Actually "Compensation Overview" and "Compensation Range" could be combined under Pay section? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map to those generic headings where appropriate. But we can also use specific headings like "About the Team" etc. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those headings, but we can also use other headings if they match content? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those exact headings when applicable. However the posting has sections like "About The Team", "About The Role", "What You'll Do", "What We're Looking For", "Ophelia Compensation Overview", "Compensation Range". We need to map to allowed headings: About the role (maybe combine About The Team and About The Role?), Responsibilities (What You'll Do), Requirements/Qualifications/Skills (What We're Looking For), Pay (Compensation Overview and Range). Benefits not present. Schedule not present. We should not invent sections. So we can have:

About the role

(maybe include both About The Team and About The Role content). But we need to preserve all substantive information. If we combine, we must not lose info. Could put both under About the role heading. Then

Responsibilities

for What You'll Do. Then

Requirements

for What We're Looking For (maybe split into Requirements and Skills? but we can just put all under Requirements). Or we could have Requirements and Skills separate but not needed. Then

Pay

for Compensation Overview and Compensation Range. We must not include filler like "commensurate with experience". Not present. We must output only HTML fragment, no /, no markdown fences. Let's extract content. About The Team: "Ophelia's Community Partnership Managers (CPMs) are the boots-on-the-ground function of our B2B growth strategy, building and managing relationships with community-based organizations, health systems, payors, and correctional facilities who refer patients into Ophelia's care. The team has grown from 3 CPMs in January 2026 to 10+ today, expanding across Pennsylvania, New Jersey, and New York, with additional markets on the horizon. Each CPM owns a territory end-to-end (sourcing new partnerships and managing existing ones) and the team as a whole has driven steady, organic growth in patient referral volume as it's scaled." About The Role: "Team growth has outpaced the operational support model built for a much smaller team. We need someone who can absorb the recurring, high-volume work that currently sits with the Sr. Director of Partnerships (e.g., 1:1 action items across a growing team, playbook upkeep, CRM hygiene, and fast-turnaround data requests) so that CPMs have the support to maximize their impact in the field. This role is ideal for someone who's equally comfortable being the project manager to chase down loose ends and the analyst who can pull an insightful dataset to guide decision making. You'll work directly with the Sr. Director of Partnerships and touch every part of the CPM function." What You'll Do (Responsibilities): List: - Execution & Follow-Through - Request Ownership: Drive action items from the Sr. Director's weekly CPM and cross-functional meetings, plus other one-off needs from the team, end-to-end. - Collateral Management: Curate the team's partner-facing collateral library (e.g., organizing existing materials, flagging what's outdated, and making light updates directly). - Tracking & Visibility: Maintain a single running log across 10+ reps' worth of requests so nothing falls through the cracks. - Playbook Ownership & Documentation - Playbook Upkeep: Own the weekly review cycle for the CPM playbook; keeping it accurate and structuring new content as the team scales into new markets. - Source of Truth: Maintain it as the team's genuine source of truth, not just a reference doc. - Data, Analytics & Systems Ownership - Ad Hoc Analysis: Pull and analyze large datasets from BI tools (e.g., Lightdash) and Google Sheets to answer one-off questions - Dashboard Monitoring: Monitor existing dashboards for accuracy and flag anomalies. - CRM & Data Hygiene: Own CRM cleanup and data hygiene (such as deduplicating records, fixing mis-tagged accounts, and keeping partner/referral data reliable). - Data & Product Request Management: Manage the intake and lifecycle of data and product requests from CPMs and the Sr. Director, acting as the point of contact with data/engineering through to resolution. - Skill Growth: Over time, partner with the data team on more complex analyses and grow into owning dashboards directly. What We're Looking For (Requirements/Skills): Paragraph: "2-4+ years of operations/data experience in operations, business analysis, or a similar analytical role.Comfortable with ambiguity: In this role, you'll often start with a vague ask and need to dig, talk to people, and scope it yourself. Independent operator: Can run a system — a tracker, a dataset, a playbook — end-to-end with minimal oversight.Data fluency: Strong Excel/Google Sheets skills (e.g. pivot tables, VLOOKUP) and comfort pulling and structuring large datasets in BI tools (Lightdash, Looker, Tableau, or similar).Stakeholder coordination: Turns vague asks into well-scoped requests and follows through to resolution.Data-driven execution: Uses data to flag anomalies and spot gaps — not just report numbers, but catch what's wrong with them.Clear communicator: Translates between CPM field needs, data/engineering priorities, and Sr. Director calls to keep things moving without constant check-ins.Growth mindset: Curious and eager to learn new tools and workflows; captures what you learn so the team benefits.Mission-driven: Passionate about improving access to care for underserved populations." Preferred bullet list: - High-growth healthtech startup experience preferred. - Exposure to OUD/SUD treatment, behavioral health, or healthcare operations - Experience with CRM systems and data hygiene/cleanup work. - Sales or pipeline management experience (directly or indirectly) – a plus but not required! Compensation Overview: Paragraph: "We set compensation based on the level and skills required for the role. We value pay transparency and equity, and are committed to fair pay. In order to prevent pay disparities and reduce time spent in negotiations, we take a “first and best” offer approach: this means we’re not holding any compensation back from our candidates, and you can feel confident that our pay is fair and does not vary based on the strength of someone’s negotiation skills.Compensation is dynamic at Ophelia: as long as the company performs well and meets our targets, there will be opportunities for increased compensation annually. We’re happy to discuss this approach and our bands if you have questions during the interview process." Compensation Range: "$85,000 - $95,000 USD" We should not include "Interested in learning more..." etc. Now produce HTML. We'll have:

About the role

... combine About The Team and About The Role ...

Responsibilities

• ... each bullet maybe with subbullets? We can keep simple
• with the content. For subpoints we could embed
  • inside but not required. We'll keep as
  • with the description. We need to preserve all substantive info. We'll include the headings inside li maybe as bold? Not needed but we can keep plain text. We'll produce something like:
  • Execution & Follow-Through
    • Request Ownership: Drive action items from the Sr. Director's weekly CPM and cross-functional meetings, plus other one-off needs from the team, end-to-end.
    • Collateral Management: Curate the team's partner-facing collateral library (e.g., organizing existing materials, flagging what's outdated, and making light updates directly).
    • Tracking & Visibility: Maintain a single running log across 10+ reps' worth of requests so nothing falls through the cracks.
  Similarly for other sections. But we must ensure we don't add extra headings beyond h3. Using inside li is fine. Now Requirements section: we can have

  Requirements

  ... paragraph ...

  then maybe

  Preferred Qualifications

  but not in allowed list. Could combine under Requirements as well. But we could add a separate

  Skills

  if we want. The instruction allows Skills heading. So we could split: Requirements (experience, etc.) and Skills (specific competencies). But we have a lot of bullet-like sentences in the paragraph. Might be easier to keep as one

  Requirements

  with paragraph and then a
  for preferred. But we need to avoid creating headings with filler. Preferred qualifications is real content, so we can have a heading like "Preferred Qualifications". Not in the example list but maybe allowed? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So Qualifications and Skills are allowed headings. So we can use

  Qualifications

  for the main requirements, and

  Skills

  for the preferred list? Or we could put all under Qualifications. But we have both "What We're Looking For" which includes both required and preferred. Could split: Qualifications (required) and Skills (preferred). Let's do that. Thus:

  Qualifications

  2-4+ years of operations/data experience in operations, business analysis, or a similar analytical role.Comfortable with ambiguity: In this role, you'll often start with a vague ask and need to dig, talk to people, and scope it yourself. Independent operator: Can run a system — a tracker, a dataset, a playbook — end-to-end with minimal oversight.Data fluency: Strong Excel/Google Sheets skills (e.g. pivot tables, VLOOKUP) and comfort pulling and structuring large datasets in BI tools (Lightdash, Looker, Tableau, or similar).Stakeholder coordination: Turns vague asks into well-scoped requests and follows through to resolution.Data-driven execution: Uses data to flag anomalies and spot gaps — not just report numbers, but catch what's wrong with them.Clear communicator: Translates between CPM field needs, data/engineering priorities, and Sr. Director calls to keep things moving without constant check