Community Engagement Liaison

We need to output only 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. Must preserve all substantive info. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines, application instructions, etc. We need to parse the posting and extract sections. Let's identify content: - About us: description of Boulder Care. Could be "About the role"? Actually "About us" is about company. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - About this role: description of role (Community Engagement Liaisons are more than connectors...). That could be "About the role". So we put that under

About the role

with paragraphs. - What you'll do: list of duties (Partnership Growth, Strategic Relationship Management, Data & CRM Management, Community Engagement, Feedback Integration, Collaborate Across Teams). That is responsibilities. So

Responsibilities

with

• items. - What you bring: Requirements (list). Also Preferred but not required. Also maybe "Qualifications" and "Skills". We need to decide. The posting includes: Requirements bullet list: - 3+ years of experience... - Proven track record... - Proficiency with Salesforce... - Ability to travel... - Self-starter... - Excellent interpersonal... - Passionate about serving... - Proven ability to maintain professionalism... Preferred but not required: - Experience within the SUD treatment community... - Experience working with clinical staff... Also there is "Work Environment" describing field-based role, vehicle, remote office, dedicated workspace, expected hours. Also "Expected hours of work": full-time 40 hrs, Mon-Fri standard business hours, flexibility, evenings/weekends as needed. Also "Compensation": pay range $60k-$65k plus $750 vehicle allowance => total cash $69k-$74k, quarterly target performance-based bonus, eligibility for annual performance bonuses. Also "Perks and Benefits": list of benefits. Also "Our values": list of values. Also "A Note About AI in Our Hiring Process": maybe not needed? It's somewhat boilerplate but maybe considered not essential? It's about hiring process; could be considered part of hiring process but we are told to remove application instructions and boilerplate. This note is about AI in hiring process; might be considered boilerplate but it's specific to the company. However instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This note is not exactly those but could be considered part of hiring process. Might be okay to keep? Safer to omit as it's not substantive about role. We'll omit. Also "Hiring Process": 30-minute phone interview, 60-minute video panel interview, Anticipated start date: September/October. That's hiring process details; maybe we could include under a section? Not in allowed headings. Could be omitted as application instructions? It's not exactly instructions but could be considered process. The instruction says remove application instructions. This is about interview steps; could be considered application instructions. Safer to omit. Thus we will include sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. - About the role: we have the paragraph(s) under "About this role". We'll put that. - Responsibilities: the "What you'll do" list. - Requirements: the "Requirements" bullet list (mandatory). Could also include "Preferred but not required" maybe under Qualifications or Skills? We'll treat "Qualifications" as the preferred but not required? Or we could split: Requirements (mandatory) under Requirements heading; Qualifications (preferred) under Qualifications heading; Skills maybe under Skills heading (proficiency with Salesforce, Google Workspace, communication, etc). But we have overlapping. Better: Use Requirements for mandatory experience/skills. Qualifications for preferred but not required. Skills for specific proficiencies (Salesforce, Google Workspace, communication, public speaking, etc). However the instruction says prefer a few substantive sections over many thin ones. So we might combine. We have to use headings only when posting has real specific content. We must not create empty sections. We need to include Pay and Schedule if posting actually states them. Pay: yes, compensation details. Schedule: expected hours of work (40 hrs/week, Mon-Fri, flexibility, evenings/weekends). That's schedule. Benefits: yes, perks and benefits. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Now we need to extract content precisely, preserving all substantive info, not inventing or summarizing away detail. Let's extract each. About the role: The paragraph(s) under "About this role". Let's copy: "Our Community Engagement Liaisons are more than connectors. They are the trusted faces of our mission in the communities we serve and the drivers of our referral partnerships. You will act as a boots-on-the-ground relationship owner, building and strengthening partnerships with healthcare providers, community organizations, reentry systems, and other local stakeholders to expand access to compassionate, harm-reduction-based care. In this role, you will proactively identify and develop new referral opportunities, grow and manage partner relationships, and expand regional networks that connect more people to Boulder Care. You will use enrollment and referral data to guide outreach efforts, demonstrate impact to partners, and continuously improve collaboration and patient access. You will have the autonomy to shape outreach strategies in your region, prioritize your efforts, and independently manage your territory while contributing to broader growth goals. If you are passionate about building meaningful partnerships, driving measurable impact, and working independently in your community, we would love to hear from you." That's the content. Now Responsibilities: "What you'll do" list with subheadings Partnership Growth, Strategic Relationship Management, Data & CRM Management, Community Engagement, Feedback Integration, Collaborate Across Teams. Each has a description. We need to preserve all detail. So we will create
  • for each bullet, and inside each li we can include the subheading as bold? But we cannot add extra tags beyond
    • and

      . The instruction: Use

      • for any list of duties/requirements/benefits, and

        for prose. It doesn't forbid other tags inside li? Probably we can include or similar but safer to just plain text. We'll include the subheading as part of the li text. Thus:

      • Partnership Growth: Identify and build relationships with new referral partners, including healthcare providers, community organizations, treatment programs, and reentry services. Manage partnerships from initial outreach through ongoing engagement to grow referrals and support enrollment goals.
      • Strategic Relationship Management: Nurture and scale existing partnerships. You aren't just a face in the room; you ensure partners remain clinically and philosophically aligned with Boulder’s mission, turning local organizations into long-term, sustainable advocates for our patients.
      • Data & CRM Management: Utilize CRM tools (like Salesforce), referrals, and enrollment data to manage timely follow-ups, track activity, conversion rates from referral to patient, and ROI on partnership outreach. You will be expected to uncover insights into your own performance, including analyzing which partner types yield the highest patient conversion and adjusting your weekly strategy accordingly.
      • Community Engagement: Spend most of your time in the field building relationships with healthcare providers, community organizations, and advocates. Identify local needs, address barriers to care, and educate partners about Boulder Care’s services and harm-reduction approach.
      • Feedback Integration: Collect and analyze feedback from community partners to refine Boulder’s referral strategies and products. Help develop and build solutions for existing referral barriers.
      • Collaborate Across Teams: Work closely with Boulder’s marketing, commercial, clinical, product, and operations teams to develop and execute 6–12-month regional or statewide outreach plans, aligning messaging, resources, and growth priorities.
      Now Requirements: The bullet list under "Requirements". Let's extract exactly: - 3+ years of experience in community outreach, business development or sales, or referral management within healthcare, hospital systems, or behavioral health settings - Proven track record of building and growing referral relationships and driving patient or partner growth through sustained engagement - Proficiency with Salesforce or similar CRM tools and Google Workspace (Docs, Sheets, Gmail, etc.) - Ability to travel locally with reliable transportation and valid drivers license ~4 days/week for meetings with partners - Self-starter with the ability to take initiative and work autonomously while managing multiple priorities - Excellent interpersonal and communication skills, including strong public speaking abilities, demonstrating empathy and a patient-first/client-first mindset - Passionate about serving marginalized and vulnerable populations - Proven ability to maintain professionalism and confidentiality when working with sensitive and confidential information We'll put each as
      • . Now Qualifications: The "Preferred but not required" list: - Experience within the SUD treatment community, with existing relationships in this space - Experience working with clinical staff, healthcare administration staff, and people with opioid use disorders We'll put under Qualifications. Now Skills: Could be overlapping with Requirements (proficiency with Salesforce, Google Workspace, communication, public speaking). But we already have those in Requirements. Perhaps we can treat Skills as the specific proficiencies: Salesforce, Google Workspace, communication, public speaking, etc. But to avoid duplication, maybe we combine Requirements and Skills into one section? However instruction says we can have multiple sections but prefer few substantive sections. We have many sections already; maybe we can merge Requirements and Qualifications into one "Requirements" and have Skills separate? But we already have Requirements as mandatory; Qualifications as preferred; Skills maybe not needed. We could decide to omit Skills section if content overlaps heavily with Requirements. But we need to include a section only when posting has real specific content for it. The posting does mention proficiency with Salesforce or similar CRM tools and Google Workspace, excellent interpersonal and communication skills, strong public speaking abilities. Those are skills. So we could have a Skills section containing those items. However they are already in Requirements list. To avoid duplication, we could split: Requirements (experience, track record, ability to travel, self-starter, passionate, confidentiality). Skills (Salesforce, Google Workspace, communication, public speaking). Qualifications (preferred). That would avoid duplication. Let's extract: From Requirements list, we can separate: Experience/background items: - 3+ years of experience in community outreach, business development or sales, or referral management within healthcare, hospital systems, or behavioral health settings - Proven track record of building and growing referral relationships and driving patient or partner growth through sustained engagement - Self-starter with the ability to take initiative and work autonomously while managing multiple priorities - Passionate about serving marginalized and vulnerable populations - Proven ability to maintain professionalism and confidentiality when working with sensitive and confidential information Skills items: - Proficiency with Salesforce or similar CRM tools and Google Workspace (Docs, Sheets, Gmail, etc.) - Excellent interpersonal and communication skills, including strong public speaking abilities, demonstrating empathy and a patient-first/client-first mindset - Ability to travel locally with reliable transportation and valid drivers license ~4 days/week for meetings with partners (maybe this is more of a requirement than skill). Could be considered a requirement. But we need to preserve all info; we can just keep Requirements as all mandatory items, and Qualifications as preferred, and maybe not have Skills separate. However the instruction says we should use headings like Skills if there is content. If we omit Skills, that's fine as long as we don't create a heading with filler. So we can omit Skills section. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We