Board Certified Behavior Analyst (BCBA) with Arizona LBA

We need to output HTML fragment with sections: About the role? The posting includes description: "Looking for a fresh start? ..." That's intro. Then "Why Clinicians Love The Treetop ABA" with bullet points. Then "Who We Are". Then "What You'll Be Doing". Then "Requirements". Then "Benefits". Also Salary and Schedule are given early: "Salary: $85,000-$95,000 BASE plus additional monthly bonus opportunities Schedule: Monday thru Friday. No Weekends! Flexible scheduling. Remote with quarterly travel opportunities". So we need Pay and Schedule sections if posting actually states them. Yes they state salary and schedule. So we should include Pay and Schedule sections. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, equal opportunity, scam warning, application instructions, etc. Also remove "Ready to Grow with Us?" maybe that's call to action; but it's not boilerplate? It's more like invitation; but we can keep as part of About? Might be considered application instruction? It says "Apply today—it only takes a few minutes." That's application instruction; we should remove that line. Also "The Treetop ABA is an Equal Opportunity Employer..." remove. Also "This position is open to candidates who reside in Arizona only." That's location restriction; maybe keep as part of Requirements? Could be a note but not boilerplate; but it's a requirement (location). We could incorporate into Requirements as a bullet? But we have Requirements section already; we could add a bullet about Arizona residency. However the instruction says preserve ALL substantive information; do not invent or summarize away detail. So we need to keep that location restriction. Could be a separate short p. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we should only include sections when posting has real specific content. We have content for About the role (intro), Responsibilities (What You'll Be Doing), Requirements (Your Qualifications), Benefits, Pay, Schedule. Possibly also Qualifications? The posting has "Requirements Your Qualifications". Could treat as Requirements and Qualifications combined? But we have separate headings for Requirements and Qualifications; we need to decide. The posting lists qualifications under Requirements. Could treat that as Requirements section; Qualifications maybe not needed separately. But we could still have Qualifications heading if we have content; but we don't have separate qualifications beyond those. Safer to follow instruction: Prefer few substantive sections over many thin ones. So we can combine Requirements and Qualifications into one section titled Requirements (or Qualifications). But the instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't mandate we must use all; we just use when we have content. So we can have Requirements (includes qualifications). We could also have Skills if there are specific skills listed: "Strong Communication & Coaching Skills", "Passion for Compassionate Care", "Adaptable & Driven". Those could be considered skills. But we could also put them under Requirements. To keep few sections, we can put them under Requirements. Thus sections: About the role (intro paragraph), Responsibilities (What You'll Be Doing), Requirements (including qualifications and skills), Benefits, Pay, Schedule. We need to use

