Center Director, ABA Clinic (BCBA)
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. We need to preserve all substantive info, remove boilerplate. No job title heading, no Job ID. No application instructions. No cookie/navigation/legal/EEO etc.
We need to parse the posting.
Key sections:
- About Aviation Aba Therapy (maybe "About the role"? Actually "About Aviation Aba Therapy" is about company. Could be "About the role"? 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:
WHY THIS ROLE IS DIFFERENT (intro) – could be part of About the role.
About Aviation Aba Therapy – could be About the role or maybe separate but we only have allowed headings. Could put under About the role.
What You Will Own – includes Clinical Leadership, Operations and Accountability, Growth and Strategy, Training and Development. That's responsibilities.
Required – qualifications.
Preferred – maybe skills? Or qualifications.
Who You Are – maybe skills or attributes.
Compensation And Benefits – includes base salary, bonus, long-term incentive, health, dental, vision, PTO, holidays, CEU support, professional development budget, direct access to leadership. That's Benefits and Pay.
We need separate Pay and Benefits sections if content exists. Pay: base salary range, performance bonus potential, long-term incentive. Benefits: health/dental/vision, PTO, holidays, CEU support, professional development budget, direct access.
Schedule: not mentioned; we should not create Schedule section.
We need to avoid filler like "commensurate with experience" – that's okay as it's actual content? It says base salary: $90,000 to $100,000, commensurate with experience and leadership track record. That's specific enough; we can keep.
We must not create sections with placeholder text.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
... content ...
Responsibilities
- ... each bullet ...
About the role
... paragraphs ...
But we might want to use- for lists. For About the role we could use
for prose; but we have bullet points. Could use
- for each bullet. The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So for About the role, which is more descriptive, we can use
paragraphs. But we have bullet points; maybe we can still use
with sentences. However we need to preserve all substantive info; we can convert bullet points into sentences within
. That's okay. But for responsibilities, requirements, qualifications, skills, benefits, pay we should use
- .
We need to decide which sections to include.
We have:
- About the role (intro + company description)
- Responsibilities (What You Will Own)
- Requirements (Required)
- Qualifications? Could combine Required and Preferred? But we have separate headings: Requirements, Qualifications, Skills. The instruction says use those headings if content exists. We have Required (mandatory) and Preferred (nice-to-have). Could map Required to Requirements, Preferred to Qualifications or Skills. Who You Are could be Skills? Or maybe we treat Who You Are as Skills (soft skills). We'll decide.
We need to avoid thin sections; prefer few substantive sections. But we need to include all info. We could combine Required and Preferred into Requirements and Qualifications? But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content for About the role, Responsibilities, Requirements (Required), Qualifications (Preferred), Skills (Who You Are), Benefits, Pay.
We should not create Schedule.
Thus we will output sections:
About the role
... combined intro and company description ...
Responsibilities
- ... each bullet ...
Requirements
- ... each required bullet ...
Qualifications
- ... each preferred bullet ...
Skills
- ... each Who You Are bullet ...
Benefits
- ... health/dental/vision, PTO/holidays, CEU support, professional development budget, direct access ...
Pay
- ... base salary range, performance bonus potential, long-term incentive ...
elements. But instruction: Use
for prose. So we can have multiple
tags. We'll do:
About the role
This is not a step sideways; it is an on-site leadership role for a BCBA who has built clinical programs, led teams, and wants to run a clinic of their own inside a growing, mission‑driven company. Aviation ABA Therapy is opening a second clinic in Provo after building a strong in‑home program and a thriving South Salt Lake location.
The company treats clinical excellence, operational discipline, and family experience as one integrated system, moving fast and running lean while expecting leaders to think outside the box. As Clinic Director you will own the Provo site, shaping care delivery, staff training, and clinic growth from day one, reporting to the Clinical Director and working alongside the CEO and broader leadership team with real autonomy and support.
A
- .
We need to decide which sections to include.
We have:
- About the role (intro + company description)
- Responsibilities (What You Will Own)
- Requirements (Required)
- Qualifications? Could combine Required and Preferred? But we have separate headings: Requirements, Qualifications, Skills. The instruction says use those headings if content exists. We have Required (mandatory) and Preferred (nice-to-have). Could map Required to Requirements, Preferred to Qualifications or Skills. Who You Are could be Skills? Or maybe we treat Who You Are as Skills (soft skills). We'll decide.
We need to avoid thin sections; prefer few substantive sections. But we need to include all info. We could combine Required and Preferred into Requirements and Qualifications? But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content for About the role, Responsibilities, Requirements (Required), Qualifications (Preferred), Skills (Who You Are), Benefits, Pay.
We should not create Schedule.
Thus we will output sections:
- for any list of duties/requirements/benefits, and
- for each bullet. The instruction: Use