Provider Partnerships Associate (Territory Sales)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate. Must preserve all substantive info. We need to parse the posting. Key parts: - About Us (mission etc) – not needed as a section? The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should include only those sections if content exists. "About Us" is not one of the allowed headings, so we should not output it. Probably we can omit it entirely. - About The Role: we have content. So we need an

About the role

then a

with that prose. - Key Responsibilities: list bullet points. So

Responsibilities

then

• ... each bullet. - About You: includes qualifications/skills etc. We need to split into Requirements, Qualifications, Skills maybe. The posting includes bullet-like list: "You’d be a great fit here if you are:" then list of traits. Then "We’d Love to Hear From You If You Have" list of experience/skills. Also "Healthcare sales experience is helpful, but not required." etc. We need to map to sections: Requirements, Qualifications, Skills. The instruction: prefer few substantive sections over many thin ones. We could combine Requirements and Qualifications into one? But we need to follow headings list; we can include only those with real content. Let's see: - Requirements: maybe the "If You Have 1–3 years of experience..." etc. That's requirements. - Qualifications: maybe the traits like competitive, motivated, etc. Could be qualifications. - Skills: maybe communication, relationship-building, organizational skills, Salesforce experience. We could create three sections. But we must not create sections with filler like "not specified". All content we have is specific. - Benefits: we have list: Competitive base salary + uncapped monthly variable compensation, Clear path for growth..., Mission-driven work..., High-autonomy..., Supportive leadership..., Mileage reimbursement..., $65/month cell phone reimbursement, $125/quarter work-from-home stipend, Company card..., Comprehensive medical, dental, and vision coverage. Also maybe "More information The Nourish Bar Our Values How We Work Comp Philosophy" is boilerplate? Probably ignore. - Pay: The posting mentions "Competitive base salary + uncapped monthly variable compensation". That's pay info. Should we create a Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation, so we could include Pay. However we also have Benefits section that includes compensation? Might be overlapping. Better to separate: Pay section for base salary + variable comp. Benefits section for other benefits (reimbursements, stipends, insurance). The instruction says prefer few substantive sections over many thin ones. But we have both Pay and Benefits content; we could combine them into Benefits? But Pay is specifically about compensation. The instruction says include a section ONLY when posting has real, specific content for it. It does have compensation details, so we could include Pay. However we also have benefits details. Could we put compensation under Benefits? The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't forbid combining them, but we have headings list includes Pay and Benefits separate. Safer to include both if content exists. - Schedule: The posting mentions "Please note: This is a full-time field-based role and candidates must be located in Sarasota, FL." Also "Spend 5 days per week in the field". That's schedule info (full-time, 5 days/week). So we can include Schedule section. 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 paragraph: "As a Provider Partnerships Associate (PPA), you’ll help grow a provider referral territory by building strong partnerships with healthcare providers and their teams. This is a field-based sales role focused on driving patient referrals to Nourish through relationship-building, strategic territory growth, and consistent in-person engagement. You’ll spend the majority of your time in the field meeting with primary care physicians, specialists, medical assistants, office managers, and healthcare administrators; building trust, growing referral volume, and helping more patients access insurance-covered nutrition care. This role combines relationship-building, new business development, and long-term account growth. Success comes from creating strong relationships, maintaining momentum within accounts, and consistently growing your territory over time. This is a great opportunity for someone earlier in their sales career who is excited to learn how to build and grow a territory in a fast-paced healthcare environment. You’ll report directly to a Provider Partnerships Regional Manager and join a fast-growing, high-performance team focused on transforming healthcare through better nutrition access." We need to keep that as prose in

  . Responsibilities bullet list: From "Key Responsibilities" list: - Own and grow a provider referral territory within your local market - Spend 5 days per week in the field meeting with healthcare providers and clinic staff within an approximately 1-hour driving radius - Build relationships with physicians, specialists, medical assistants, office managers, and healthcare administrators - Prospect into new offices and create referral partnerships from the ground up - Grow referral volume within existing accounts through strong relationship management, consistent follow-up, and strategic territory planning - Become a trusted resource to providers by educating them on Nourish and the impact nutrition care can have on patient outcomes - Drive toward monthly referral goals and performance targets - Manage your territory like it’s your own business, balancing new business development with long-term account growth - Track activity, pipeline, and account performance in Salesforce - Partner closely with leadership and teammates to share learnings, improve processes, and help scale the organization We need each as

