Regional Director (Alaska)
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to convert lists appropriately.
Let's extract content.
About Pear Suite: paragraphs describing company. Could be placed under a heading? Not required but we could include as a
before sections? The instruction: Output ONLY the HTML fragment. It didn't forbid extra paragraphs before headings. But better to include a short intro maybe as
about company? Not required but could be included as part of "About the role"? Actually "About Pear Suite" is separate. Might be okay to include as a
before sections.
But they said "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have headings for those sections only. The company description could be just a
without heading.
Let's structure:
About Pear Suite: ...
About the role
Pear Suite is seeking a Regional Director to lead the development and implementation of community health initiatives across assigned states and regions. This role serves as the primary regional operator responsible for bringing together healthcare providers, community-based organizations, Community Health Workers (CHWs), Tribal health organizations, health plans, government agencies, workforce partners, and other stakeholders to build stronger community-based care ecosystems. The Regional Director will take complex initiatives from concept to implementation, translating Pear Suite's national capabilities into locally responsive programs and partnerships. This includes developing regional relationships, building provider and community networks, launching new programs, coordinating implementation across partners, and identifying sustainable pathways for programs to grow beyond initial grant or pilot funding. This is a highly cross-functional role. The Regional Director will work across Pear Suite's workforce development, community outreach, provider network, operations, product, clinical, impact, sales, and payer teams to ensure that regional initiatives move from strategy into successful execution.
Responsibilities
- Regional Ecosystem Development
- Develop a deep understanding of the healthcare, community health, workforce, and policy landscape across assigned states and regions.
- Build and maintain relationships with CBOs, CHW and CHR programs, Tribal health organizations, healthcare providers, health systems, health plans, government agencies, academic institutions, and workforce partners.
- Identify gaps and opportunities where Pear Suite's technology, provider network, workforce infrastructure, and community partnerships can strengthen regional care delivery.
- Develop regional stakeholder maps and engagement strategies that support Pear Suite's long-term presence and impact.
- Represent Pear Suite at regional meetings, coalitions, conferences, working groups, and community convenings.
- Program Development & Implementation
- Serve as the primary owner for implementation of major regional initiatives, including grant-funded programs, provider network initiatives, workforce programs, telehealth initiatives, and healthcare-community partnerships.
- Translate proposals, contracts, and strategic initiatives into actionable implementation plans with clear milestones, responsibilities, timelines, and performance measures.
- Coordinate partner agreements, onboarding, readiness assessments, implementation activities, and ongoing technical assistance.
- Identify implementation barriers early and coordinate Pear Suite teams and external partners to resolve them.
- Manage multiple initiatives and markets simultaneously while maintaining consistency with Pear Suite's broader operating model.
- Community & Provider Network Development
- Build networks of CHWs, CHRs, CBOs, Tribal organizations, healthcare providers, and other community-based partners within assigned regions.
- Identify and recruit organizations that can participate in Pear Suite programs and provider networks.
- Support partners in progressing from initial engagement through readiness, onboarding, implementation, and long-term participation.
- Coordinate with Pear360 and Network Operations teams on credentialing, compliance, contracting, billing readiness, care coordination, and other operational requirements.
- Help establish relationships between community-based organizations and healthcare partners that create sustainable pathways for community-based care.
- Healthcare & Strategic Partnerships
- Develop relationships with healthcare organizations that can strengthen regional community health infrastructure, including hospitals, FQHCs, rural health clinics, health systems, health plans, and virtual care providers.
- Help design workflows connecting community-based providers with clinical and healthcare partners.
- Identify opportunities for Pear Suite and its community partners to participate in care coordination, population health, value-based care, telehealth, and other emerging delivery models.
- Support leadership and sales teams with strategic regional opportunities while maintaining primary responsibility for ecosystem and program development rather than carrying a traditional sales quota.
- Sustainability & Regional Growth
- Help move successful initiatives from pilot or grant funding toward sustainable operating models.
- Identify reimbursement, health plan, health system, employer, government, and other funding pathways that can sustain community health programs.
- Develop repeatable regional implementation models that can be adapted across multiple states.
- Identify opportunities to expand successful partnerships and programs into additional communities and geographies.
- Provide leadership with recommendations regarding future investment, partnerships, staffing, and expansion within assigned regions.
But note: The instruction: Use - for any list of duties/requirements/benefits, and
for prose. The above nested lists might be okay but we could flatten: each top-level bullet as a duty, and sub-bullets as separate
- maybe? However they said any list of duties/requirements/benefits use
- . Could have nested lists but still okay.
Alternatively we could just list each duty as a
- with the description. Simpler: produce a flat list of responsibilities (the bullet points under each heading). But we need to preserve the grouping? Not required. Could just list all duties as
- . However the headings "Regional Ecosystem Development", etc are section headings within responsibilities; but we already have a Responsibilities heading. Could we keep subheadings as
? Not allowed; only for section headings per instruction? They said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't forbid other headings but to be safe we could avoid extra headings. So we can just make a flat list.
Thus under Responsibilities each duty as - with the full description.
Similarly Qualifications: list each qualification as
- .
Benefits: list each benefit as
- .
Pay: we have compensation range; we can put in
maybe.
Let's extract qualifications:
- 7+ years of experience in healthcare, public health, community health, healthcare operations, Medicaid, population health, community-based care, or a related field.
- Demonstrated experience building partnerships across multiple types of organizations and stakeholder groups, particularly in the region.
- Experience leading complex, multi-partner initiatives from planning through implementation.
- Strong understanding of healthcare delivery and the relationship between healthcare organizations and community-based services.
- Experience working with community-based organizations, CHWs, Tribal organizations, rural healthcare, Medicaid programs, or health plans strongly preferred.
- Ability to operate effectively in environments where programs, policies, partnerships, and operating models are still being developed.
- Strong project and program management skills without requiring highly structured environments.
- Ability to translate strategy into practical workplans and move multiple organizations toward shared objectives.
- Excellent communication, facilitation, relationship-building, and stakeholder-management skills.
- Willingness to travel regularly throughout assigned regions.
Benefits list:
- A mission driven culture that values innovation, collaboration and growth
- Equity: participation in an early-stage company
- Fully Remote
- Unlimited PTO
- Comprehensive Health, dental, and vision insurance
- Health and Wellness Stipend
- Tech Stipend
- Co-working Stipend
- Education and professional development allowance ($1,500 annually)
- Home office setup stipend
Compensation: The salary range for this role is $89,000-$104,000. Plus explanation about compensation range disclosure. We can keep that as prose
.
Now About Pear Suite paragraph: we can include as
before sections.
Now About the role heading: we need a prose summary of role. Could be the paragraph from "About The Role". We'll put that as
under
About the role
.
Now Responsibilities heading: we need to list duties. We'll compile all duties from "What You'll Do" sections (the five categories). We'll flatten.
Let's extract duties from each bullet:
From Regional Ecosystem Development:
- Develop a deep understanding of the healthcare, community health, workforce, and policy landscape across assigned states and regions.
- Build and maintain relationships with CBOs, CHW and CHR programs, Tribal health organizations, healthcare providers, health systems, health plans, government agencies, academic institutions, and workforce partners.
- Identify gaps and opportunities where Pear Suite's technology, provider network, workforce infrastructure, and community partnerships can strengthen regional care delivery.
- Develop regional stakeholder maps and engagement strategies that support Pear Suite's long-term presence and impact.
- Represent Pear Suite at regional meetings, coalitions, conferences, working groups, and community convenings.
Program Development & Implementation:
- Serve as the primary owner for implementation of major regional initiatives, including grant-funded programs, provider network initiatives, workforce programs, telehealth initiatives, and healthcare-community partnerships.
- Translate proposals, contracts, and strategic initiatives into actionable implementation plans with clear milestones, responsibilities, timelines, and performance measures.
- Coordinate partner agreements, onboarding, readiness assessments, implementation activities, and ongoing technical assistance.
- Identify implementation barriers early and coordinate Pear Suite teams and external partners to resolve them.
- Manage multiple initiatives and markets simultaneously while maintaining consistency with Pear Suite's broader operating model.
Community & Provider Network Development:
- Build networks of CHWs, CHRs, CBOs, Tribal organizations, healthcare providers, and other community-based partners within assigned regions.
- Identify and recruit organizations that can participate in Pear Suite programs and provider networks.
- Support partners in progressing from initial engagement through readiness, onboarding, implementation, and long-term participation.
- Coordinate with Pear360 and Network Operations teams on credentialing, compliance, contracting, billing readiness, care coordination, and other operational requirements.
- Help establish relationships between community-based organizations and healthcare partners that create sustainable pathways for community-based care.
Healthcare & Strategic Partnerships:
- Develop relationships with healthcare organizations that can strengthen regional community health infrastructure, including hospitals,
for prose. We need to convert lists appropriately. Let's extract content. About Pear Suite: paragraphs describing company. Could be placed under a heading? Not required but we could include as a
before sections? The instruction: Output ONLY the HTML fragment. It didn't forbid extra paragraphs before headings. But better to include a short intro maybe as
about company? Not required but could be included as part of "About the role"? Actually "About Pear Suite" is separate. Might be okay to include as a
before sections. But they said "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have headings for those sections only. The company description could be just a
without heading. Let's structure:
About Pear Suite: ...
About the role
Pear Suite is seeking a Regional Director to lead the development and implementation of community health initiatives across assigned states and regions. This role serves as the primary regional operator responsible for bringing together healthcare providers, community-based organizations, Community Health Workers (CHWs), Tribal health organizations, health plans, government agencies, workforce partners, and other stakeholders to build stronger community-based care ecosystems. The Regional Director will take complex initiatives from concept to implementation, translating Pear Suite's national capabilities into locally responsive programs and partnerships. This includes developing regional relationships, building provider and community networks, launching new programs, coordinating implementation across partners, and identifying sustainable pathways for programs to grow beyond initial grant or pilot funding. This is a highly cross-functional role. The Regional Director will work across Pear Suite's workforce development, community outreach, provider network, operations, product, clinical, impact, sales, and payer teams to ensure that regional initiatives move from strategy into successful execution.
Responsibilities
- Regional Ecosystem Development
- Develop a deep understanding of the healthcare, community health, workforce, and policy landscape across assigned states and regions.
- Build and maintain relationships with CBOs, CHW and CHR programs, Tribal health organizations, healthcare providers, health systems, health plans, government agencies, academic institutions, and workforce partners.
- Identify gaps and opportunities where Pear Suite's technology, provider network, workforce infrastructure, and community partnerships can strengthen regional care delivery.
- Develop regional stakeholder maps and engagement strategies that support Pear Suite's long-term presence and impact.
- Represent Pear Suite at regional meetings, coalitions, conferences, working groups, and community convenings.
- Program Development & Implementation
- Serve as the primary owner for implementation of major regional initiatives, including grant-funded programs, provider network initiatives, workforce programs, telehealth initiatives, and healthcare-community partnerships.
- Translate proposals, contracts, and strategic initiatives into actionable implementation plans with clear milestones, responsibilities, timelines, and performance measures.
- Coordinate partner agreements, onboarding, readiness assessments, implementation activities, and ongoing technical assistance.
- Identify implementation barriers early and coordinate Pear Suite teams and external partners to resolve them.
- Manage multiple initiatives and markets simultaneously while maintaining consistency with Pear Suite's broader operating model.
- Community & Provider Network Development
- Build networks of CHWs, CHRs, CBOs, Tribal organizations, healthcare providers, and other community-based partners within assigned regions.
- Identify and recruit organizations that can participate in Pear Suite programs and provider networks.
- Support partners in progressing from initial engagement through readiness, onboarding, implementation, and long-term participation.
- Coordinate with Pear360 and Network Operations teams on credentialing, compliance, contracting, billing readiness, care coordination, and other operational requirements.
- Help establish relationships between community-based organizations and healthcare partners that create sustainable pathways for community-based care.
- Healthcare & Strategic Partnerships
- Develop relationships with healthcare organizations that can strengthen regional community health infrastructure, including hospitals, FQHCs, rural health clinics, health systems, health plans, and virtual care providers.
- Help design workflows connecting community-based providers with clinical and healthcare partners.
- Identify opportunities for Pear Suite and its community partners to participate in care coordination, population health, value-based care, telehealth, and other emerging delivery models.
- Support leadership and sales teams with strategic regional opportunities while maintaining primary responsibility for ecosystem and program development rather than carrying a traditional sales quota.
- Sustainability & Regional Growth
- Help move successful initiatives from pilot or grant funding toward sustainable operating models.
- Identify reimbursement, health plan, health system, employer, government, and other funding pathways that can sustain community health programs.
- Develop repeatable regional implementation models that can be adapted across multiple states.
- Identify opportunities to expand successful partnerships and programs into additional communities and geographies.
- Provide leadership with recommendations regarding future investment, partnerships, staffing, and expansion within assigned regions.
- for any list of duties/requirements/benefits, and
for prose. The above nested lists might be okay but we could flatten: each top-level bullet as a duty, and sub-bullets as separate
- maybe? However they said any list of duties/requirements/benefits use
- . Could have nested lists but still okay. Alternatively we could just list each duty as a
- with the description. Simpler: produce a flat list of responsibilities (the bullet points under each heading). But we need to preserve the grouping? Not required. Could just list all duties as
- . However the headings "Regional Ecosystem Development", etc are section headings within responsibilities; but we already have a Responsibilities heading. Could we keep subheadings as
? Not allowed; only
for section headings per instruction? They said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't forbid other headings but to be safe we could avoid extra headings. So we can just make a flat list. Thus under Responsibilities
- each duty as
- with the full description. Similarly Qualifications: list each qualification as
- . Benefits: list each benefit as
- .
Pay: we have compensation range; we can put in
maybe. Let's extract qualifications: - 7+ years of experience in healthcare, public health, community health, healthcare operations, Medicaid, population health, community-based care, or a related field. - Demonstrated experience building partnerships across multiple types of organizations and stakeholder groups, particularly in the region. - Experience leading complex, multi-partner initiatives from planning through implementation. - Strong understanding of healthcare delivery and the relationship between healthcare organizations and community-based services. - Experience working with community-based organizations, CHWs, Tribal organizations, rural healthcare, Medicaid programs, or health plans strongly preferred. - Ability to operate effectively in environments where programs, policies, partnerships, and operating models are still being developed. - Strong project and program management skills without requiring highly structured environments. - Ability to translate strategy into practical workplans and move multiple organizations toward shared objectives. - Excellent communication, facilitation, relationship-building, and stakeholder-management skills. - Willingness to travel regularly throughout assigned regions. Benefits list: - A mission driven culture that values innovation, collaboration and growth - Equity: participation in an early-stage company - Fully Remote - Unlimited PTO - Comprehensive Health, dental, and vision insurance - Health and Wellness Stipend - Tech Stipend - Co-working Stipend - Education and professional development allowance ($1,500 annually) - Home office setup stipend Compensation: The salary range for this role is $89,000-$104,000. Plus explanation about compensation range disclosure. We can keep that as prose
. Now About Pear Suite paragraph: we can include as
before sections. Now About the role heading: we need a prose summary of role. Could be the paragraph from "About The Role". We'll put that as
under
About the role
. Now Responsibilities heading: we need to list duties. We'll compile all duties from "What You'll Do" sections (the five categories). We'll flatten. Let's extract duties from each bullet: From Regional Ecosystem Development: - Develop a deep understanding of the healthcare, community health, workforce, and policy landscape across assigned states and regions. - Build and maintain relationships with CBOs, CHW and CHR programs, Tribal health organizations, healthcare providers, health systems, health plans, government agencies, academic institutions, and workforce partners. - Identify gaps and opportunities where Pear Suite's technology, provider network, workforce infrastructure, and community partnerships can strengthen regional care delivery. - Develop regional stakeholder maps and engagement strategies that support Pear Suite's long-term presence and impact. - Represent Pear Suite at regional meetings, coalitions, conferences, working groups, and community convenings. Program Development & Implementation: - Serve as the primary owner for implementation of major regional initiatives, including grant-funded programs, provider network initiatives, workforce programs, telehealth initiatives, and healthcare-community partnerships. - Translate proposals, contracts, and strategic initiatives into actionable implementation plans with clear milestones, responsibilities, timelines, and performance measures. - Coordinate partner agreements, onboarding, readiness assessments, implementation activities, and ongoing technical assistance. - Identify implementation barriers early and coordinate Pear Suite teams and external partners to resolve them. - Manage multiple initiatives and markets simultaneously while maintaining consistency with Pear Suite's broader operating model. Community & Provider Network Development: - Build networks of CHWs, CHRs, CBOs, Tribal organizations, healthcare providers, and other community-based partners within assigned regions. - Identify and recruit organizations that can participate in Pear Suite programs and provider networks. - Support partners in progressing from initial engagement through readiness, onboarding, implementation, and long-term participation. - Coordinate with Pear360 and Network Operations teams on credentialing, compliance, contracting, billing readiness, care coordination, and other operational requirements. - Help establish relationships between community-based organizations and healthcare partners that create sustainable pathways for community-based care. Healthcare & Strategic Partnerships: - Develop relationships with healthcare organizations that can strengthen regional community health infrastructure, including hospitals,