Clinic Director

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only sections that have real content. Remove boilerplate. Preserve all substantive info. We need to parse the input. Input includes: Overview: Lead an established clinic... (some text). Then a span about Pay down your student loans faster – up to $25K in repayment support through our student loan repayment program... Then a span about Benefits include generous paid time off, medical, dental, vision, disability, and 401(K) with a 4% employer match. A care model designed to support quality outcomes and efficiency. AI clinical documentation support... Structured mentorship and career development. Industry-leading continuing education through Evidence in Motion (EIM) including residency, fellowship, and board certification support. Multiple career pathways: clinical excellence, hybrid roles, and leadership Then Responsibilities: You’ll Achieve Success By: then list items (Provide direct patient care..., Lead, mentor..., Manage budgets..., Expand clinic visibility...) Then Qualifications: then list items (Doctorate in Physical Therapy, Licensed Physical Therapist in good standing in Ohio, Proven leadership experience..., Proficiency in Microsoft Office Suite and web-based EMR systems) Then later there is a section: About: Compensation: $90,000 - $100,000 / Year commensurate with experience. $10,000 sign-on bonus available! Benefits include generous paid time off, medical, dental, vision, disability, and 401(K) with a 4% employer match. Confluent Health... EEO etc. We need to include sections: About the role (maybe from Overview?), Responsibilities, Requirements (maybe Qualifications?), Qualifications (maybe separate?), Skills (maybe from qualifications?), Benefits, Pay, Schedule. We need to decide what content goes where. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have those headings if content exists. We must not repeat job title as heading (not present). Do not put Job ID/requisition numbers as headings. We must include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Thus we need to check each potential section: - About the role: The Overview paragraph describes role: "Lead an established clinic, build your vision, and make a lasting impact. At Fairborn Clinic, you'll have the autonomy to shape the future of patient care while benefiting from a strong referral network, a trusted community reputation, and a culture dedicated to Passionately Impacting Lives. This is an opportunity to lead with purpose, grow professionally, and leave your mark on a clinic that has served the Beavercreek community for more than a decade." That's substantive. Also there is later "About: Compensation..." but that's separate. So we can put Overview content under About the role. - Responsibilities: we have list items. - Requirements: Could be Qualifications? The posting has "Qualifications:" heading with list. That could be Requirements or Qualifications. We need both sections maybe. The instruction says we can have Requirements and Qualifications separate if content exists. The posting has "Qualifications:" list. It also may have "Requirements" not explicitly labeled but could be same as qualifications. However we have also "Qualifications:" list includes doctorate, license, leadership experience, proficiency. Those are qualifications. There's no separate "Requirements" besides that. So we could treat Qualifications as the qualifications section, and maybe Requirements could be omitted or we could put same content under Requirements? But we must not create sections with filler. If we don't have distinct Requirements content, we should not create a Requirements heading. So we will have Qualifications section. - Skills: Could be derived from qualifications like proficiency in Microsoft Office Suite and web-based EMR systems. That's a skill. Could also include leadership, mentoring etc. But we already have those in qualifications. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine skills into Qualifications or Responsibilities. But we have a separate Skills heading possible if we have specific skill list. The posting does not have a separate skills list; we could extract "Proficiency in Microsoft Office Suite and web-based EMR systems" as a skill. But we already have that under Qualifications. To avoid thin sections, we could omit Skills heading and keep that under Qualifications. - Benefits: The posting mentions benefits multiple times: "Benefits include generous paid time off, medical, dental, vision, disability, and 401(K) with a 4% employer match." Also earlier: "Benefits include generous paid time off, medical, dental, vision, disability, and 401(K) with a 4% employer match." Also earlier: "Pay down your student loans faster – up to $25K in repayment support through our student loan repayment program". Also "AI clinical documentation support... Structured mentorship and career development. Industry-leading continuing education through Evidence in Motion (EIM) including residency, fellowship, and board certification support. Multiple career pathways: clinical excellence, hybrid roles, and leadership". Those could be considered benefits as well. So we have substantive benefits content. - Pay: The posting includes "Pay down your student loans faster – up to $25K in repayment support through our student loan repayment program, paid directly to your loan servicer. Program details and offerings vary by location and role." Also later: "Compensation: $90,000 - $100,000 / Year commensurate with experience. $10,000 sign-on bonus available!" So we have pay info: salary range and sign-on bonus, plus student loan repayment support. That's substantive. However note: we must not create Pay section if content is only filler like "commensurate with experience". But we have actual numbers: $90,000 - $100,000 / Year, $10,000 sign-on bonus, up to $25K loan repayment. So we can include Pay section. - Schedule: No mention of schedule (e.g., full-time, part-time, hours). Not present. So we should not create Schedule section. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We need to format as HTML fragment: use

