Special Education Teacher – One-on-One Child Development

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions (like "Apply Today—we'd Love To Learn More About You.") and any duplicated lines. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The posting includes "INDBCA" at end maybe a code; we can drop as minor metadata. We need to include sections only when posting has real specific content. Let's extract content: - Intro paragraph: "Use Your Special Education Experience in a More Meaningful, Individualized Setting. Bright Pathways is seeking experienced Special Education Teachers, Autism Classroom Teachers, Life Skills Teachers, Resource Teachers, Inclusion Teachers, Behavior Interventionists, and Special Education Paraprofessionals to join our growing team. If you enjoy helping children who learn differently, adapting your teaching to meet individual needs, and celebrating meaningful progress, this role offers the opportunity to do even more of what you love. Instead of supporting an entire classroom, you'll work one-on-one with a child, building a strong relationship while helping them develop the communication, social, emotional, behavioral, and daily living skills they need to become more independent and successful in everyday life." That's about the role. Could be "About the role" section. - "What You'll Be Doing:" then bullet list of duties. List items: Help a child communicate their wants and needs more effectively. Teach social skills through games, play, and everyday interactions. Help children develop friendships, take turns, share, and participate successfully with others. Support emotional regulation and teach strategies for handling frustration, disappointment, or changes in routine. Teach independence with everyday activities such as getting dressed, brushing teeth, completing homework, or following daily routines. Practice community skills such as ordering food, grocery shopping, playground interactions, or participating in recreational activities. Create engaging learning opportunities through play, crafts, books, outdoor activities, and other child-centered experiences. Celebrate meaningful milestones—whether it's saying a new word, making a new friend, or completing a task independently for the first time. Every activity has a purpose. You'll receive individualized goals for each child and ongoing guidance from experienced supervisors while using your own creativity and teaching skills to make learning engaging and enjoyable. We can treat the last sentence as prose after list. - "Why Special Education Professionals Thrive Here:" paragraph. - "Why Bright Pathways?" paragraph(s) about human-first organization, intentional about keeping company personal, leadership, supervisors, etc. - "Qualifications:" list of encouraged applications: Special Education Teacher, Autism Classroom Teacher, Life Skills Teacher, Resource Teacher, Inclusion Teacher, Behavior Interventionist, Special Education Paraprofessional. Then "Preferred qualifications:" bullet list: Experience working with children who benefit from individualized behavioral, developmental, communication, or learning support. Strong communication and relationship-building skills. Reliable transportation. Passion for helping children reach their fullest potential. - "What We Offer:" bullet list: $20–$32 per hour based on experience, Paid training and ongoing mentorship, Flexible scheduling, Thoughtful child and family matching, Supportive leadership and accessible supervisors, Professional development opportunities, Opportunities for long-term career growth, A collaborative, people-first culture. - "About Bright Pathways:" paragraph. We need to map to sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (intro). Responsibilities (What You'll Be Doing). Requirements maybe Qualifications? Actually Qualifications section is separate. Requirements could be the encouraged applications? But we have Qualifications and Preferred qualifications. Could treat Qualifications as Requirements? But we have both Qualifications and Preferred qualifications. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). So we need to decide which sections to include based on content. We have: - About the role: intro paragraph. - Responsibilities: duties list. - Requirements: maybe the encouraged applications (the qualifications we encourage). Could be "Qualifications" heading for that. But we also have "Qualifications" heading separate from Requirements. The list includes both "Qualifications" and "Preferred qualifications". Could combine into Qualifications section with sub-bullets? But we must not create thin sections. Perhaps we make a Qualifications section that includes both encouraged and preferred qualifications as lists. - Skills: maybe the preferred qualifications include strong communication etc. Could be Skills section. - Benefits: What We Offer includes many items; some are benefits like Paid training, Flexible scheduling, Professional development, Opportunities for long-term career growth, Collaborative culture. Also Pay: $20–$32 per hour based on experience. Schedule: Flexible scheduling (maybe also schedule). But we should not duplicate. Pay section: we have pay range. Schedule: flexible scheduling. We need to avoid filler like "commensurate with experience" etc. We have specific pay range. We need to output only HTML fragment, no markdown fences. Let's structure:

  About the role

  ... intro paragraph ...

  Responsibilities

  • Help a child communicate their wants and needs more effectively.
  • Teach social skills through games, play, and everyday interactions.
  • Help children develop friendships, take turns, share, and participate successfully with others.
  • Support emotional regulation and teach strategies for handling frustration, disappointment, or changes in routine.
  • Teach independence with everyday activities such as getting dressed, brushing teeth, completing homework, or following daily routines.
  • Practice community skills such as ordering food, grocery shopping, playground interactions, or participating in recreational activities.
  • Create engaging learning opportunities through play, crafts, books, outdoor activities, and other child-centered experiences.
  • Celebrate meaningful milestones—whether it's saying a new word, making a new friend, or completing a task independently for the first time.

  Every activity has a purpose. You'll receive individualized goals for each child and ongoing guidance from experienced supervisors while using your own creativity and teaching skills to make learning engaging and enjoyable.

  Qualifications

  We encourage applications from professionals with experience as:

  • Special Education Teacher
  • Autism Classroom Teacher
  • Life Skills Teacher
  • Resource Teacher
  • Inclusion Teacher
  • Behavior Interventionist
  • Special Education Paraprofessional

  Preferred qualifications:

  • Experience working with children who benefit from individualized behavioral, developmental, communication, or learning support.
  • Strong communication and relationship-building skills.
  • Reliable transportation.
  • Passion for helping children reach their fullest potential.
  Alternatively, we could split into Requirements and Skills. But we have Qualifications heading already. The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should include those headings if we have content. We have content for About the role, Responsibilities, Qualifications (maybe also Requirements?), Skills (maybe from preferred qualifications), Benefits, Pay, Schedule. We need to decide what goes where. - Requirements: maybe the encouraged applications (the baseline qualifications). Could be Requirements. - Qualifications: maybe the preferred qualifications? Or we could combine. But we have both encouraged and preferred. Could treat encouraged as Requirements, preferred as Skills? Or Qualifications. Let's map: Requirements: encouraged applications list. Skills: preferred qualifications (communication, transportation, passion). Could also include experience working with children etc. Qualifications: maybe we could skip if we already have Requirements and Skills. But we need to avoid thin sections. Perhaps we combine Requirements and Qualifications into one Qualifications section. But the instruction says prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Qualifications (including both encouraged and preferred), Benefits, Pay, Schedule. We also have About Bright Pathways paragraph; could be part of About the role or separate section like "About the company". Not in list of headings but we could include as part of About the role or maybe as a separate section like "About Bright Pathways". But the instruction only gave examples; we can add other headings if needed? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those. We could incorporate About Bright Pathways into About the role or maybe as a separate paragraph under About the role. We also have "Why Special Education Professionals Thrive Here:" and "Why Bright Pathways?" paragraphs. Those could be part of About the role or Benefits? They are more about culture. Could be part of Benefits or maybe a separate section like "Why work here". But not in list. Could incorporate into Benefits or About the role. We need to preserve all substantive information. So we must include those paragraphs somewhere. We could add a section "Why Bright Pathways?" as its own heading, but not in the examples. However, the instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but to be safe, we could incorporate that content into existing sections like Benefits or About the role. Better to create a section "Why Bright Pathways?" as it's substantive. But the instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies those are examples, not exhaustive. So we can use other headings as needed. However, they also say "Prefer a few substantive sections over many thin ones." So we should avoid many thin sections. Adding a Why Bright Pathways section may be okay. But we also have "Why Special Education Professionals Thrive Here:" which could be part of Benefits or About the role. Let's think: we have a lot of content; we could have sections: - About the role (intro + why special ed professionals thrive here + why Bright Pathways? maybe combined) - Responsibilities - Qualifications (encouraged + preferred) - Benefits (What We Offer) - Pay - Schedule That's six sections. We need to ensure we don't repeat info. Let's extract each piece: Intro paragraph (first paragraph) -> About the role. "Why Special Education Professionals Thrive Here:" paragraph -> could go under About the role as well. "Why Bright Pathways?" paragraphs (two paragraphs) -> also About the role. Thus About the role will contain multiple paragraphs. Responsibilities: the bullet list and the sentence after. Qualifications: encouraged applications list and preferred qualifications list. Benefits: What We Offer bullet list. Pay: $20–$32 per hour based on experience. Schedule: Flexible scheduling (maybe also mention flexible scheduling under Benefits? But we have it also in Benefits list. To avoid duplication, we could put Flexible scheduling under Schedule section, and not duplicate in Benefits. But the Benefits list includes "Flexible scheduling". If we move it to Schedule, we should remove from Benefits to avoid duplication. However, we must preserve all substantive information; we can keep it in Schedule and not duplicate in Benefits. But we need to check if Benefits list includes other items that are not schedule. We'll keep Benefits without Flexible scheduling. Thus Benefits list: Paid