Child and Adolescent Therapist - SiSW, LPC-R

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections from the posting: 1. About Blackbird Health (company description) 2. Position Summary 3. Employment Options (with two sub-options: Full-Time and Part-Time) 4. Why Blackbird & Your Impact 5. Who You Are (requirements/qualifications) 6. Salary Range (already mentioned in employment options) 7. Some boilerplate at the end about inclusive environment, EEO, contact info - these should be removed per rules. Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use

• for lists,

  for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions - Include section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, let's map the content to appropriate sections: The posting has: - Company description: "About Blackbird Health" - this could be "About the Company" or similar, but the rules mention "About the role" as a heading example. However, the company description is substantive. I'll use "About Blackbird Health" as heading? But rules say use

  for section headings like "About the role". The posting doesn't have an "About the role" section; it has "Position Summary". I'll use "Position Summary" as heading. - Position Summary: describes the role. - Employment Options: two options with details on compensation, hours, schedule, benefits, supervision. This could be split into "Pay & Schedule" and "Benefits" but the rules say only create sections if posting actually states them. The posting has specific details for each employment option. I could create a section "Employment Options" with subsections? But we only have

  headings. Could use

  for each employment option? But rules say use

  for section headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So maybe we should have separate sections for "Pay", "Schedule", "Benefits". However, the posting combines them per employment type. The rules: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state them, but they are embedded within employment options. I think we should create sections for "Pay", "Schedule", "Benefits" but only if they are distinct. However, the posting has two different employment options with different pay, schedule, benefits. Might be better to keep as "Employment Options" with details. But the rules say: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect those specific headings if content exists. The posting has "Why Blackbird & Your Impact" which is like benefits/perks. "Who You Are" is requirements/qualifications. Let's decide on sections: 1. Position Summary (prose) 2. Employment Options (maybe with two subsections? But we can't use h4? The rules only mention h3. Could use h3 for each employment type? But that might be too many headings. Alternatively, we can have a section "Employment Options" with prose and lists. 3. Why Blackbird & Your Impact (list of benefits/perks) 4. Who You Are (requirements/qualifications) - list 5. Salary Range (already covered in employment options, but there's a separate line "Salary Range: $40,000 USD - $85,000 USD". That's a summary range. Could be part of Pay section. But the rules: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state pay, schedule, benefits in detail. So we could create separate sections for Pay, Schedule, Benefits. However, the pay and schedule differ between full-time and part-time. Might be better to keep them together under "Employment Options". I think the best is to follow the natural sections of the posting: - Position Summary - Employment Options (with details for Full-Time and Part-Time) - Why Blackbird & Your Impact - Who You Are And maybe a "Benefits" section? But benefits are included in employment options and also in "Why Blackbird". The "Why Blackbird" includes supervision, credentialing, guaranteed caseload, impact. That's more about perks/impact. The rules say: "Prefer a few substantive sections over many thin ones." Thus, I'll create:

  Position Summary

  ...

  Employment Options

  Then for each option, maybe use

  ? But rules only allow h3? The instruction says "use

  for section headings". It doesn't forbid h4, but says use h3 for section headings. Could use h3 for each employment option? That would be two h3 headings: "Full-Time (Provisionally Licensed FTE)" and "Part-Time (Provisionally Licensed PT)". But then we lose the grouping. Might be okay. Alternatively, keep "Employment Options" as h3, then use

  and

  for each option. Let's see the content: For each option, there are base compensation, hours & schedule, benefits & supervision. Could present as two subsections with bold labels? But we need semantic HTML. Could use

  for each employment type? The instruction doesn't explicitly forbid h4, but says "use

  for section headings". It might be okay to use h4 for subsections. However, to be safe, I'll use h3 for each employment type, but that might be too many headings. The posting has two employment options, each with distinct details. I think using h3 for each is acceptable. But the rules: "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Associate / Provisionally Licensed Therapist". Not repeated. I'll structure as:

  Position Summary

  ...

  Full-Time Employment (Provisionally Licensed FTE)

  Base Compensation: $65,000 – $70,000 base salary (100% Onsite)

  Hours & Schedule

  ? Not allowed? I'll use

  and

  for schedule details. Actually, the rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect Pay and Schedule as separate sections. But the posting combines them per employment type. However, the posting also has a "Salary Range" at the end. Might be better to create separate sections for Pay, Schedule, Benefits that aggregate across both employment types? But they differ. Given the complexity, I'll follow the posting's structure and use h3 for each major section: Position Summary, Employment Options (with subsections using h4? but not specified). I think using h3 for each employment option is fine. Let's examine the rules again: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests that if there is a "Pay" section, use h3. The posting has pay information. But it's split. I could create a "Pay" section that summarizes both? But the posting doesn't have a unified pay section. I think the best is to keep the posting's own headings as h3, but ensure they match the suggested ones where appropriate. The posting has "Position Summary", "Employment Options", "Why Blackbird & Your Impact", "Who You Are". Those are substantive. I'll map: - Position Summary -> About the role? But the rule says "About the role" as example. However, the posting uses "Position Summary". I'll use "Position Summary" as h3. - Employment Options -> could be "Pay & Schedule" and "Benefits"? But the posting includes benefits under each option. I'll keep "Employment Options" as h3, then within it, use

  for each option's details. - Why Blackbird & Your Impact -> this is like Benefits/Perks. Could be "Benefits" but it's more about impact. I'll use "Why Blackbird & Your Impact" as h3. - Who You Are -> Requirements/Qualifications. I'll use "Requirements" as h3 (since rules mention Requirements, Qualifications). The posting says "Who You Are". I'll use "Requirements" as heading. - Salary Range: already covered. - The inclusive environment boilerplate should be removed. Now, let's write HTML. We need to preserve all substantive information. So include all details. I'll start with Position Summary. Then Employment Options: I'll create a list for each option? Or use prose with nested lists. Better to use
  for each option's details. Let's draft:

  Position Summary

  As an Associate / Provisionally Licensed Therapist at Blackbird Health, you’ll deliver high-quality, evidence-based therapy to children, adolescents, young adults, and their caregivers with full clinical supervision and administrative support provided by Blackbird. Working onsite alongside an interdisciplinary team, you’ll receive dedicated clinical supervision hours toward independent licensure while delivering impactful care to young patients and their families.

  Employment Options

  W2 Full-Time (Provisionally Licensed FTE) | SiSW, LPC-R

  Base Compensation: $65,000 – $70,000 base salary (100% Onsite)

  Hours & Schedule

  • Workload: 36 hours of scheduled clinical availability supporting 28 completed direct care hours/week.
  • Shift Schedules: 4-day workweek options including 12:00 PM – 8:00 PM or 1:00 PM – 9:00 PM (4 days/week).
  • Core Hours: Minimum of 20 Core hours/week during peak evening/weekend periods (after 3:00 PM weekdays and/or weekends).

  Benefits & Supervision

  • Full clinical board supervision provided at no cost
  • Medical, dental, vision
  • 401(k) with company match
  • PTO + 11 paid holidays
  • Life insurance
  • Short/long-term disability

  W2 Part-Time (Provisionally Licensed PT) | SiSW, LPC-R

  Base Compensation: $40,000 base salary + $65 / session incentive for completed sessions beyond the 17-hour baseline.

  Hours & Onsite Expectations

  • 100% Onsite (Flex): 20 contracted hours per week (17 completed direct care hours).
  • Core Schedule: All 20 hours