for each heading, then content:

for prose,

• for lists. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we need to strip out the EEO statement at the end, also the "Confluent Health, LLC and its affiliates are equal opportunity employers..." etc. Also remove the "If you need assistance..." line. Also remove duplicated lines: The benefits sentence appears twice; we should include only once. We need to include the student loan repayment program detail under Pay or Benefits? It's a benefit but also related to pay. The instruction: we have Pay section for compensation, student loan repayment could be under Benefits or Pay. Since it's a financial benefit, but we already have Pay section for salary and sign-on bonus. Could also include loan repayment under Benefits. However we need to avoid duplication. Let's decide: Put salary range and sign-on bonus under Pay. Put student loan repayment under Benefits (as it's a benefit). Or we could put both under Pay. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does not forbid mixing content. But we need to preserve all substantive info. We'll allocate: - About the role: overview paragraph. - Responsibilities: list of 4 items. - Qualifications: list of 4 items (doctorate, license, leadership experience, proficiency). - Benefits: list of benefits: generous paid time off, medical, dental, vision, disability, 401(K) with 4% employer match; student loan repayment up to $25K; AI clinical documentation support; structured mentorship and career development; industry-leading continuing education through EIM including residency, fellowship, board certification support; multiple career pathways: clinical excellence, hybrid roles, leadership. Also maybe "care model designed to support quality outcomes and efficiency". That's also a benefit. We'll include as separate bullet. - Pay: compensation: $90,000 - $100,000 per year; $10,000 sign-on bonus. We need to ensure we don't include filler like "commensurate with experience". The posting says "$90,000 - $100,000 / Year commensurate with experience." That includes the phrase "commensurate with experience". According to instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. It says we should not emit a heading followed by filler/placeholder text. Does that mean we cannot include the phrase "commensurate with experience" in the content? It says "never emit a heading followed by filler/placeholder text". That seems to refer to the heading itself? Actually "never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")". I think they mean we should not create a section where the only content is filler like "commensurate with experience". But if we have real numbers plus that phrase, it's okay to include the phrase as part of the content. However to be safe, we could omit the phrase "commensurate with experience" and just keep the numbers and sign-on bonus. But the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The phrase "commensurate with experience" is substantive? It's a qualifier but maybe considered filler. It's ambiguous. I'd keep it because it's part of the posted compensation description. However the instruction says never emit a heading followed by filler/placeholder text. That is about the heading, not the content. Actually reading: "never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")". Means if you create a heading, you shouldn't have only filler text under it. So as long as we have real numbers, it's fine. Thus we can include the phrase. Now we need to format HTML. We'll produce something like:

  About the role

  Lead an established clinic, build your vision, and make a lasting impact. At Fairborn Clinic, you'll have the autonomy to shape the future of patient care while benefiting from a strong referral network, a trusted community reputation, and a culture dedicated to Passionately Impacting Lives. This is an opportunity to lead with purpose, grow professionally, and leave your mark on a clinic that has served the Beavercreek community for more than a decade.

  Responsibilities

  • Provide direct patient care while overseeing clinic operations to ensure exceptional service and outcomes
  • Lead, mentor, and develop clinic staff to build a high-performing, patient-focused team
  • Manage budgets, resources, and schedules to drive financial success and operational efficiency
  • Expand clinic visibility through community outreach, marketing, and patient engagement initiatives

  Qualifications

  • Doctorate in Physical Therapy
  • Licensed Physical Therapist