• . Now Requirements: from "We’d Love to Hear From You If You Have" list: - 1–3 years of experience in sales, customer-facing roles, healthcare, hospitality, recruiting, athletics, or other high-performance environments - A track record of hitting goals, competing, or outperforming expectations - Strong communication and relationship-building skills - A high level of coachability, curiosity, and willingness to learn - Comfort working independently in a fast-paced environment - A willingness to spend most of your week in the field - Strong organizational skills and the ability to manage multiple relationships and priorities at once - Experience with Salesforce or CRM tools is a plus, but not required - Healthcare sales experience is helpful, but not required. We could treat these as Requirements. Qualifications: from "You’d be a great fit here if you are:" list: - Competitive and motivated by performance - Energized by building relationships and earning trust quickly - Excited by the challenge of growing accounts over time, not just making the first sale - Comfortable hearing “no” and resilient enough to keep going - Self-driven, resourceful, and excited by ownership - Coachable and hungry to improve - Adaptable in fast-moving, high-growth environments - Looking for an opportunity to grow their career quickly and make a meaningful impact These are more like personal attributes/qualifications. Skills: maybe we could extract specific skills: communication, relationship-building, organizational, Salesforce/CRM, etc. But those already appear in Requirements. To avoid duplication, we could combine Requirements and Qualifications into one section? But instruction says prefer few substantive sections over many thin ones. However we have distinct content; we could merge Requirements and Qualifications into a single "Requirements" section that includes both experience and personal traits. But the instruction list includes Qualifications as a possible heading; we can omit if we think it's thin. However we have substantial content for both; maybe better to have two sections: Requirements (experience) and Qualifications (personal traits). Skills could be omitted because skills are covered in Requirements. But we have "Strong communication and relationship-building skills" etc. That's skill. Could make Skills section for those specific skills: communication, relationship-building, organizational, Salesforce/CRM. However that would be thin. Given instruction to prefer few substantive sections, maybe we combine Requirements, Qualifications, Skills into one section called "Requirements" that includes all. But the instruction says use headings for those specific categories if content exists. It doesn't forbid omitting some headings. It says "include a section ONLY when the posting has real, specific content for it". So we can include only those headings that have real specific content. If we think Qualifications content is real specific, we should include it. Similarly Skills. But we risk duplication. Let's see if we can assign distinct content to each: - Requirements: experience (1-3 years, track record, etc.) - Qualifications: personal attributes (competitive, motivated, energized, etc.) - Skills: specific abilities (communication, relationship-building, organizational, Salesforce/CRM, etc.) Check if any overlap: Requirements list includes "Strong communication and relationship-building skills" and "Strong organizational skills" and "Experience with Salesforce or CRM tools". Those are skills. So if we make Skills section, we would duplicate those. To avoid duplication, we could move those skill lines to Skills section and remove from Requirements. But then Requirements would lose some content. However we could keep them in Requirements and not have Skills section. The instruction says prefer few substantive sections over many thin ones. Having Skills section might be thin if we only have a few items. Better to omit Skills and keep those under Requirements. Thus we will have: - About the role - Responsibilities - Requirements (includes experience, track record, communication, organizational, Salesforce, healthcare sales experience optional, etc.) - Qualifications (personal attributes) - Benefits - Pay - Schedule We need to ensure we preserve all substantive info. Let's extract Requirements content exactly as posted, but we may need to split into two groups. Original "We’d Love to Hear From You If You Have" list: - 1–3 years of experience in sales, customer-facing roles, healthcare, hospitality, recruiting, athletics, or other high-performance environments - A track record of hitting goals, competing, or outperforming expectations - Strong communication and relationship-building skills - A high level of coachability, curiosity, and willingness to learn - Comfort working independently in a fast-paced environment - A willingness to spend most of your week in the field - Strong organizational skills and the ability to manage multiple relationships and priorities at once - Experience with Salesforce or CRM tools is a plus, but not required - Healthcare sales experience is helpful, but not required. We'll keep all these in Requirements. Qualifications list from "You’d be a great fit here if you are:": - Competitive and motivated by performance - Energized by building relationships and earning trust quickly - Excited by the challenge of growing accounts over time, not just making the first sale - Comfortable hearing “no” and resilient enough to keep going - Self-driven, resourceful, and excited by ownership - Coachable and hungry to improve - Adaptable in fast-moving, high-growth environments - Looking for an opportunity to grow their career quickly and make a meaningful impact We'll keep those. Now Benefits: list from "Why Join Nourish": - Competitive base salary + uncapped monthly variable compensation - Clear path for growth and promotion within the Provider Partnerships organization - Mission-driven work that directly improves patient access to care - High-autonomy, high-ownership culture - Supportive leadership and collaborative team environment - Mileage reimbursement at IRS standard rate - $65/month cell phone reimbursement - $125/quarter work-from-home stipend - Company card for provider engagement expenses - Comprehensive medical, dental, and vision coverage Note: The first item is compensation; we might move that to Pay section. But we already