• for any list of duties/requirements/benefits. So for Responsibilities we need list. For Requirements we need list. For Benefits we need list. We need to preserve all substantive information. Let's extract. Intro: "Looking for a fresh start? If you're feeling burned out, overwhelmed by productivity expectations, or simply wondering if there's a better place to practice, we'd love to have a conversation. At Treetop ABA, we've created an environment where BCBAs can focus on delivering excellent clinical care while receiving the support, flexibility, and respect they deserve." That's About the role. Why Clinicians Love The Treetop ABA: bullet points list: - A Collaborative, Supportive Team Work alongside compassionate clinicians who genuinely enjoy collaborating, sharing ideas, and supporting one another's success - BCBA-Led Clinical Excellence Our clinical culture is led by experienced BCBAs who understand the realities of the role and are committed to delivering exceptional, evidence-based care - Accessible Clinical Leadership Receive ongoing mentorship, guidance, and support from leaders who are invested in your professional growth and clinical success - Ethics First We prioritize ethical decision-making, high-quality clinical outcomes, and doing what's right for our clients, not simply meeting productivity expectations - Technology & Administrative Support Our AI-powered tools and dedicated back-office team help streamline administrative tasks so you can spend more time focused on your clients and less time on paperwork - Continuous Learning & Growth From free in-house CEUs to mentorship and professional development opportunities, we're committed to helping you grow throughout your career - Manageable Caseloads With a 25-billable expectation, you'll have the time and support needed to provide high-quality, individualized care while maintaining a healthy work-life balance These could be part of About the role or Benefits? They are more about culture; could be part of About the role. We'll include them as part of About the role maybe as a list under About the role? But About the role is supposed to be prose; we could still have a list inside? The instruction: Use
  • for any list of duties/requirements/benefits, and

    for prose. So if we have a list that is not duties/requirements/benefits, maybe we still should use list? It says "any list of duties/requirements/benefits". It doesn't forbid using list for other things, but to be safe we could incorporate those points into prose or keep as list under About the role? Might be considered benefits? Actually they are benefits/culture. Could be placed under Benefits section. But Benefits section already has specific benefits like PTO, insurance, etc. The culture points could be part of About the role. I'll keep them as a list under About the role? But the instruction says use list for duties/requirements/benefits; culture is not exactly those. Might be okay to use

    with line breaks? Better to keep as

    with sentences separated. But we risk losing structure. However we can keep them as

    • under About the role; it's still a list, but not strictly duties/requirements/benefits. The instruction may be interpreted as: when you have a list of duties/requirements/benefits, you must use
      • . It doesn't prohibit using lists elsewhere. So we can use list for culture. Thus About the role: intro paragraph + maybe a list of culture points. Responsibilities (What You'll Be Doing): list: - Design & Implement ABA Plans: Develop personalized therapy plans that create real, measurable impact - Conduct Assessments & Track Progress: Use data to guide meaningful client outcomes - Lead & Mentor Behavior Technicians: Inspire and support your team with coaching and expertise - Partner with Families: Collaborate with caregivers to set goals, celebrate successes, and build trust - Remote Caseload: Enjoy the perfect blend of remote work with quarterly travel opportunities - Stay Current: Keep up with the latest ABA research and best practices Requirements (Your Qualifications): list: - Active BCBA and Arizona LBA Certification - Required to ensure clinical excellence. - Strong Communication & Coaching Skills - Able to inspire, guide, and support your colleagues effectively. - Passion for Compassionate Care - A genuine commitment to delivering high-quality ABA services. - Adaptable & Driven - Comfortable thriving in both clinic and remote environments, adjusting to evolving needs. - Must reside in Arizona (position open to Arizona residents only). We could also include "Active BCBA and Arizona LBA Certification" as requirement. Benefits: list from Benefits section: - Industry-leading Base (Remote) Salary: $85K-$95K based on experience plus additional bonus potential (below) (but we have Pay section separate; maybe we shouldn't duplicate salary in Benefits; but the Benefits section includes salary info; we have Pay section for salary. To avoid duplication, we could keep salary only in Pay section and not repeat in Benefits. However the Benefits section also mentions "Attractive monthly performance bonuses with clear, attainable benchmarks - opportunities to make up to $2,600 per month ($31,200 annually)". That's bonus info; could be part of Pay as well. But we have Pay section for salary; we could include bonus in Pay or Benefits. The instruction: include Pay section only when posting actually states them. It states salary and bonus. So Pay section could include both base salary and bonus. Benefits section then would exclude salary/bonus. Let's parse Benefits list: From Benefits section: - Industry-leading Base (Remote) Salary: $85K-$95K based on experience plus additional bonus potential (below) - Attractive monthly performance bonuses with clear, attainable benchmarks - opportunities to make up to $2,600 per month ($31,200 annually) - 15 days Paid Time Off (PTO), plus 8 company holidays which includes flex days (you choose!) - because you deserve time to recharge! - Remote Schedule - work from the comfort of your home! - Annual CEU Stipend: $1,000 to support your professional growth plus free in house CEUs, and ongoing mentorship and advancement opportunities as we expand throughout Arizona - 401(k) with Company Match: Helping you build your financial future - Employee Referral Bonuses: Rewarded for helping us grow our amazing team - Manageable Caseloads: Focus on high-quality care without burnout - Comprehensive Insurance - Medical, Dental, Vision, and Life Insurance to keep you and your family healthy and protected Note: Remote Schedule also appears; but we have Schedule section separate. So we should not duplicate schedule in Benefits. Manageable Caseloads also appears in Requirements? Actually it's also in Benefits list; but we already have Manageable Caseloads under Why Clinicians Love... maybe duplicate. We need to preserve all substantive information; we can include it in Benefits or elsewhere but not duplicate? Duplication is allowed if it's in posting; but we should avoid repeating same content multiple times? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but we should avoid unnecessary repetition. However we can keep each piece in its appropriate section; if it appears in multiple places, we could include it once. But to be safe, we can include each piece where it fits best, and if it appears elsewhere we can still include but maybe not duplicate. Let's decide: - Manageable Caseloads: appears in Why Clinicians Love... and also Benefits. We'll keep it under Benefits maybe, or under About the role? It's a benefit. We'll keep under Benefits. - Remote Schedule: appears in Benefits and also Schedule section. We'll keep schedule in Schedule section; we can omit from Benefits to avoid duplication. - Salary and bonus: we will put in Pay section; we can omit from Benefits. Thus Benefits list will include: - 15 days Paid Time Off (PTO), plus 8 company holidays which includes flex days (you choose!) - Annual CEU Stipend: $1,000 to support your professional growth plus free in-house CEUs, and ongoing mentorship and advancement opportunities as we expand throughout Arizona - 401(k) with Company Match - Employee Referral Bonuses - Manageable Caseloads: Focus on high-quality care without burnout - Comprehensive Insurance - Medical, Dental, Vision, and Life Insurance Also maybe "Remote Schedule" removed. Now Pay section: base salary $85,000-$95,000 BASE plus additional monthly bonus opportunities; also mention attractive monthly performance bonuses up to $2,600 per month ($3